From: reed@reedmedia.net (Jeremy C. Reed)
Subject: [TUHS] syslog (was Re: daemons are not to be exorcised)
Date: Wed, 21 Mar 2018 21:25:10 -0500 (CDT) [thread overview]
Message-ID: <alpine.NEB.2.20.1803212017420.25928@t1.m.reedmedia.net> (raw)
In-Reply-To: <20180322002246.GK9739@mcvoy.com>
On Wed, 21 Mar 2018, Larry McVoy wrote:
> On Wed, Mar 21, 2018 at 06:18:37PM -0600, Grant Taylor via TUHS wrote:
> > On 03/21/2018 03:16 AM, Jaap Akkerhuis wrote:
> > >I've been told that syslog was came in existence as a debugging aid for
> > >sendmai.
> >
> > I can't prove to the contrary. But that does seem a little extreme to me.
>
> For what it is worth, the syslog/sendmail connection rings a tiny bell for
> me, I can't prove it either, but I feel like there was some connection.
> Is Eric on the list?
Allman's logging was somewhat in 4BSD (4.0).
# -DLOG -- include log information. This is probably
# only useful on systems that include the logger.
delivermail was build with that flag.
But it used log.h which was not shipped in the version I have.
Some of the code has ifdef LOG and some doesn't.
2.79BSD (from McKusick's disk) which is later has logmsg(3) manual and
its corresponding syslog(8) daemon manual (both Feb 5 1981).
I cannot find those files online so here they are:
http://reedmedia.net/~reed/tmp-oicyi3t6984y/logmsg.3.txt
Notice that it says "12/31/79"
http://reedmedia.net/~reed/tmp-oicyi3t6984y/syslog.8.txt
But no code there for logmsg, initlog, nor syslog.
(Note that uucp's logent.c has a syslog() but that is different.)
McKusick said that syslog was first in 4.1c and official in 4.2.
In both places shipped with sendmail code.
He said it was one of the first applications to use sockets.
4.1c.1 version says "reads datagrams from an IPC port
(currently port 2222, for no good reason)"
It uses the /etc/syslog.conf file.
Allman's 4.1c.1 code says:
** This program implements a system log, implemented as the
** "/dev/log" mpx file on a pre-4.2bsd system or a port on
** a post-4.2bsd system.
I think this code is not in the dspinellis/unix-history-repo
(if you find it, please teach me how to find it).
The 4.1c code entirely changed api naming and some usage from
initlog("delivermail", 0, LOG_INDEP);
to
openlog("sendmail", LOG_PID);
(even though comments in syslog.h and syslog.c still mentioned initlog)
and from:
logmsg(LOG_INFO, "%s->%s: %ld: %s", From.q_paddr, To, MsgSize, statmsg);
to like:
syslog(LOG_INFO, "%s: message-id=%s", e->e_id, p);
even though syslog.c there defined logmsg() use and not syslog()
I may have overlooked but don't see any use of the code outside of
sendmail in 4.1c. The logger.c (without manpage) utility was included
in the sendmail source.
4.2 shipped two version of syslog(3) source code that no longer had
logmsg() api. (One in libc and one with sendmail.)
4.2 could started it with rc.local. While I didn't see other use of it,
a syslog.3 showed another example use:
openlog("serverftp", LOG_PID);
4.3 finally had lots of use (including in contrib): comsat, courier,
various mh daemons, nntpd, savecore, shutdown, lpd, telnetd, r services,
inetd, named, and much more. Even the date tool:
syslog(LOG_NOTICE, "set by %s", username);
next prev parent reply other threads:[~2018-03-22 2:25 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-20 1:26 [TUHS] daemons are not to be exorcised 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
2018-03-22 0:18 ` Grant Taylor
2018-03-22 0:22 ` Larry McVoy
2018-03-22 2:25 ` Jeremy C. Reed [this message]
2018-03-21 13:59 ` 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
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=alpine.NEB.2.20.1803212017420.25928@t1.m.reedmedia.net \
--to=reed@reedmedia.net \
/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).