test

SunScreen 3.1 Reference Manual

Configuring Log Event Limiters

The log limiters are controlled by LogSeverity variables as previously introduced. Each such variable contains the following items:

You can only configure the LogSeverity variables using the command line interface (see Appendix B, Command-Line Reference). You configure group-Screen installations on the primary Screen.

The following is an example of what you would type to display the global global log limiter, while logged in to the primary Screen:


admin% ssadm -r primary edit Initial
edit> vars print name=LogSeverity
NAME="LogSeverity" ENABLED VALUE="INFO"DESCRIPTION="global log severity limit" ...

The following is an example of what you would type to display the global log limiter for authentication events, while logged in to the primary Screen:


admin% ssadm -r primary edit Initial
edit> vars print prg=auth
name=LogSeverity
PRG="auth" NAME="LogSeverity" ENABLED VALUE="INFO"
 DESCRIPTION="global log severity limit, authentication"
...

The following is an example of what you would type to log more (debugging) information on a particular Screen for authentication events, while logged in to the primary Screen:


admin% ssadm -r primary edit Initial
edit> vars add sys=Screenname
prg=auth
name=LogSeverity
value=debug
description="debug authentication operations"
edit> quit
Note -

Although, the output produced by print surrounds the value of each item in double quotes, these are only necessary on input to protect embedded spaces within the values of items. Also, although print outputs all tag names in capital letters (for example, PRG=), these tags are recognized in a case-insensitive manner on input (for example, prg=, Prg=, PRG= are equivalent). Finally, the VALUE string for the LogSeverity variable is likewise processed in a case-insensitive manner.

Once log limiters have been altered, the configuration must be activated to propagate the changes.