bill@fedeva.UUCP (Bill Daniels) (10/06/90)
I posted a similar request about a week or two ago. Just as luck would
have it my news machine went away for a couple of days right afterwards.
I have need to log operator messages via syslog(3) on a remote machine. I
am sure that this is possible because of the way the docs and headers read.
It seems however that Ultrix has coded up syslog() so that all messages go
to the local machine.
If there is a way around this I would be ever grateful to the one who shares
the insight. If there is not a workaround, could someone mail me the source
to syslog(3) and syslog(8) if it is publicly available?
Thanks for your help
bill daniels
--
bill daniels
federal express, memphis, tn
{zardoz!dhw68k,mit-eddie!premise}!fedeva!bill
bill@fedeva.UUCPgrr@cbmvax.commodore.com (George Robbins) (10/10/90)
In article <111@fedeva.UUCP> bill@fedeva.UUCP (Bill Daniels) writes: > I posted a similar request about a week or two ago. Just as luck would > have it my news machine went away for a couple of days right afterwards. > > I have need to log operator messages via syslog(3) on a remote machine. I > am sure that this is possible because of the way the docs and headers read. > It seems however that Ultrix has coded up syslog() so that all messages go > to the local machine. The Ultrix syslog seems to be able to capture and display remote syslog messages, but doesn't seem to be able to direct it's own messages to another system. Other people have claimed that the BSD 4.3 syslog stuff is easy to get working with Ultrix, but I haven't tried it (yet). Note that having Ultrix syslog capture messages originating from a Sun system results in a ugly syslog file, apparently there is some format divergence. -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing: domain: grr@cbmvax.commodore.com Commodore, Engineering Department phone: 215-431-9349 (only by moonlite)