sasaki@HARVARD.HARVARD.EDU (Marty Sasaki) (10/17/85)
Is there any way to set things up so that security alarms go to a file instead of a terminal? There are a few files and devices that I would like to monitor, but having to have a terminal (hardcopy) logged in all of the time is almost impossible to do right now. Thanks in advance. Marty Sasaki (sasaki@harvard.arpa) (sometimes sasaki@harvard.harvard.edu works)
AWalker@RED.RUTGERS.EDU (*Hobbit*) (10/17/85)
Since all the alarms go into the operator log as well as enabled terminals, isn't that sufficient? On our local vax, in our equivalent of systartup.com, I did $def/us sys$command opa0: $reply/disable=(security,<some other frobs>) which saves some paper. _H* -------
info-vax@cca.UUCP (10/18/85)
From: sasaki@harvard.harvard.edu (Marty Sasaki) Is there any way to set things up so that security alarms go to a file instead of a terminal? There are a few files and devices that I would like to monitor, but having to have a terminal (hardcopy) logged in all of the time is almost impossible to do right now. Thanks in advance. Marty Sasaki (sasaki@harvard.arpa) (sometimes sasaki@harvard.harvard.edu works)
info-vax@cca.UUCP (10/18/85)
From: *Hobbit* <AWalker@red.rutgers.edu> Since all the alarms go into the operator log as well as enabled terminals, isn't that sufficient? On our local vax, in our equivalent of systartup.com, I did $def/us sys$command opa0: $reply/disable=(security,<some other frobs>) which saves some paper. _H* -------