[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [coldsync-hackers] Re: Redux: Netsync + [X]inetd
- To: <coldsync-hackers at lusars dot net>
 
- Subject: Re: [coldsync-hackers] Re: Redux: Netsync + [X]inetd
 
- From: "Alex Tronin" <at at urbis dot net>
 
- Date: Tue, 26 Feb 2002 18:29:03 -0500
 
- Organization: Urbis.Net Ltd
 
- References: <Pine.BSI.4.44.0202261453130.28814-100000@mail.his.com> <m21yf7zxo5.fsf@pi-air.mynet>
 
- Reply-To: coldsync-hackers at lusars dot net
 
- Sender: owner-coldsync-hackers at lusars dot net
 
> Something seems wrong with that reasoning somewhere, since services
> like telnet also listen on a port in /etc/services, and they readily
> handle multiple simultaneous connections.
Yes, telnetd accepts incoming connection on stdin.
As I said, ther are two way to do many net connections:
1) Launch from inetd/xinetd - incoming TCP connections on stdin. ColdSync
doesn't do it now - so won't work.
2) Have ColdSync run as daemon and listen() - fork() -accept(). It is not
doing this now, so won't work too.
Bottom line - ColdSync has to be modified for multiple Net Connections - but
not a great deal.
I had no problems with ColdSync NetSync when connections are done one at a
time -works just fine.
Alex Tronin
-- 
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.