NOAUDTERM (JANUS DEFINE parameter): Difference between revisions
mNo edit summary |
(Automatically generated page update) |
||
| Line 1: | Line 1: | ||
{{DISPLAYTITLE:NOAUDTERM}} | {{DISPLAYTITLE:NOAUDTERM}} | ||
<span class="pageSubtitle" | <span class="pageSubtitle">Suppress non-compiler terminal output from audit</span> | ||
<var>NOAUDTERM</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | <var>NOAUDTERM</var> is a parameter on <var>[[JANUS DEFINE]]</var>, which defines and sets characteristics of a Janus port. | ||
Revision as of 22:21, 16 April 2013
Suppress non-compiler terminal output from audit
NOAUDTERM is a parameter on JANUS DEFINE, which defines and sets characteristics of a Janus port.
This parameter is used to control whether the server thread sends "non-compiler terminal output" to the audit trail. Compiler terminal output is always sent to the audit trail. Any terminal output sent to the audit trail is sent as RK lines.
NOAUDTERM, which is the default port setting, specifies that (non-compiler) terminal output is not sent to the audit trail; AUDTERM specifies that terminal output is sent to the audit trail.
Note that some "print output" can be captured on a Sirius $list, a Janus socket, or a USE output stream, and thus it would not be sent as terminal output — to the audit trail or anywhere else.
On a WEBSERV port:
- Even with AUDTERM set on a WEBSERV port, terminal output is not sent to the audit trail if $Web_On is explicitly or implicitly set.
- The setting of AUDTERM (or NOAUDTERM) applies to all URLs on a WEBSERV port unless explicitly overridden by a NOAUDTERM(or AUDTERM) parameter on a JANUS WEB ON rule.
On a SRVSOCK port:
- The setting of AUDTERM (or NOAUDTERM) for a socket can be changed using the $Sock_Set function.
This parameter applies to all Janus "server" port types, and the default setting is NOAUDTERM.
Starting with Version 6.0, compared to earlier versions, any WEBSERV port that does not specify either AUDTERM or NOAUDTERM will probably generate fewer audit trail lines, as will any SDS or OPENSERV port. This should be a benefit, since most of this terminal output is either uninteresting or already logged to the audit trail as ER, AD or MS lines. Logging these messages as RK lines as well is just a waste of journal space and I/O and makes application diagnosis and debugging from the audit trail more difficult because of the extra noise data. For WEBSERV, OPENSERV, or SRVSOCK applications that wish to explicitly audit information, the User Language Audit statement should be used, not the Print statement.
Valid for WEBSERV, SDS, OPENSERV, or SRVSOCK port types.
Not valid for CLSOCK or DEBUGGERCLIENT port types.