From: "Diego 'Flameeyes' Pettenò" <flameeyes@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] inetd/xinetd useflags
Date: Wed, 6 Jul 2005 00:17:18 +0200 [thread overview]
Message-ID: <200507060017.25598@enterprise.flameeyes.is-a-geek.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1789 bytes --]
Time for cleanups in Gentoo/FreeBSD.. we already disabled inetd building in
our latest ebuilds, but that isn't exactly sorted out for a reason: I don't
know how to deal with xinetd.
Let me summarize:
inetd is the old-unix-insecure implementation that it's usually used.
xinetd is a (drop-in?) replacement for it which is now used by quite everyone
who wants an inetd-style daemons.
Now the problem is: I don't really know how inetd/xinetd works, I just used
them some time ago to have a cvs pserver, but that was a very long time ago.
Right now, we have a couple of packages with xinetd useflag, one with inetd
useflag, and others which doesn't care and just installs the configuration
file unconditionally:
flame@enterprise ~ $ grep inetd devel/gentoo-x86/profiles/use.*
devel/gentoo-x86/profiles/use.local.desc:dev-db/firebird:inetd - If you want
inetd version instead of a superserver (daemon)
devel/gentoo-x86/profiles/use.local.desc:net-ftp/proftpd:xinetd - Enable
support for starting from xinetd
devel/gentoo-x86/profiles/use.local.desc:net-ftp/vsftpd:xinetd - Add support
for running under xinetd
devel/gentoo-x86/profiles/use.local.desc:net-mail/qpopper:xinetd - If you want
inetd version instead of standalone
devel/gentoo-x86/profiles/use.local.desc:net-misc/linux-identd:xinetd - Use
xinetd instead of the initscript
flame@enterprise ~ $ ls /etc/xinetd.d/
cups-lpd cvspserver svnserve swat telnetd
so what we should do?
Add a global xinetd useflag and a doxinetd function to add/remove the
installed config files?
Yeah i know they aren't so big.. but "the less, the best".
--
Diego "Flameeyes" Pettenò
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-07-05 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 22:17 Diego 'Flameeyes' Pettenò [this message]
2005-07-05 23:26 ` [gentoo-dev] inetd/xinetd useflags Mike Frysinger
2005-07-06 3:34 ` Donnie Berkholz
2005-07-06 11:55 ` Stelian Ionescu
2005-07-06 9:23 ` Diego 'Flameeyes' Pettenò
2005-07-06 13:36 ` Aron Griffis
2005-07-06 13:55 ` Diego 'Flameeyes' Pettenò
2005-07-06 14:17 ` Mike Frysinger
2005-07-06 14:32 ` Diego 'Flameeyes' Pettenò
2005-07-06 14:58 ` Mike Frysinger
2005-07-06 18:20 ` Maurice van der Pot
2005-07-06 18:58 ` Aron Griffis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200507060017.25598@enterprise.flameeyes.is-a-geek.org \
--to=flameeyes@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox