[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] Re: Redux: Netsync + [X]inetd
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] Re: Redux: Netsync + [X]inetd
- From: Alessandro Zummo <azummo-coldsync2 at towertech dot it>
- Date: Tue, 26 Feb 2002 10:25:47 +0100
- In-Reply-To: <15a901c1be7e$b12a7130$0101a8c0@ALEX>
- Organization: Tower Technologies
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
On 26-Feb-02 at 05:33:08,
Alex Tronin <at@urbis.net> wrote:
> 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?
--
- 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.