Re: [coldsync-hackers] Re: What goes in inetd.conf?

["Brian Johnson" <bjohnson at jecinc dot on.ca>]

Although it would be nice to have, I think we've found workaround hacks for it in
the meantime (on Linux - I don't know if they will work for other OS's)

For local syncs - put it in inittab (check the mailing list archives for how)

For network syncs - run a cron job to restart coldsync (check the mailing list
archives for how)

I don't know if they will work together (coldsync running at the same time even if
not a simiutaneous sync) - I haven't heard any reports from people running both
local and network syncs




Alessandro Zummo (azummo-coldsync2@towertech.it) wrote*:
>
> On 03-Set-02 at 11:38:13,
>  Rich Bowen <rbowen@rcbowen.com> wrote:
>
>
>>> No, inetd.conf shouldn't be used with coldsync. The correct flag is -md.
>
>>> As you noticed, coldsync exits after the first sync. You can put an
>>> entry in
>>> /etc/inittab to keep it running.
>
>> Ohhhh. I see. I assumed that daemon mode meant that it would actually run
>> as a daemon, and stay running. I misunderstood. Thanks for the tip.
>
>I think such a feature needs to be implemented in the near future... anyone
>volunteers for it?
>
>
>--
>
>  - 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.