BSDi uses the reverse of the -r for accept remote logic: syslogd -l
says local connections only (that's elle for local, not one for one machine).
But, since some transactions are being logged, the problem lies
elsewhere...probably with what /etc/syslogd.conf is doing with the
facility/priority you are using for the messages. I decided not to
mess with that, and used a pair I hoped would work:
admin-logins: auth.info
user-logins: auth.info
...
termination: syslog.info
(It then turned out that both auth.info and syslog.info are going to
the "messages" log.)
Someday, I'll have to learn /etc/syslogd.conf (unless we switch to
Linux first).
--JOhn
-- John Baxter jwblist@olympus.net Port Ludlow, WA, USA Give a man a fish and you feed him for a day. Teach him to fish, and you get rid of him for the weekend. - To unsubscribe, email 'majordomo@livingston.com' with 'unsubscribe portmaster-users' in the body of the message. Searchable list archive: <URL:http://www.livingston.com/Tech/archive/>