[2848] in SIPB-AFS-requests
Re: replaced syslogd on sipb server machines
daemon@ATHENA.MIT.EDU (mhpower@MIT.EDU)
Mon Sep 1 03:21:43 1997
From: mhpower@MIT.EDU
To: rtfm-maintainers@MIT.EDU, charon-maintainers@MIT.EDU, sipb-afsreq@MIT.EDU,
anxiety-maintainers@MIT.EDU
Date: Mon, 01 Sep 1997 03:21:28 EDT
>It's possible that some Ultrix software, such as timed, ought to be
>recompiled so that uses the correct syslog client code.
I added the changes for compatibility with the old Ultrix syslog code
(the changes written by jtkohl in 1991) to the current syslogd code,
and installed the modified version on the three Ultrix servers.
> ... I haven't yet attempted to generate data with
> internal NUL characters to see whether this is an actual problem
> on non-Linux systems.
I wrote a test program that verified that this is an actual problem.
Other issues:
Sending syslogs from perl scripts was not working. This is because
perl writes its data to udp port 514, not to /dev/log. I modified
/usr/local/lib/perl/syslog.pl to write to /dev/log instead. I haven't
yet changed Syslog.pm (for perl 5), since I don't think we have any
perl 5 scripts that call syslog. Also, I haven't tried to make it
possible for perl 4 on Solaris to write syslog data to a STREAMS file.
I couldn't find any perl scripts on dandelion-patch that use syslog.
>It dumped core in strncat. The reason for this is that the Solaris
>implementation of strncat is broken. ...
> ... so I may end up just changing the syslogd source
>code to work around the problem.
I rebuilt syslogd for Solaris so that it uses the NetBSD strncat; the
new version has been installed and started running on dandelion-patch.
Matt
