IBM® Carrier Grade Server X3650 T
Revision 3.0
79
For each of the following conditions, if the condition is detected, the syscon_log_write() function shall
return the corresponding error number:
• [EPERM]: The caller does not have the appropriate implementation-defined privilege for writing
with the given event type. For example, an application whose effective user ID is not root has
attempted to log an event with a reserved event_type code.
• [ECANCELED]: The event-logging system has declined to log this event, for some
implementation-defined reason. For example, this event is a duplicate of another recently logged
event, or the event-logging system has been configured to screen out events such as this one.
17.1.1.5 Cross-References
write(), Clocks and CLOCK_REALTIME, getpid(), geteuid(), getegid(), getpgrp()
17.1.2 Write Formatted String to Log
Function: syscon_log_printf()
17.1.2.1 Synopsis
#include <syscon.h>
int syscon_log_printf(syscon_log_event_type_t event_type, int event_type,
syscon_log_severity_t severity, const char *format, ...);
17.1.2.2 Description
The call
syscon_log_printf(fac, type, sev, format, args);
where args is a set of zero or more comma-separated arguments, is equivalent to the following code:
char buf[SYSCONLOG_ENTRY_MAXLEN];
sprintf(buf, format, args);
syscon_log_write(fac, type, sev, buf, strlen(buf)+1, SYSCONLOG_STRING);
If the implied call to sprintf() would create a string whose length (including terminating null character) is
greater than SYSCONLOG_ENTRY_MAXLEN, the behavior of syscon_log_printf() is undefined.
17.1.2.3 Returns
Upon successful completion, the syscon_log_printf() function shall return zero. Otherwise an error
number shall be returned to indicate the error.
To Next Page
Loading...
Need help?
General