home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!sun-barr!cs.utexas.edu!ut-emx!ibmchs!auschs!awdprime.austin.ibm.com!eric
- From: eric@austin.ibm.com (Eric Carpenter)
- Newsgroups: comp.bugs.4bsd
- Subject: syslogd problem
- Message-ID: <1992Sep8.144857.22346@awdprime.austin.ibm.com>
- Date: 8 Sep 92 14:48:57 GMT
- Sender: news@awdprime.austin.ibm.com (USENET News)
- Reply-To: eric@thelake.austin.ibm.com
- Organization: IBM Austin
- Lines: 39
- Originator: eric@thelake.austin.ibm.com
-
-
- Can anyone give me some insight into this situation?
-
- If machineA has the following syslog.conf file:
-
- user.alert /tmp/alert
- user.info /tmp/info
- user.alert @machineB
- user.info @machineB
-
- and machineB has the following syslog.conf file:
-
- user.info /tmp/info
- user.alert /tmp/alert
-
- Then when machineA does a syslog of an alert priority, 2 alert entries
- are put in the /tmp/alert file of machineB. Shouldn't there only be 1?
- There is also 2 entries in the /tmp/info file of machineB, but this I
- can understand (one for the alert and one for the info). When I comment
- out the .info entries from machineA's syslog.conf file, the problem goes
- away.
-
- user.alert /tmp/alert
- #user.info /tmp/info
- user.alert @machineB
- #user.info @machineB
-
- The same thing occurs on every platform that I tried it on.
-
- Thanks for any help..
-
-
-
-
- --
- ___________________________________________________________________
- | Eric Carpenter | inet: eric@thelake.austin.ibm.com |
- | PSP, Austin | vnet: ECARP at AUSTIN |
- | Dept. D54 3b-17/905 | phone: (512)838-3277 -- T/L 678 |
-