On Mon, 2 Dec 2002 netbsd99@sudog.com wrote:

> xinetd is evil. It doesn't do the right thing when forking off daemons.
> stderr ends up being mapped to the socket--if the application isn't
> designed with xinetd's handling of stderr in mind, a single error
> message can disrupt protocols in a very messy fashion. :-)

What is an example?

> ..  err ..  I forget: does inetd do this too?

pop3 server lauched via inetd as shown with fstat(1):

root     vm-pop3d    1336    0* internet stream tcp c08a9178 127.0.0.1:110 <-> 127.0.0.1:63775
root     vm-pop3d    1336    1* internet stream tcp c08a9178 127.0.0.1:110 <-> 127.0.0.1:63775
root     vm-pop3d    1336    2* internet stream tcp c08a9178 127.0.0.1:110 <-> 127.0.0.1:63775

> Also, xinetd is unecessarily complex to configure.

I agree (but xinetd does offer many options not available in inetd).

Anyways, there are many packages I don't use in pkgsrc -- and some
packages in pkgsrc that I don't agree with, but I am sure that someone
else finds them useful for some reason or another.

   Jeremy C. Reed
   http://bsd.reedmedia.net/