Path: utzoo!attcan!uunet!cs.utexas.edu!sun-barr!apple!agate!agate!rusty From: rusty@belch.Berkeley.EDU (rusty wright) Newsgroups: comp.unix.ultrix Subject: Re: Error Logging Requirements Message-ID: Date: 14 Nov 90 18:41:03 GMT References: <9011061336.AA19738@decpa.pa.dec.com> <1990Nov12.082526.26969@ircam.ircam.fr> Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: University of California Berkeley Lines: 9 In-Reply-To: mf@ircam.ircam.fr's message of 12 Nov 90 08:25:26 GMT Another thing that I'd like to see is some sort of version number in the packets. Client programs should be able to query the syslog server and send it log packets in the appropriate format. Or any new stuff could be at the end of the packet and old servers could simply ignore it. Alternatively, they could send it to a syslog server on the local machine and its config file could say to send it to another syslog server, possibly with reformatting if it's a different version. The fact that the 4.2 and 4.3 BSD syslogs don't work together is just bad design.