[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    RE: [BusyBox] xinetd?
From:       Dan Kegel <dkegel () ixiacom ! com>
Date:       2003-01-28 22:39:03
[Download RAW message or body]

The drawback with your suggestion is that it's different
from what people expect.  I prefer to go with something
that feels standard to users, to reduce their learning curve.
At the same time, I can't use inetd.conf, as that makes 
scripting too hard.  I can't imagine it'd be hard to make
an implementation of xinetd that was svelte enough to qualify
for busybox.

'Nuff said.  We're not convincing each other, and it doesn't matter
that much anyway.
- Dan

-----Original Message-----
From: Russ Dill
To: Allan (pls reply to  ""list only)
Cc: Dan Kegel; busybox
Sent: 28.01.2003 11:39
Subject: Re: [BusyBox] xinetd?

On Mon, 2003-01-27 at 17:25, Allan (pls reply to list only) wrote:
> Dan Kegel wrote:
> > [...merciless snip...] 
> > So it might be nice for busybox to support xinetd,
> > where each service is controlled by a file in /etc/xinetd.d.
> > Then our start and stop scripts can just create and
> > destroy files in that directory, which is a lot easier
> > to script.
> 
> An alternative is to support a "-D" option present in some linux
> versions of inetd.  The action of "inetd -D /etc/inet.d" is to append
> the contents of each file (ftw depth=1) to the /etc/inetd.conf file
read
> in.
> 
> The benefit here is that little additional code would be necessary,
and
> yield the result you're looking for, but would be compatible with few
> linux variants.

I thought about it some more, and I still don't see the point. If you
want a user editable file, make a /etc/inetd.d/inetd.conf where users
can put the services they want. When a user wants to restart notify
inetd of their changes, they run /etc/init.d/inetd restart and it
combines all the files, and sends -HUP to inetd. KISS

-- 
Russ Dill <Russ.Dill@asu.edu>

[prev in list] [next in list] [prev in thread] [next in thread]