EWR@XX.LCS.MIT.EDU (Betsy Ramsey) (04/23/87)
There were some messages earlier that pointed out that you can disable some OPCOM messages on the console by using commands $ DEFINE/USER SYS$COMMAND OPA0 $ REPLY/DISABLE=whatever This also appears to prevent the messages from appearing in the OPERATOR.LOG file. Is there some way to inhibit them on the console but still get them in the OPERATOR.LOG file? What I really want to do is get my SECURITY messages logged somewhere other than the console. If I could log them to the file of my choice, that would be nice. Any way to do that? Betsy Ramsey American Mathematical Society Providence, RI 401-272-9500 Arpa: EWR@XX.LCS.MIT.EDU -------
SteveG@MAINE.BITNET (Steve E. Goldsmith) (04/28/87)
To stop the security messages from going to OPA0: I use: SET TERM OPA0:/NOBROAD </PERM; I dont remember offhand if PERM is required>. This of course turns off all messages to OPA0:, but doesnt stop them from showing up in operator.log. We run several uVaxen here and couldnt have OPA0: keep breaking in with security messages on the workstations, so thats how I solved the problem. Hope it helps. /Steve +----------------------------------------------------------------------+ | Steve E. Goldsmith | | UMECS Systems Manager | | CSNEWS Operations Staff | | | | STEVEG@MAINE.BITNET | | STEVEG@MECAN1.BITNET University Of Maine | | STEVE@BITNIC.BITNET Computer Science Department | | STEVE%OPUS.MAINE_CS@MECAN1.BITNET 111 Neville Hall | | STEVE%MILO.MAINE_CS@MECAN1.BITNET Orono, Maine 04469 | | (207) 581-3945 | +----------------------------------------------------------------------+