From: jaapna@xs4all.nl (Jaap Akkerhuis)
Subject: [TUHS] daemons are not to be exorcised
Date: Wed, 21 Mar 2018 10:16:49 +0100 [thread overview]
Message-ID: <76E7D09E-023B-4A29-ACCD-AF9ED425EE5F@xs4all.nl> (raw)
In-Reply-To: <20180321023125.GC6850@thunk.org>
> On Mar 21, 2018, at 3:31, Theodore Y. Ts'o <tytso at mit.edu> wrote:
>
> There are also ways in which Unix is just simply deficient. For
> example, take syslog. It's simple, sure, but it has an extremely
> simple structure, and it's not nearly flexible enough for more
> sophisticated use cases. As a result, *many* commercial Unix systems
> have tried reinventing an event logging system which had more structure.
I've been told that syslog was came in existence as a debugging aid for sendmai.
jaap
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180321/d5eef898/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 267 bytes
Desc: Message signed with OpenPGP
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20180321/d5eef898/attachment.sig>
next prev parent reply other threads:[~2018-03-21 9:16 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 1:26 A. P. Garcia
2018-03-20 1:40 ` Dave Horsfall
2018-03-20 1:47 ` maxigas
2018-03-20 4:23 ` Grant Taylor
2018-03-20 4:24 ` Steve Nickolas
2018-03-20 4:40 ` Grant Taylor
2018-03-20 5:19 ` A. P. Garcia
2018-03-21 2:31 ` Theodore Y. Ts'o
2018-03-21 3:20 ` Larry McVoy
2018-03-21 4:30 ` Warner Losh
2018-03-21 4:52 ` Grant Taylor
2018-03-21 9:16 ` Jaap Akkerhuis [this message]
2018-03-22 0:18 ` Grant Taylor
2018-03-22 0:22 ` Larry McVoy
2018-03-22 2:25 ` [TUHS] syslog (was Re: daemons are not to be exorcised) Jeremy C. Reed
2018-03-21 13:59 ` [TUHS] daemons are not to be exorcised Clem Cole
2018-03-21 14:18 ` Paul Winalski
2018-03-21 15:15 ` Warner Losh
2018-03-21 15:45 ` Andy Kosela
2018-03-21 15:49 ` Warner Losh
2018-03-22 0:28 ` Grant Taylor
2018-03-20 6:32 ` Andy Kosela
2018-03-20 12:31 ` Nemo
2018-03-20 17:48 ` Paul Winalski
2018-03-20 17:56 ` George Michaelson
2018-03-20 18:04 ` Dan Cross
2018-03-20 18:24 ` Bakul Shah
2018-03-20 18:46 ` Clem Cole
2018-03-20 19:10 ` Bakul Shah
2018-03-20 19:55 ` Dan Cross
2018-03-20 19:56 ` Tim Bradshaw
2018-03-20 21:12 ` A. P. Garcia
2018-03-20 21:40 ` Andy Kosela
2018-03-21 6:32 ` Wesley Parish
2018-03-20 20:14 ` Warren Toomey
2018-03-20 20:25 ` Paul Winalski
2018-03-20 21:15 ` Clem Cole
2018-03-20 21:09 ` Clem Cole
2018-03-20 18:53 ` Toby Thain
2018-03-20 19:24 ` Nemo Nusquam
2018-03-21 12:10 ` emanuel stiebler
2018-03-25 19:56 ` emanuel stiebler
2018-03-26 9:44 ` George Michaelson
2018-03-26 12:38 ` emanuel stiebler
2018-03-20 21:32 Nelson H. F. Beebe
2018-03-21 14:17 Noel Chiappa
2018-03-21 15:03 ` Clem Cole
2018-03-21 16:18 ` Arthur Krewat
2018-03-21 17:28 ` Paul Winalski
2018-03-21 17:33 ` George Michaelson
2018-03-21 17:50 ` Arthur Krewat
2018-03-21 19:49 ` A. P. Garcia
2018-03-21 19:37 ` Paul Winalski
2018-03-21 17:34 ` Larry McVoy
2018-03-22 2:24 ` Dave Horsfall
2018-03-21 17:39 ` WIlliam Cheswick
2018-03-21 17:52 ` Arthur Krewat
2018-03-21 17:56 ` Nemo
2018-03-21 18:01 ` Larry McVoy
2018-03-21 18:04 ` Dan Cross
2018-03-21 19:56 ` Clem Cole
2018-03-21 20:13 ` Paul Winalski
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=76E7D09E-023B-4A29-ACCD-AF9ED425EE5F@xs4all.nl \
--to=jaapna@xs4all.nl \
/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;
as well as URLs for NNTP newsgroup(s).