X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=elogind.git;a=blobdiff_plain;f=man%2Fsd_journal_print.xml;h=c03762ac2ca9a5cc1af04ccabde8c4f1ea81c990;hp=65694a2e301292ec2c11a3b308f397d9947b640c;hb=bdfb9e7f7c315af5a6755ac4701b696ce2305a19;hpb=19125c205aa6084c225b5c11cc6dcbe18c6dbcc0;ds=sidebyside diff --git a/man/sd_journal_print.xml b/man/sd_journal_print.xml index 65694a2e3..c03762ac2 100644 --- a/man/sd_journal_print.xml +++ b/man/sd_journal_print.xml @@ -47,6 +47,8 @@ sd_journal_printv sd_journal_send sd_journal_sendv + sd_journal_perror + SD_JOURNAL_SUPPRESS_LOCATION Submit log entries to the journal @@ -80,6 +82,11 @@ int n + + int sd_journal_perror + const char* message + + @@ -124,17 +131,19 @@ immediately followed by their associated parameters, terminated by NULL. The strings passed should be of the format VARIABLE=value. The - variable name must be in uppercase and consist only - of characters, numbers and underscores, and may not - begin with an underscore. The value can be of any size - and format. It is highly recommended to submit - text strings formatted in the UTF-8 character encoding - only, and submit binary fields only when formatting in - UTf-8 strings is not sensible. A number of well known - fields are defined, see + variable name must be in uppercase and consist only of + characters, numbers and underscores, and may not begin + with an underscore. (All assignments that do not + follow this syntax will be ignored.) The value can be + of any size and format. It is highly recommended to + submit text strings formatted in the UTF-8 character + encoding only, and submit binary fields only when + formatting in UTf-8 strings is not sensible. A number + of well known fields are defined, see systemd.journal-fields7 for details, but additional application defined fields - may be used. + may be used. A variable may be assigned more than one + value per entry. sd_journal_sendv() is similar to sd_journal_send() but @@ -149,6 +158,21 @@ particularly useful to submit binary objects to the journal where that is necessary. + sd_journal_perror() is a + similar to + perror3 + and writes a message to the journal that consists of + the passed string, suffixed with ": " and a human + readable representation of the current error code + stored in + errno3. If + the message string is passed as NULL or empty string + only the error string representation will be written, + prefixed with nothing. An additional journal field + ERRNO= is included in the entry containing the numeric + error code formatted as decimal string. The log + priority used is LOG_ERR (3). + Note that sd_journal_send() is a wrapper around sd_journal_sendv() to make it @@ -171,7 +195,7 @@ sd_journal_send("MESSAGE=Hello World, this is PID %lu!", (unsigned long) getpid( syslog3 and and sd_journal_print() may - largely be used interchangably + largely be used interchangeably functionality-wise. However, note that log messages logged via the former take a different path to the journal server than the later, and hence global @@ -190,8 +214,10 @@ sd_journal_send("MESSAGE=Hello World, this is PID %lu!", (unsigned long) getpid( Return Value - The four calls return 0 on success or a - negative errno-style error code. + The four calls return 0 on success or a negative + errno-style error code. The + errno3 + variable itself is not altered. @@ -216,6 +242,8 @@ sd_journal_send("MESSAGE=Hello World, this is PID %lu!", (unsigned long) getpid( sd-journal3, sd_journal_stream_fd3, syslog3, + perror3, + errno3, systemd.journal-fields7