Isn't irritating when people post things to the list answered only days
earlier?
Sorry.
As most people suggested, I created the /etc/syslog.auth and added the
remote host. To verify it was working, I used the syslogd with (-d) flag to
verify I was receiving messages. However, when I run the
/usr/sbin/syslogd command without flags, nothing is written to the file
designated in the /etc/syslog.conf file. Any suggestions?
Thanks for the replies from
John Speno
Whitney Latta
Gary George
Daniel Monjar
Brian Hill
Tom Webster
Here are some :
>From Whitney Latta
A feature was added to syslogd in DU-V4.0d to prevent a system from
being swamped with remote syslog requests. You must create and add
"authorized" remote syslogd hosts to the file "/etc/syslog.auth".
Syntax for the file is simply one remote hostname to each line.
To verify the syslogd is doing the right thing, invoke it manually with
the "-d" (debug) flag. If all is well, you will see the remote host
entries and their logfiles listed in the output.
NOTE: syslogd in 4.0d possesses a bug that causes syslogd to core-dump
IF the /etc/syslog.auth file contains over 23 lines. A patch has been
made available for this.
Hope this helps.
--------------------------
>From John Speno:
Yes. This question seems to be a popular one these days. In fact, it was
just
asked and answers on this very list two days ago. :-)
See your release notes for 4.0d, section 4-14 I believe.
Then call Digital Software support and rag on them because the syslogd in
4.0d is not documented in the man pages, and it's broken. Seriously.
I'll forward you some recent summaries from this list.
------------------
>From Gary George:
With 4.0D there's a new piece of security: file /etc/syslog.auth.
Enter the dns names of the remote sites that you're allowing to write
into syslog.
And for heaven's sake, close up the file permissions. Only syslogd
should be able to write to the log files.
----------------------
Received on Thu Jul 23 1998 - 17:50:44 NZST