Re: (PM) syslog changes, require reboot?

Kevin Wormington (kworm@sofnet.com)
Wed, 3 Mar 1999 11:56:38 -0600

I believe you have to reboot the pm3 to get the log settings to take effect.
At least I had to reboot 3.8.2 a couple weeks ago when I changed from one
log host to another.

Kevin
Sofnet, Inc.
-----Original Message-----
From: Mike Greene <mikeg@rockisland.com>
To: portmaster-users@livingston.com <portmaster-users@livingston.com>
Date: Wednesday, March 03, 1999 11:51 AM
Subject: (PM) syslog changes, require reboot?

>Setting up the termination cause logging on our PM3's but not seeing any
>syslog messages being logged. This is what I've done on our PM3's and our
>loghost
>
>PM3 settings:
>--------------------------------
> Syslog Configuration Settings
>
> admin-logins: auth.info
> user-logins: auth.info
> packet-filters: auth.notice
> commands: disabled
> termination: local7.info
>
>LOG Host OS & Settings:
>--------------------------------
>BSDi 3.1
>/etc/syslog.conf
>local7.info /var/log/pm_term
>
>I restarted syslogd
>
>kill -HUP <syslogd-pid>
>
>/var/log/pm_term does exist and is writable by root.wheel
>
>I have NOT rebooted the terminal servers, looking at the docs it doesn't
>mention a reboot is neccessary, is it?
>
>
>- Mike
>
>------------------------------------------------
>Rock Island Communications, Inc. (360)-378-5884
>http://www.rockisland.com/ San Juan Islands, WA
>------------------------------------------------
>
>-
>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/>
>

-
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/>