Re: ITP: inetdconf
On Mon, 9 Oct 2000, Anthony Towns wrote:
> On Mon, Oct 09, 2000 at 02:03:31AM +0900, Atsushi KAMOSHIDA wrote:
> > > If that is the case, you should probably configure a
> > > conflict between your package and xinetd (any version).
> > OK. In future, I want to support /etc/xinetd.conf.
> FWIW, I'm currently working on a new update-inetd that should support
> xinetd as well as netkit-inetd/whatever. It's a ways off being done
> yet though. It'll probably have a --list argument of some sort that'll
> list current services so you won't have to parse inetd.conf yourself.
Yes, please. Will this be a solution for all those broken /etc/init.d/*
scripts that grep /etc/inetd.conf to determine whether a daemon should be
started or not?
For example, look at this snippet from /etc/init.d/exim :
# Exit if exim runs from /etc/inetd.conf
if grep -q "^ *smtp" /etc/inetd.conf; then
This is not useable for people who use xinetd, like me.
Another question: how long will it be before netbase depends on
"netkit-inetd | xinetd", allowing me to remove inetd alltogether?
qn-195-66-31-144: 1:10am up 37 days, 1:26, 9 users, load average: 1.48, 1.46, 1.45