[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldsync-hackers] Re: Problem respawning coldsync daemon
- To: coldsync-hackers at lusars dot net
- Subject: Re: [coldsync-hackers] Re: Problem respawning coldsync daemon
- From: Andrew Bainbridge-Smith <Andrew dot Bainbridge-Smith at csiro.au>
- Date: 28 Feb 2002 08:54:37 +1100
- In-Reply-To: <yam8822.411.143645456@mail.galactica.it>
- References: <yam8822.411.143645456@mail.galactica.it>
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
On Tue, 2002-02-26 at 20:22, Alessandro Zummo wrote:
>
> 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.
Ok, gave that a go (actually I slept first then called coldsync). That
fixed the problem so I believe your probably right about the read bit.
I will also have a look at the code, but that won't happen until the
weekend and as I don't know my way around it, it may take me some time.
BTW: log files -dsync:5 -dmisc:5 didn't reveal anything useful.
Cheers,
Andrew
--
Dr Andrew Bainbridge-Smith
Senior Research Engineer
Machine Vision Group
CSIRO Manufacturing Science and Technology
Australia
--
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.