From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] inetd/xinetd useflags
Date: Tue, 5 Jul 2005 19:26:26 -0400 [thread overview]
Message-ID: <200507051926.26393.vapier@gentoo.org> (raw)
In-Reply-To: <200507060017.25598@enterprise.flameeyes.is-a-geek.org>
On Tuesday 05 July 2005 06:17 pm, Diego 'Flameeyes' Pettenò wrote:
> 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.
you cant technically say it's a drop in since you have to redo the config
files, but for all intents and purposes, it is ... old school inetd suffered
from many issues (resource management being the foremost) so xinetd was
born ... it is the preferred inetd in Gentoo
> 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)
unrelated to anything in this e-mail
> 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".
personally i'd support a doxinetd func that would check to see if xinetd is
installed rather than go with a USE flag ...
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-05 23:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-05 22:17 [gentoo-dev] inetd/xinetd useflags Diego 'Flameeyes' Pettenò
2005-07-05 23:26 ` Mike Frysinger [this message]
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=200507051926.26393.vapier@gentoo.org \
--to=vapier@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