[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldsync-hackers] coldsync -t net Not Responding
- To: coldsync-hackers at lusars dot net
- Subject: Re: [coldsync-hackers] coldsync -t net Not Responding
- From: Christophe Beauregard <christophe dot beauregard at sympatico.ca>
- Date: Wed, 3 May 2006 17:02:32 -0400
- In-reply-to: <4456EF3A.4040508@mikebaas.org>
- References: <200605020508.k4258gh1014429@thirtyseven.lusars.net> <4456EF3A.4040508@mikebaas.org>
- Reply-to: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
- User-agent: KMail/1.8.3
On Tuesday 02 May 2006 01:33, Mike Baas wrote:
> Do I have to be more specific at the command line? I've tried
> specifying /dev/pilot as the port, with no luck.
"-t net" is only telling coldsync the underlying protocol to use, but it
doesn't actually tell it to _listen_ to the netsync ports. What you want is
described at the end of README.daemon:
Standalone
==========
To run ColdSync in standalone (one-shot) mode, you'll need a
profile like this one:
listen net "netsync-standalone" {
}
and launch ColdSync with
coldsync -md --listen netsync-standalone
c.