[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[coldsync-hackers] Re: What goes in inetd.conf?
- To: coldsync-hackers at lusars dot net
- Subject: [coldsync-hackers] Re: What goes in inetd.conf?
- From: Alessandro Zummo <azummo-coldsync2 at towertech dot it>
- Date: Tue, 03 Sep 2002 19:02:46 +0100
- In-Reply-To: <Pine.BSI.4.44.0209031232360.25638-100000@mail.his.com>
- Organization: Tower Technologies
- Reply-To: coldsync-hackers at lusars dot net
- Sender: owner-coldsync-hackers at lusars dot net
On 03-Set-02 at 17:40:06,
Andrew Arensburger <arensb+CShackers@ooblick.com> wrote:
> On Tue, 3 Sep 2002, Alessandro Zummo wrote:
>> On 03-Set-02 at 15:50:06,
>> Andrew Arensburger <arensb+CShackers@ooblick.com> wrote:
>>> 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...?
> Shouldn't be a problem (after all, the same problem appears with
> ftp, POP, IMAP, etc.)
> Just specify "nowait" in /etc/inetd.conf, so that inetd can fork
> the process, and listen for a new incoming connection.
well, ok.. that implies the use of inetd and stdin/stdout as communication
channel for coldsync. I have to try if it works reliaby....
--
- 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.