[gentoo-dev] Re: xinetd configuration

[gentoo-dev] Re: xinetd configuration

[Andreas Voegele]

> Thus the conversion from /etc/xinetd.conf to /etc/xinetd.conf will
                           ^^^^^^^^^^^^^^^^
That should be /etc/inetd.conf, of course.

-- 
Bye,
Andreas

Re: [gentoo-dev] xinetd configuration

[Jerry A!]

On Sat, Nov 10, 2001 at 01:17:55AM +0100, Andreas Voegele wrote:
: Hi!
:
: On Mandrake systems the package management system can add and remove
: services from the xinetd configuration without problems since the file
: /etc/xinetd.conf includes all files that were put into the directory
: /etc/xinetd.d by the installed packages.
:
: I'm wondering why Gentoo does not use such a scheme.
:
: It may be a security risk to enable all installed services by default
: but then /etc/init.d/xinetd shouldn't create /etc/xinetd.conf from

It may be easier to just have a xinetd.conf with the only entry being
"includedir /etc/xinetd.d".  Then you create a singular .conf file for
each service.  Each portage that needs a xinetd entry simply installs
its conf file into /etc/xinetd.d.  This is how pam/pam.d is currently
setup.

        --Jerry

name:  Jerry Alexandratos         ||  Open-Source software isn't a
phone: 571.275.9795               ||  matter of life or death...
email: jerry@thehutt.org          ||  ...It's much more important
                                  ||  than that!

[gentoo-dev] Re: xinetd configuration

[Andreas Voegele]

Jerry Alexandratos writes:

> : On Mandrake systems the package management system can add and
> : remove services from the xinetd configuration without problems
> : since the file /etc/xinetd.conf includes all files that were put
> : into the directory /etc/xinetd.d by the installed packages.
> :
> : I'm wondering why Gentoo does not use such a scheme. [...]

> It may be easier to just have a xinetd.conf with the only entry
> being "includedir /etc/xinetd.d".  Then you create a singular .conf
> file for each service.  Each portage that needs a xinetd entry
> simply installs its conf file into /etc/xinetd.d.  This is how
> pam/pam.d is currently setup.

That's what I meant. Mandrake puts the default values and the
includedir statement into /etc/xinetd.conf. Everything else goes into
the directory /etc/xinetd.d.

But in contrast to Mandrake it might be good to restrict the access to
the localhost for security reasons, eg by using "only_from=localhost"
as a default value or by putting a corresponding rule into
/etc/hosts.deny.

-- 
Andreas