From: Henti Smith <bain@tcsn.co.za>
To: Daniel <dragonheart@tpg.com.au>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] xinetd
Date: Tue, 20 May 2003 07:49:14 +0200 [thread overview]
Message-ID: <20030520074914.26f84f4d.bain@tcsn.co.za> (raw)
In-Reply-To: <200305200843.30774.dragonheart@tpg.com.au>
On Tue, 20 May 2003 08:43:25 +0930
Daniel <dragonheart@tpg.com.au> wrote:
> > Just thinking it would be nice to have a xinetd USE flag which causes all
> > daemons to configure themselves as xinetd services... Is there any reason
> > why this would be a bad idea or why it doesn't exist?
>
> Sounds great to me. I run a lot of services that don't get used all that
> often. When I get a bit more time I'll double check some of the scripts I've
> written and add a few ebuilds.
>
> I'm assuming this is going to be a buy-in service like everything else in
> gentoo.
>
> great idea,
Just as long as it's a virtual USE flag so I can use tcpserver instead of xinetd ;P
Henti
--
gentoo-dev@gentoo.org mailing list
prev parent reply other threads:[~2003-05-20 6:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 11:09 [gentoo-dev] xinetd Luke-Jr
2003-05-19 23:13 ` Daniel
2003-05-20 5:49 ` Henti Smith [this message]
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=20030520074914.26f84f4d.bain@tcsn.co.za \
--to=bain@tcsn.co.za \
--cc=dragonheart@tpg.com.au \
--cc=gentoo-dev@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