On Fri, 27 Dec 2002 12:17:36 -0600, [EMAIL PROTECTED] (Michael Weber) wrote:
>I have a script that listens on a port for a connection, receives some >data over that connection, and writes it to a file. > >This works, but it takes up CPU cycles, RAM etc. when it waits. I am >trying to get the script to use xinetd instead. That way the tcp daemon >will launch it when needed and let it die when it's done. > >What I get when xinetd runs it,however, is "bind: Address already in >use". > >Here's the script. (Fervent readers of Ellie Quigley will recognize it >right off as a modified copy of Example 18.21." I'm just hazarding a quess here, but I just saw a similar discussion about inetd. The gist was that when you use inetd (or maybe in your case xinetd), the program just needs to read and write to STDIN and STDOUT. xinetd takes care of the socket. -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
