On Jul 24, Magnus Holmgren <[EMAIL PROTECTED]> wrote:
> Anyway, you have proposed that all superserver packages provide their own
> update-inetd implementation, which is fine and simple enough, except that
> it's not clear how the configuration would be transferred when one
> superserver is rep
Magnus Holmgren <[EMAIL PROTECTED]> writes:
> Perhaps not, but the possibility to just drop a configuration snippet in
> a ".d" directory, instead of having to mess with a single configuration
> file, is appealing IMHO. Russ: May I ask why you don't like xinetd?
A bad taste left over from Red Hat
On Monday 23 July 2007 18:47, Marco d'Itri wrote:
> On Jul 23, Magnus Holmgren <[EMAIL PROTECTED]> wrote:
> > Packages containing servers that can be started from inetd should all
> > provide an xinetd configuration file in /etc/xinetd.d. They will
> > instantly work with
>
> Way too much work, and
On Mon, Jul 23, 2007 at 05:45:31PM +0200, Magnus Holmgren wrote:
> A legitimate question is whether the xinetd configuration format is a good
> format. Are there, or will there be, even more "extended" inetd:s?
apt-cache search shows at least:
inetutils-inetd - Internet super server
micro-inet
> However, even more importantly than the discussion of possible solutions,
> we need an implementation. If you have a solution, please *implement* it
> (and in a way that doesn't make large parts of Debian buggy, which means
> being backwardly compatible) and I bet you'll be able to build a cons
On Jul 23, Magnus Holmgren <[EMAIL PROTECTED]> wrote:
> Packages containing servers that can be started from inetd should all provide
> an xinetd configuration file in /etc/xinetd.d. They will instantly work with
Way too much work, and "better support for xinetd" is not something
important enoug
Magnus Holmgren <[EMAIL PROTECTED]> writes:
> Boy, what an old bug!
> This has been discussed some times[1], but no conclusion reached. I'd
> like to suggest (again, probably) the following:
As near as I can tell, the reason why no conclusion has been reached is
because no one has written the co
Boy, what an old bug!
This has been discussed some times[1], but no conclusion reached. I'd like to
suggest (again, probably) the following:
Packages containing servers that can be started from inetd should all provide
an xinetd configuration file in /etc/xinetd.d. They will instantly work with
8 matches
Mail list logo
