IBM Carrier Grade X3650 T, Руководство пользователя

Страница: 86 / 108

IBM® Carrier Grade Server X3650 T
Revision 3.0 78
The event_type argument indicates the event type that is logging the event. The event record’s
log_event_type member shall be set to the value of the event_type argument. The value of the
event_type argument shall be a valid log event type or the syscon_log_write () function shall fail.
The severity argument indicates the severity level of the event record. The event record’s log_severity
member shall be set to the value of the severity argument. The value of the severity argument shall be
one of the severity levels defined in
<syscon.h>
, or the syscon_log_write () function shall fail.
The event record’s log_uid member shall be set to the effective user-ID of the calling process. The event
record’s log_gid member shall be set to the effective group-ID of the calling process. The event record’s
log_pid member shall be set to the process ID of the calling process. The event record’s log_pgrp
member shall be set to the process-group ID of the calling process. The event record’s log_time member
shall be set to the time of the call to syscon_log_write (). (If {_POSIX_TIMERS} is defined, this shall be
the current value of the CLOCK_REALTIME clock.)
The event record’s log_recid member shall be set to an implementation-defined value that uniquely
identifies this event record in the active system log.
If one or more processes have registered (via the syscon_log_notify_add () function) to be notified of new
events, it is up to the implementation whether those notifications occur before or after control returns from
the
syscon_log_write () function.
Note that there is no need to “open” the system log before writing to it with syscon_log_write ().
17.1.1.3 Returns
Upon successful completion, the syscon_log_write () function shall return zero. Otherwise an error
number shall be returned to indicate the error.
17.1.1.4 Errors
If any of the following conditions occur, the syscon_log_write () function shall return the corresponding
error number:
•
[EINVAL]: The event_type argument is not a valid log event type.
•
[EINVAL]: The severity argument is invalid.
•
[EINVAL]: The format argument is invalid.
•
[EMSGSIZE]: The len argument exceeds {SYSCONLOG_ENTRY_MAXLEN} length, and
{SYSCONLOG_TRUNCATE} is not defined by the implementation.
•
[EBADMSG]: The format argument is equal to {SYSCONLOG_STRING}, but buf does not point
to a null-terminated string whose length is len bytes.
•
[ENOSPC]: The log has run out of space.
•
[EIO]: An I/O error occurred in writing to the system log.