*BSD News Article 92882


Return to BSD News archive

Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.wildstar.net!news.ececs.uc.edu!newsfeeds.sol.net!europa.clark.net!cpk-news-hub1.bbnplanet.com!news.bbnplanet.com!ais.net!uunet!in3.uu.net!199.232.240.7!kayrad.ziplink.net!rtfm.ziplink.net!mi
From: mi@ALDAN.ziplink.net..remove-after-`net' (Mikhail Teterin)
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: syslogd watching other machine(s)
Date: 6 Apr 1997 05:19:02 GMT
Organization: Aldan at Newton Upper Falls
Lines: 24
Message-ID: <5i7bo6$o1t$1@kayrad.ziplink.net>
Reply-To: mi@ALDAN.ziplink.net..remove-after-`net'
NNTP-Posting-Host: rtfm.ziplink.net
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Newsreader: knews 0.9.8
Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38531

Hi! I have several Unix machines (FreeBSD and Irix), which I'd like
to set up to watch for other machine's log entries. Say, rtfm will
log aldan's messages and aldan will log rtfm's messages.

Unfortunately, simply modifying /etc/syslogd.conf to send things to
@another_host on both system, causes cascades of messages: rtfm sends
the message to aldan, which bounces it back to rtfm right away.
Then, rtfm passes it to aldan again, and so on... syslogd has to be
restarted...

The only solution I see for this, is to run two syslogd-s on each machine.
With different config files. One will send local messages out (run in
"safe" mode), another one -- logging remote messages.

Can anyone think of a single process solution? Thanks!

I think, syslogd has to have an option to operate in intelligent
mode -- recognise when the incoming message is about the localhost
and not log it (or, at least, not propagate it).

	-mi

-- 
	"Windows for dummies"