Re: [coldsync-hackers] coldsync -t net Not Responding

[Christophe Beauregard <christophe dot beauregard at sympatico.ca>]

On Thursday 04 May 2006 11:38, Mike Baas wrote:
> mike@jasmines:~$ coldsync -md --listen netsync-standalone -f
> myconfig -d sync:4
...
> Inside run_mode_Daemon()
> Using port from config file.
> Opening device [(null)]

Interesting. In _this_ trace, it actually found the listen block (since you 
got to the "Opening device" part). Is there now a process listing on port 
14237? i.e.

  cpb@earth:~$ netstat -an |grep 14237
  udp        0      0 0.0.0.0:14237           0.0.0.0:*

Because if you're getting that, coldsync is ready for a network connection.

> I thought the docs said the 'palms' information was option, so I
> didn't include any.

In daemon mode (-md), it's needed.

If you don't have it coldsync can try to _initialize_ the PDA (by running 
any "init" conduits), but you won't be able to get any further without it. 
Otherwise, during the sync you'll get a "No matching entry 
in /path/to/palms" error and it'll abort.

I suppose the intent here is that an "init" conduit could add the 
appropriate palms entry (this isn't exactly documented) and any other magic 
(create a Unix account).

> My suspicion is that "Opening device 
> [(null)]" is not a good error message but I'm not sure what to do
> to fix it.

In normal usage, this would list the path of the device file 
(i.e. /dev/pilot). As errors go, it's cosmetic.

c.