Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 22 Aug 1996 15:28:09 -0700
From:      Doug Wellington <>
To:        "Jon T. Ilko" <>
Subject:   Re: Creating an inetd server.
Message-ID:  <>
In-Reply-To: "Your message of Thu, 22 Aug 1996 14:08:26 GMT." <>

Next in thread | Previous in thread | Raw E-Mail | Index | Archive | Help
>  I'm trying to create a simple server that
>will run from inetd on port 1211.

You're working too hard!  ;-)  When you use inetd to control
access to a process, all you need to do in that process is
to read from stdin and write to stdout.  Don't worry about
binding to a socket and all that, it's what inetd does for
a living...  (One nice thing about it is that you can test
your server without inetd - just fire it up from the command
line and interact with it...)

One of the cardinal rules with reading is to make sure you
explicitly specify the size of your buffers!  Don't let anyone
send you a huge input line and overrun your buffers...


Doug Wellington
System and Network Administrator
US Geological Survey, Tucson, AZ Project Office

According to proposed Federal guidelines, this message is a "non-record".
Hmm, I wonder if _everything_ I say is a "non-record"...?

FreeBSD and Apache - the best real tools for the virtual world!
Check out and

Just say NO to Netscape Navigator!

Want to link to this message? Use this URL: <>