[coldsync-hackers] Re: Problem respawning coldsync daemon

[Alessandro Zummo <azummo-coldsync2 at towertech dot it>]

 On 26-Feb-02 at 05:03:46,
  Andrew Bainbridge-Smith <Andrew.Bainbridge-Smith@csiro.au> wrote:

> The above coldsync call works ok on the command line. But I am observing
> the same problem as in the first message.  It appears that after success
> with the first hotsync a new coldsync is respawn (first version exits as
> expected)--- ie. there is a change of PID.  This new coldsync does not
> respond. I don't even see messages in the log file indicating that
> coldsync is polling for activity.  ps reports that the new coldsync is
> waiting on a `read' from the moment it is spawned (given my delays to
> type ps etc).

You setup seems ok. Try to add a little delay just after the completition
ofthe hotsync process with something like this:

#!/bin/bash

coldsync etc etc...

sleep 3s

IMHO the problem is that the second coldsync is trying to read using
the connection the first one has just ended. 

Let me know if it worked for you. Then we might try to handle
this in coldsync itself.

-- 

  - alex.



-- 
This message was sent through the coldsync-hackers mailing list.  To remove
yourself from this mailing list, send a message to majordomo@thedotin.net
with the words "unsubscribe coldsync-hackers" in the message body.  For more
information on Coldsync, send mail to coldsync-hackers-owner@thedotin.net.