Re: (PM) syslog changes, require reboot?

John W Baxter (jwblist@olympus.net)
Wed, 3 Mar 1999 20:32:19 -0800

At 11:09 -0700 3/3/99, Craig Baird wrote:
> I got mine set up the other day. Make sure you have your loghost set in
> the PM3. I think you have to reboot if you change it. In other words,
> if you do a
>
> set loghost <the IP of your log host>
> save all
>
> Then I think you have to reboot to get it to take effect. I don't know
> if you have to reboot after doing a 'set syslog ...', however. Mine was
> already set up, so I really didn't have to do any reboots.

The other day, I wasn't sure about changing the set syslog xxx
values...now I've remembered an "incident", and I believe the
following is correct

a loghost change requires a reboot (this I was sure of before)

a change to the details using set syslog does not.

[We have a PM2e with some widgets attached, along with 20 modems.
When I turned on termination logging, the ports with the widgets
started flooding the syslog with repeated termination reports. I was
able to stop the Sorcerer's Apprentic effect without rebooting.]

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