[Initng] IRC meeting
Eric MSP Veith
eveith at wwweb-library.net
Sun Dec 2 20:47:02 GMT 2007
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Sunday 02 December 2007, "Rob Ubuntu Linux"
<rob.ubuntu.linux at googlemail.com> wrote:
> On Dec 2, 2007 4:35 PM, Eric MSP Veith <eveith at wwweb-library.net> wrote:
> > The tcp_wrappers aren't that commonly used that they are more than a
> > nice exciter in my eyes.
>
> They were very useful at one time, before Openssh really took off.
> But and this is typical, Wietse implemented the access stuff as a
> library, and that code is probably on every linux distro; even if it's
> fewer systems are offering services in that way.
And...? I mean: You said it's nice and fits nice with a system, but you also
admit that it isn't used by a large number off applications; so where's the
point?
> Guessing you don't really know why DJB didn't use the syslog ABI. If
> he's passing all the info out and then re-logging it via syslog(3) it
> seems more complex not less. There's probably some doc by DJB
> somewhere that gives a rationale.
Er... AFAIK he just states that multilog(8) is the better solution in his
eyes; and remember that daemontools were designed long before syslog-ng. It
allows a fine-grained configuration for alot of services, has built-in log
rotation and stuff like that. And the configuration is really
straightforward and simple. You needed to cope with a bunch of utilities if
you used syslog, but as I said, this changed, and the need for multilog
isn't that great anymore.
DJB gave its syslog interface as a bonus for people who want to stick with
an already working syslog environment. It is an "you could also do it that
way, if you want" solution, and not yet another inconvenien re-invetion of
the wheel.
But no, I haven't read any paper where he explicitly states his reasons to
design multilog.
I'm btw still interested in the paper you were writing about. :-)
However, I think this discussion is far away from the main topic. I,
personally, continue to think that a simple logging facility that fetches
messages from stderr/stdin is a really nice thing to have in InitNG, not
more, not less. :-) If InitNG would be able to create a pipe to a
separately monitored daemon, like daemontools do, this would also be nice.
Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
iD8DBQFHUxnGfkUtd7QNU/sRAo1qAKCPCuVTS8K6FHELiWCvi8iMW0zKiwCfanwF
lEGtE69W7aS2sM6pmpJSGeE=
=7n3p
-----END PGP SIGNATURE-----
More information about the upstart-devel
mailing list