RE: [coldsync-hackers] Re: Redux: Netsync + [X]inetd

["Rob Bloodgood" <robb at empire2 dot com>]

> > My resolution:
> > 1) ColdSync in netsync mode should listen on both ports independently -
> > which calls to have UDP daemon like pi-csd running separately
> > 2) running netsync from inetd.conf or xinetd.conf calls for serious code
> > rewriting - stdin is incoming TCP/IP connection to PDA and stdout is
> > outgoing TCP/IP connection - so extensive modifications are required.
>
> > So, I think best way to have coldsync running as standalone
> > server for TCP and another small daemon for UDP
>
> There's  a think i can't understand:
>
> last week i tried coldsync in netsync mode and worked perfectly. Why do we
> need to use a netcat or (x)inetd wrapper?

Did it automatically restart, waiting for the next sync?

I must admit, I'm puzzled by the netcat trick... I'm not sure I understand
the way it works at all, except for providing an (empty?) input for the '-'
on the commandline.  OTOH, (x)inetd would provide for "answering the phone"
and then putting it back on the cradle again for the next call... :-)

L8r,
Rob


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