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

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

 On 03-Set-02 at 15:50:06,
  Andrew Arensburger <arensb+CShackers@ooblick.com> wrote:


>> I think such a feature needs to be implemented in the near future...
>> anyone volunteers for it?

>     The reason I didn't do it that way in the first place is that
> a long-running daemon will inevitably leak memory; if it exits after
> syncing, at least the memory that it leaks will be reclaimed. Plus,
> there might be issues if it caches /etc/coldsync.conf or /etc/palms
> information.
>     It's possible to avoid this by having the daemon fork() for
> new requests, and make sure that the long-running part doesn't leak

that's the model i would like to follow.

> memory or retain transient information, but I'm wondering what the
> real issue is. Was there a serious problem getting it to run from
> /etc/ttys (or /etc/inittab under SysV-derivatives)?

multiple network syncs at the same time...?

-- 

  - 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.