| /illumos-gate/usr/src/man/man5/ |
| H A D | nfslog.conf.5 | 8 nfslog.conf \- NFS server logging configuration file
20 and \fBnfslogd\fR(8) daemon during logging. Each entry in the file consists of
27 \fBshare_nfs\fR(8) command specifies the \fBNFS\fR server logging parameters
30 using the same logging tag identifier.
33 NFS server logging is not supported on Solaris machines that are using NFS
38 specifies the default set of values to be used during logging. If no tag
61 Specifies the directory where the logging files and working files will be
124 logging use a common set of parameters that conform to the specific needs of
148 engineering defaultdir=/engineering/logging \e
150 accounting defaultdir=/accounting/logging
[all …]
|
| H A D | kdc.conf.5 | 79 \fB\fBlogging\fR\fR
83 Contains relations that determine how Kerberos programs perform logging.
526 .SS "The \fBlogging\fR Section"
529 This section indicates how Kerberos programs perform logging. The same relation
530 can be repeated if you want to assign it multiple logging methods. The
531 following relations can be defined in the \fB[logging]\fR section:
539 Specifies how the \fBKDC\fR is to perform its logging. The default is
550 Specifies how the administration server is to perform its logging. The default
561 Specifies how to perform logging in the absence of explicit specifications.
566 The \fB[logging]\fR relations can have the following values:
[all …]
|
| H A D | krb5.conf.5 | 97 \fB\fBlogging\fR\fR
102 logging.
898 .SS "The \fB[logging]\fR Section"
899 This section indicates how Kerberos programs are to perform logging. There are
905 can be repeated if you want to assign it multiple logging methods.
924 Specifies how to perform logging in the absence of explicit specifications
935 Specifies how the \fBKDC\fR is to perform its logging. The default is
954 This value causes the entity's logging messages to go to the specified file. If
966 This value causes the entity's logging messages to go to its standard error
977 This value causes the entity's logging messages to go to the console, if the
[all …]
|
| /illumos-gate/usr/src/man/man8/ |
| H A D | mount_ufs.8 | 154 \fB\fBlogging\fR | \fBnologging\fR\fR
158 If \fBlogging\fR is specified, then logging is enabled for the duration of the
159 mounted file system. Logging is the process of storing transactions (changes
164 might run. And, if \fBfsck\fR is bypassed, logging generally reduces the time
167 The default behavior is \fBlogging\fR for all UFS file systems.
174 Logging is enabled on any \fBUFS\fR file system, including root (\fB/\fR),
180 When logging is specifically disabled.
193 Could not enable logging for /mnt on /dev/dsk/c0t4d0s0.
199 The log created by \fBUFS\fR logging is continually flushed as it fills up. The
322 \fBExample 1 \fRTurning Off (and On) Logging
[all …]
|
| H A D | th_define.8 | 72 the logging criteria. The log of accesses is placed at the top of each script
83 (refer to the \fB-e\fR option for more information). By default, logging
85 from areas mapped for both reading and writing. You can constrain logging by
87 \fIlength\fR. Logging will continue for \fIcount\fR matching accesses, with an
154 If \fIacc_types\fR is set to \fBlog\fR, logging will match all \fBPIO\fR
157 case the matching condition for logging will be restricted to the specified
192 logging, the number of logged accesses is given by \fIcount\fR +
196 Note that access logging may be combined with error injection if
198 logging and any of the other access types (\fBpio\fR, \fBdma\fR and \fBintr\fR)
334 option applies only to non-logging errdefs. If an error definition remains
[all …]
|
| H A D | svc.startd.8 | 84 \fB\fBlogging\fR\fR
88 Control the level of global service logging for \fBsvc.startd\fR. An
158 In addition to any logging done by the managed service, \fBsvc.startd\fR
159 provides a common set of service reporting and logging mechanisms.
235 By default, \fBsvc.startd\fR provides logging of significant restarter actions
238 of logging to system global locations like \fB/var/svc/log/svc.startd.log\fR
239 and \fBsyslog\fR is controlled by the \fBoptions/logging\fR property.
549 \fBExample 1 \fRTurning on Verbose Logging
552 To turn on verbose logging, type the following:
559 svc:/system/svc/restarter:default> setprop options/logging = \e
|
| H A D | mdnsd.8 | 51 .Sh LOGGING
54 logging levels map as follows:
63 A SIGUSR1 signal toggles additional logging, with Warning and Notice
68 A SIGUSR2 signal toggles packet logging:
|
| H A D | poold.8 | 72 Specify the verbosity level for logging information.
76 the default logging level is \fBINFO\fR.
151 \fBExample 1 \fRModifying the Default Logging Level
154 The following command modifies the default logging level to \fBERR\fR:
|
| H A D | rctladm.8 | 22 supported in the current release of the Solaris operating system. Logging of
99 \fBExample 1 \fRActivating System Logging for Specific Violations
102 The following command activates system logging of all violations of
192 By default, there is no global logging of \fBrctl\fR violations.
|
| /illumos-gate/usr/src/cmd/pools/poold/ |
| H A D | poold.properties | 36 # poold-specific logging properties (replacing default logging.properties)
41 java.util.logging.FileHandler.limit = 0
42 java.util.logging.FileHandler.count = 1
43 java.util.logging.FileHandler.append = true
46 java.util.logging.FileHandler.pattern = /var/log/pool/java%u.log
47 java.util.logging.FileHandler.formatter = com.sun.solaris.service.logging.SysloglikeFormatter
|
| /illumos-gate/usr/src/man/man3sip/ |
| H A D | sip_enable_trans_logging.3sip | 10 logging operations
36 functions enable transaction and dialog logging respectively. The \fIlogfile\fR
38 argument controls the amount of logging. The only flag defined in \fB<sip.h>\fR
39 is \fBSIP_DETAIL_LOGGING\fR. Either transaction or dialog logging, or both, can
40 be enabled at any time. For dialog logging to work, the SIP stack must be
53 functions disable the transaction or dialog logging. These functions do not
64 \fBExample 1 \fRDialog logging
67 The following is an example of dialog logging.
82 /* Application disables logging */
|
| /illumos-gate/usr/src/cmd/hal/hald/ |
| H A D | logger.c | 4 * logger.c : Logging
43 * @defgroup HalDaemonLogging Logging system
45 * @brief Logging system for the HAL daemon
60 /** Disable all logging
69 /** Enable all logging
78 /** enable usage of syslog for logging
87 /** disable usage of syslog for logging
115 /** Setup logging entry
117 * @param priority Logging priority, one of HAL_LOGPRI_*
131 /** Emit logging entry
[all …]
|
| H A D | logger.h | 4 * logger.h : Logging facility
39 /** Logging levels for HAL daemon
66 /** Trace logging macro */
69 /** Debug information logging macro */
72 /** Information level logging macro */
75 /** Warning level logging macro */
78 /** Error leve logging macro */
|
| /illumos-gate/usr/src/cmd/pools/poold/com/sun/solaris/domain/pools/ |
| H A D | Poold.java | 33 import java.util.logging.*;
38 import com.sun.solaris.service.logging.*;
128 * logging Interface to Solaris syslog facility
171 * Logging:
173 * Logging services are provided by the com.sun.solaris.logging
175 * specific logging requirements.
268 * Default path to the logging properties file.
378 * Flag recording whether the logging Severity has been
381 * and the configuration's logging properties are
387 * Indicates whether logging semantics should be changed
[all …]
|
| /illumos-gate/usr/src/man/man4fs/ |
| H A D | ufs.4fs | 73 Indicates that the file system has logging enabled.
75 If a file system has logging enabled, the only flags that it can have are
79 A non-logging file system can have
164 .Ss UFS Logging
165 UFS logging bundles the multiple metadata changes that comprise a complete UFS
170 UFS logging provides two advantages:
178 UFS logging often provides a significant performance improvement.
179 This is because a file system with logging enabled converts multiple updates to
|
| /illumos-gate/usr/src/man/man3m/ |
| H A D | fex_set_log.3m | 39 The \fBfex_set_log()\fR function enables logging of retrospective diagnostic
41 If \fIfp\fR is \fINULL\fR, logging is disabled. When a program starts, logging
47 the log from becoming exorbitantly long, the logging mechanism eliminates
98 The \fBfex_set_log()\fR function returns a non-zero value if logging is enabled
101 (regardless of whether logging is enabled) and returns 0 otherwise.
114 * enable logging of retrospective diagnostics
|
| /illumos-gate/usr/src/uts/common/fs/ufs/ |
| H A D | lufs.c | 80 * Logging delta and roll statistics
132 * General logging kstats
401 * progress of enabling/disabling logging. in lufs_snarf()
424 * enabling/disabling logging. in lufs_snarf()
557 * Assumes the file system is write locked and is not logging
658 * Assumes the file system is write locked and is not logging
845 * Disable logging
860 * Logging is already disabled; done in lufs_disable()
874 * File system must be write locked to disable logging in lufs_disable()
897 * WE ARE COMMITTED TO DISABLING LOGGING PAST THIS POINT in lufs_disable()
[all …]
|
| /illumos-gate/usr/src/boot/efi/include/Protocol/ |
| H A D | Security.h | 10 as event logging for attested boots, locking flash in response to discovering
39 flash upon failure to authenticate, attestation logging for all signed drivers,
40 and other exception operations. The File parameter allows for possible logging
63 being dispatched. This will optionally be used for logging.
89 /// attestation logging, and other exception operations.
|
| /illumos-gate/usr/src/cmd/acctadm/ |
| H A D | main.c | 309 * Stop net logging before turning it off so that the last in main()
320 die(gettext("failed to stop logging network " in main()
360 * Stop net logging before turning it off so that the in main()
372 die(gettext("failed to stop logging " in main()
428 * Let's get network logging started. We do this after turning on in main()
434 * Default logging interval for AC_NET is in main()
446 die(gettext("failed to start logging " in main()
458 * Stop net logging before turning it off so that the last in main()
469 die(gettext("failed to stop logging " in main()
493 * Let's get network logging started. in main()
[all …]
|
| /illumos-gate/usr/src/man/man3c/ |
| H A D | lfmt.3c | 9 lfmt \- display error message in standard format and pass to logging and
30 that of \fBprintf()\fR. It forwards its output to the logging and monitoring
106 \fIconsole display control\fR and \fIlogging information\fR should be specified
258 \fB\fILogging information\fR\fR
364 for logging:
386 displays the message to \fBstderr\fR and makes it available for logging:
|
| /illumos-gate/usr/src/lib/krb5/kadm5/srv/ |
| H A D | logger.c | 37 * logger.c - Handle logging functions for those who want it.
78 static const char LSPEC_PARSE_ERR_2[] = "%s: warning - logging entry syntax error\n";
99 return(gettext("%s: warning - logging entry syntax error\n")); in krb5_log_error_table()
127 * Output logging.
129 * Output logging is now controlled by the configuration file. We can specify
130 * the following syntaxes under the [logging]->entity specification.
464 * logging specification. in klog_com_err_proc()
524 * krb5_klog_init() - Initialize logging.
565 * Look up [logging]-><ename> in the profile. If that doesn't in krb5_klog_init()
566 * succeed, then look for [logging]->default. in krb5_klog_init()
[all …]
|
| /illumos-gate/usr/src/tools/scripts/ |
| H A D | wsdiff.py | 75 # -V Log *all* ELF sect diffs vs. logging the first diff found
137 # Logging routines
150 if logging :
163 if logging :
176 if logging :
185 if logging :
211 # Do the actual logging of the difference to the results file
215 if logging :
369 -V Log *all* ELF sect diffs vs. logging the first diff found""",
379 global logging
[all …]
|
| /illumos-gate/usr/src/man/man3sasl/ |
| H A D | sasl_log_t.3sasl | 10 sasl_log_t \- the SASL logging callback function
24 SASL library. \fBsyslog\fR(3C) is used, unless another logging function is
33 The logging context from the callback record.
42 The logging level. Possible values for \fIlevel\fR include:
|
| /illumos-gate/usr/src/cmd/svc/startd/ |
| H A D | log.c | 29 * log.c - debugging and logging functions
31 * Logging destinations
32 * svc.startd(8) supports three logging destinations: the system log, a
56 * Logging detail
93 * Logging configuration
94 * The preferred approach is to set the logging property values
97 * "verbose" and "debug" allow LOG_INFO and LOG_DEBUG logging requests to
131 * internal debug logging. Although a performance loss can be expected.
138 * logging messages. To read it properly you should start after the first
237 * some checking are done before logging the messages in the internal
[all …]
|
| /illumos-gate/usr/src/lib/krb5/kadm5/clnt/ |
| H A D | logger.c | 37 * logger.c - Handle logging functions for those who want it.
78 static const char LSPEC_PARSE_ERR_2[] = "%s: warning - logging entry syntax error\n";
99 return(gettext("%s: warning - logging entry syntax error\n")); in krb5_log_error_table()
126 * Output logging.
128 * Output logging is now controlled by the configuration file. We can specify
129 * the following syntaxes under the [logging]->entity specification.
463 * logging specification. in klog_com_err_proc()
523 * krb5_klog_init() - Initialize logging.
564 * Look up [logging]-><ename> in the profile. If that doesn't in krb5_klog_init()
565 * succeed, then look for [logging]->default. in krb5_klog_init()
[all …]
|