


     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



     NAME
	  LSB.os/genuts/syslog_L - control system log test case

     DESCRIPTION
	  This test case tests the syslog() system call	interface for
	  conformance to The Open Group's CAE Specification: System
	  Interfaces and Headers, page:syslog()

     TESTS
	  1    A call to syslog(priority, message, ...)	sends the
	       specified message to a logging facility.	 The logged
	       message includes	a header and a body: the header
	       contains	a timestamp and	a tag string and the body is
	       derived from the	message	and any	following arguments
	       that were passed	to syslog(), formatted after the style
	       of printf() with	plain characters passed	through
	       unaltered.

	  2    When a valid severity level value is ORed into
	       priority, then the message generated by a call to
	       syslog(priority,	message, ...) is logged	with the
	       specified severity level.

	  3    When a valid facility value is ORed into	priority, then
	       the message generated by	a call to
	       syslog(priority,	message, ...) is logged	with the
	       specified facility value.

	  4    When no valid facility value is ORed into priority and
	       a default facility value	has been specified in a
	       previous	call to	openlog(), then	the message generated
	       by a call to syslog(priority, message, ...) is logged
	       with the	default	facility value.

	  5    When no valid facility value is ORed into priority and
	       there has been no previous call to openlog() in which a
	       default facility	value has been specified, then the
	       message generated by a call to
	       syslog(priority,	message, ...) is logged	with a
	       facility	value of LOG_USER.

	  6    When message contains %m, then in the message generated
	       by a call to syslog(priority, message, ...) the %m is
	       replaced	by a digit string whose	value is taken from
	       errno in	the calling process.

	  7    When message does not include a trailing	newline, then
	       a call to syslog(priority, message, ...)	appends	a
	       newline to the logged message.

	  8    When message includes a conversion specification	in
	       which the field width is	not specified or the field



     Page 1					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       width is	smaller	than the converted number, then	in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	converted
	       number is not truncated and the field is	expanded to
	       contain the conversion result.

	  9    When message contains %d, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       integer specified by arg	is converted to	a signed
	       decimal character string	with a default precision of
	       one.

	  10   When message contains %i, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       integer specified by arg	is converted to	a signed
	       decimal character string	with a default precision of
	       one.

	  11   When message contains %o, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       integer specified by arg	is converted to	an unsigned
	       octal character string with a default precision of one.

	  12   When message contains %u, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       integer specified by arg	is converted to	a decimal
	       character string	with a default precision of one.

	  13   When message contains %x, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       integer specified by arg	is converted to	a hexadecimal
	       notation	character string, using	the letters "abcdef"
	       with a default precision	of one.

	  14   When message contains %X, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       integer specified by arg	is converted to	a hexadecimal
	       notation	character string, using	the letters "ABCDEF"
	       with a default precision	of one.

	  15   When message contains %f, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       float or	double specified by arg	is converted to	a
	       decimal notation	character string of the	form
	       "[-]ddd.ddd" where six digits are output	after the
	       decimal point character by default.

	  16   When message contains %e, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       float or	double specified by arg	is converted to	a
	       decimal notation	character string of the	form
	       "[-]d.ddde_dd" where, by	default, there is one digit



     Page 2					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       before the decimal point	character, six digits after
	       the decimal point character and the exponent always has
	       at least	two digits.

	  17   When message contains %e, and the float or double
	       specified by arg	is greater than	or equal to 1e+100,
	       then in the message generated by	a call to
	       syslog(priority,	message, arg, ...), additional
	       exponent	digits are added as necessary.

	  18   When message contains %E, then in the message generated
	       by a call to syslog(priority, message, arg, ...), this
	       directive produces the same effect as the "%e" notation
	       except that the string has an "E" instead of an "e"
	       introducing the exponent.

	  19   When message contains %g	and the	exponent, resulting
	       from a conversion to "%e" format	of the float or	double
	       specified by arg, would be greater than or equal	to -4,
	       or less than the	default	precision of 6,	then in	the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	"%f" format is
	       used for	the conversion.

	  20   When message contains %g	and the	exponent, resulting
	       from a conversion to "%e" format	of the float or	double
	       specified by arg, would be less than -4,	or greater
	       than or equal to	the default precision of 6, then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), the	"%e" format is
	       used for	the conversion.

	  21   When message contains %G, then in the message generated
	       by a call to syslog(priority, message, arg, ...), this
	       directive produces the same effect as the "%g" notation
	       except that it uses the "%E" format instead of the "%e"
	       format.

	  22   When message contains %g	or %G, then in the message
	       generated by a call to
	       syslog(priority,	message, arg, ...), trailing zeros are
	       removed from the	fractional portion of the result.

	  23   When message contains %g	or %G, then in the message
	       generated by a call to
	       syslog(priority,	message, arg, ...), a decimal point
	       character appears in the	result only in the case	that
	       it is followed by a digit.

	  24   When message contains %c, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       character specified by arg is printed.



     Page 3					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	  25   When message contains %s, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       character pointer specified by arg is assumed to	be a
	       string and characters from the string are printed until
	       a null character	is encountered.

	  26   When message contains %C, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       wide character specified	by arg is converted to its
	       multibyte equivalent and	printed.

	       Not tested in POSIX and XPG3 modes.

	  27   When message contains %S, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       wide string pointed to by arg is	converted to a
	       multibyte sequence until	a null wide character is
	       reached and the multibyte sequence is printed.

	       Not tested in POSIX and XPG3 modes.

	  28   When message contains %p, then in the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       pointer to void specified by arg	is converted to	an
	       implementation defined sequence of printable
	       characters.

	  29   When message contains %n, then on a call	to
	       syslog(priority,	message, arg, ...), arg	is a pointer
	       to an integer into which	is written the number of
	       characters written so far by this call to the function.
	       No argument is converted.

	  30   When message contains %%, then in the message generated
	       by a call to syslog(priority, message, ...), a "%" is
	       printed and no argument is converted.

	  31   When message contains %l?, where	? = a type conversion
	       character (d, i,	o, u, x, X, n),	then in	the message
	       generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	i | o |	u | x |	X], then arg is	taken
	       to be a long integer and	converted accordingly;
	       b. when ? = [n],	then arg is taken to be	a pointer to a
	       long integer which is written accordingly.

	  32   When message contains %h?, where	? = a type conversion
	       character (d, i,	o, u, x, X, n),	then in	the message
	       generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	i | o |	u | x |	X], then arg is
	       converted as if the h were not there;



     Page 4					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       b. when ? = [n],	then arg is taken to be	a pointer to a
	       short integer which is written accordingly.

	  33   When message contains %.?, where	? = a type conversion
	       character (d, hi, lo, f,	e, g, s, S), then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | lo], then the result is
	       equivalent to "%?";
	       b. when ? = [d |	hi | lo], arg =	0 then arg is
	       converted to a null string;
	       c. when ? = [f |	e], then no decimal point character
	       occurs in the decimal notation character	string that
	       arg is converted	to;
	       d. when ? = [g],	then :
		    i. for ((arg >= 1E-04) && (arg < 1)) || ((arg <=
		    -1E-04) && (arg > -1)), the	result is printed in
		    'f'	format with one	significant digit;
		    ii.	for ((arg < 1E-04) && (arg > -1E-04)) || ((arg
		    >= 1) && (arg <= -1)), no decimal point character
		    occurs in the decimal notation character string
		    that arg is	converted to;
	       e. when ? = [s |	S], then the result is converted to a
	       null string.

	       The S directive is not tested in	POSIX and XPG3 modes.

	  34   When message contains %.m?, where ? = a type conversion
	       character (d, hi, lo, f,	e, g, s, S), then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | lo], and m	= an integer, then m
	       represents the minimum number of	digits that appear in
	       the converted output and	in the case that the value
	       being converted can be represented in a fewer number of
	       digits than m, it will be expanded with leading zeros;
	       b. when ? = [f |	e], and	m = an integer,	then m
	       represents the number of	digits after the decimal point
	       character in the	converted output string;
	       c. when ? = [g],	m = an integer precision and m <= 4
	       then :
		    i. for ((arg >= 1E-m) && (arg < 1))	|| ((arg <=
		    -1E-m) && (arg > -1)), "0" is printed out;
		    ii.	for ((arg < 1E-m) && (arg > -1E-m)) || ((arg
		    >= 1) && (arg <= -1)), m decimal places of
		    precision will be printed out in the result	arg is
		    converted to;
	       d. when ? = [g],	and m =	an integer then	in the case
	       that the	exponent of the	converted number is greater
	       than or equal to	m or less than -4 then "%e", ("%E"
	       format when "%.mG" given) will be used for converting
	       arg;



     Page 5					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       e. when ? = [s |	S], and	m = an integer,	then m
	       represents the maximum number of	bytes to be printed in
	       the case	that a null character (or null wide character)
	       is not reached;

	       The S directive is not tested in	POSIX and XPG3 modes.

	  35   When message contains %n?, where	? = a type conversion
	       character (d, hi, lo, x,	f, e, g, c, C, s, S) and n =
	       an integer, then	in the message generated by a call to
	       syslog(priority,	message, arg, ...), n represents the
	       minimum field width of the converted output string and
	       in the case that	the converted value has	fewer bytes
	       then it will be padded on the left with spaces.

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.

	  36   When message contains %0n?, where ? = a type conversion
	       character (d, hi, lo, x,	f, e, g) and n = an integer,
	       then in the message generated by	a call to
	       syslog(priority,	message, arg, ...), n represents the
	       minimum field width of the converted output string and
	       in the case that	the converted value has	fewer
	       characters then it will be padded on the	left with
	       zeroes, following any sign or base.

	  37   When message contains %n.?, where ? = a type conversion
	       character (d, hi, lo, f,	e, g, s, S) and	n = an
	       integer,	then in	the message generated by a call	to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then n
	       represents the minimum field width of the converted
	       output string and the precision of the string is	set to
	       the default value for that particular conversion	type;

	       The S directive is not tested in	POSIX and XPG3 modes.

	  38   When message contains %n.m?, where ? = a	type
	       conversion character (d,	hi, lo,	f, e, g, s, S) and
	       n & m = an integer, then	in the message generated by a
	       call to syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then n
	       represents the minimum field width of the converted
	       output string, m	represents the precision of the	string
	       for that	particular conversion type and the result is
	       equivalent to the result	from "%n?" except for the
	       modification for	a precision of m;

	       The S directive is not tested in	POSIX and XPG3 modes.

	  39   When message contains %*?, where	? = a type conversion



     Page 6					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       character (d, hi, lo, f,	e, g, c, C, s, S), then	in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	"*" takes the
	       place of	the field width	integer	the value of which is
	       taken from an integer argument that precedes the
	       argument	to be converted	(from the nth argument).
	       A negative field	width is taken as a - flag followed by
	       a positive field	width (not required in XPG3 mode).

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.

	  40   When message contains %.*?, where ? = a type conversion
	       character (d, hi, lo, f,	e, g, s, S), then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then the	"*"
	       takes the place of the precision	integer	the value of
	       which is	taken from an integer argument that precedes
	       the argument to be converted (from the mth argument);
	       A negative precision is taken as	if the precision were
	       omitted (not required in	XPG3 mode).

	       The S directive is not tested in	POSIX and XPG3 modes.

	  41   When message contains %*.?, where ? = a type conversion
	       character (d, hi, lo, f,	e, g, s, S), then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then the	"*"
	       takes the place of the minimum field width of the
	       converted output	string and the precision of the	string
	       is set to the default value for that particular
	       conversion type;
	       A negative field	width is taken as a - flag followed by
	       a positive field	width (not required in XPG3 mode).

	       The S directive is not tested in	POSIX and XPG3 modes.

	  42   When message contains %*.*?, where ? = a	type
	       conversion character (d,	hi, lo,	f, e, g, s, S),	then
	       in the message generated	by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then the	first
	       "*" takes the place of the field	width integer and the
	       second "*" takes	the place of precision integer.	 Both
	       take their values from integer arguments.
	       A negative field	width is taken as a - flag followed by
	       a positive field	width (not required in XPG3 mode).
	       A negative precision is taken as	if the precision were
	       omitted (not required in	XPG3 mode).




     Page 7					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       The S directive is not tested in	POSIX and XPG3 modes.

	  43   When message contains %#?, where	? = a type conversion
	       character (d, hi, o, lo,	x, lX, f, e, g,	c, s), then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | f | e | c | s] then the result is
	       equivalent to "%?", (the	"#" flag only affects ?	= [f |
	       e | E] when a precision of 0 is specified);
	       b. when ? = [o |	lo] then the "#" flag increases	the
	       precision to force the first digit of the result	to be
	       a zero;
	       c. when ? = [x] then the	"#" flag increases the
	       precision to prefix a non-zero result with a "0x";
	       d. when ? = [lX]	then the "#" flag increases the
	       precision to prefix a non-zero result with a "0X";
	       e. when ? = [g] then "#"	flag prevents removal of
	       trailing	zeros from the result so that precision	number
	       of digits are always printed out	after the decimal
	       point character;

	       The d, hi, c and	s directives are tested	in XPG3	mode
	       only.

	  44   When message contains % ?, where	? = a type conversion
	       character (d, hi, u, lo,	f, e, g, c, C, s, S), then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [c |	C | s |	S | u |	lo], the " " flag has
	       no effect on the	conversion of arg and the result is
	       equivalent to "%?";
	       b. when ? = [d |	hi | f | e | g], the result is
	       equivalent to "%?"  except that in the case that	the
	       first character is not a	sign the " " flag prefixes the
	       result with a blank.

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.

	  45   When message contains %+?, where	? = a type conversion
	       character (d, hi, u, lo,	f, e, g, c, C, s, S), then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [c |	C | s |	S | u |	lo], the "+" flag has
	       no effect on the	conversion of arg and the result is
	       equivalent to "%?";
	       b. when ? = [d |	hi | f | e | g], the result is
	       equivalent to "%?"  except that the first character of
	       the result is always a sign ('+'	or '-').

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.



     Page 8					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	  46   When message contains %-n?  where ? = a type conversion
	       character (d, hi, u, lo,	f, e, g, c, C, s, S) then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%n?" except that it is left justified.

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.

	  47   When message contains %+-n?, where ? = a	type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S) then in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%+n?" except that	it is left justified.

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.

	  48   When message contains % -n?, where ? = a	type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S) then in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%	n?" except that	it is left justified.

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.

	  49   When message contains %+	?, where ? = a type conversion
	       character (d, hi, u, lo,	f, e, g, c, C, s, S), then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%+?".

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.

	  50   When message contains %-	+?, where ? = a	type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S) then in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%-+?".

	       The C and S directives are not tested in	POSIX and XPG3
	       modes.

	  51   When message contains %+n.*?, where ? = a type
	       conversion character (d,	hi, lo,	f, e, g, s, S) and n =
	       an integer, then	in the message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [ s | S | lo], the "+" flag has no effect
	       on the conversion of arg	and the	result is equivalent
	       to "%n.*?";



     Page 9					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       b. when ? = [d |	hi | f | e | g], the result is
	       equivalent to "%n.*?"  except that the first character
	       of the result is	always a sign ('+' or '-').

	       The S directive is not tested in	POSIX and XPG3 modes.

	  52   When message contains %-n.m?, where ? = a type
	       conversion character (d,	hi, lo,	f, e, g, s, S) then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%n.m?" except that the result is left
	       justified.

	       The S directive is not tested in	POSIX and XPG3 modes.

	  53   When message contains %+-n.?, where ? = a type
	       conversion character (d,	hi, lo,	f, e, g, s, S) then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%+n.?" except that it is left justified.

	       The S directive is not tested in	POSIX and XPG3 modes.

	  54   When message contains %#.?, where ? = a type conversion
	       character (d, hi, lo, f,	e, g, s), then in the message
	       generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | lo], then the resultant
	       conversion is equivalent	to "%#?";
	       b. when ? = [d |	hi | lo], and arg = 0 then arg is
	       converted to a null character string;
	       c. when ? = [f |	e | g],	the result is equivalent to
	       "%.?" except that the decimal point character is	always
	       printed out;
	       d. when ? = s, the result is equivalent to "%.s";

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  55   When message contains %#*.?, where ? = a	type
	       conversion character (d,	hi, lo,	f, e, g, s), then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%#.?" except that	it will	have a field
	       width of	at least the value specified by	the argument
	       corresponding to	* and in the case that the converted
	       value has fewer characters then it will be padded on
	       the left	with spaces.

	       The d, hi and s directives are tested in	XPG3 mode
	       only.




     Page 10					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	  56   When message contains %#.m?, where m = an integer and ?
	       = a type	conversion character (d, hi, lo, f, e, g, s),
	       then in the message generated by	a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | f | e | s], the result is
	       equivalent to "%.m?";
	       b. when ? = [lo], the result is equivalent to "%.m?"
	       except that the result always has a zero	as the first
	       digit;
	       c. when ? = [g],	the result is equivalent to "%.m?"
	       except that the decimal point and trailing zeros	are
	       not removed;

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  57   When message contains %#	+*?, where ? = a type
	       conversion character (d,	hi, lo,	f, e, g, c, s),	then
	       in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%#*?" except that	the first character of
	       a signed	conversion result is always a sign ('+', '-').

	       The d, hi, c and	s directives are tested	in XPG3	mode
	       only.

	  58   When message contains %#+-.*?, where ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, s), then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%#+.*?" except that it is	left
	       justified.

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  59   When message contains %#	*.*?, where ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, s), then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%#*.*?" except that, in the case that
	       the first character of a	signed conversion result is
	       not a sign, a blank is prefixed to the result.

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  60   When message contains %#- +n?, where ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, c, s),	then
	       in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%#n?" except that	it is left justified



     Page 11					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       and, in the case	that the first character of a signed
	       conversion result is not	a sign,	a blank	is prefixed to
	       the result.

	       The d, hi, c and	s directives are tested	in XPG3	mode
	       only.

	  61   When message contains %#-*.m?, where ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, s) and	m = an
	       integer,	then in	the message generated by a call	to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%#*.m?" except that it is	left
	       justified.

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  62   If the long double type is supported:
		    When message contains %L?, where ? is one of the
		    type conversion characters f, e, g,	E or G,	then
		    in the message generated by	a call to
		    syslog(priority, message, arg, ...), arg is	taken
		    to be a long double	and converted accordingly.

	  63   A call to syslog(priority, message, ...)	uses the
	       decimal point character defined by the locale specified
	       for the LC_NUMERIC category.

	  64   When the	current	locale setting is for the 'C' locale,
	       and the decimal point character is not defined or
	       supported by the	currently specified language, then the
	       decimal point character used in the message generated
	       by a call to syslog(priority, message, ...) defaults to
	       a period	".".

	  65   When the	conversion sequence contains "%k$", where k is
	       a positive integer in the range 1 to {NL_ARGMAX}, then
	       a call to syslog(priority, message, arg,	...) picks up
	       the kth argument	arg in the argument list and applies
	       the conversion sequence,	following the '$', to it, and
	       a non-existent field width or field width smaller than
	       the converted number does not cause truncation of the
	       converted number, as the	field is expanded to contain
	       the conversion result.

	  66   When message contains %k$d , where k = a	positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	integer
	       specified by arg	is converted to	a signed decimal
	       character string	with a default precision of one.




     Page 12					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	  67   When message contains %k$i, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	integer
	       specified by arg	is converted to	a signed decimal
	       character string	with a default precision of one.

	  68   When message contains %k$o, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	integer
	       specified by arg	is converted to	an unsigned octal
	       character string	with a default precision of one.

	  69   When message contains %k$u, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	integer
	       specified by arg	is converted to	a decimal character
	       string with a default precision of one.

	  70   When message contains %k$x, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	integer
	       specified by arg	is converted to	a hexadecimal notation
	       character string, using the letters "abcdef" with a
	       default precision of one.

	  71   When message contains %k$X, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	integer
	       specified by arg	is converted to	a hexadecimal notation
	       character string, using the letters "ABCDEF" with a
	       default precision of one.

	  72   When message contains %k$f, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	float or
	       double specified	by arg is converted to a decimal
	       notation	character string of the	form "[-]ddd.ddd"
	       where six digits	are output after the decimal point
	       character by default.

	  73   When message contains %k$e, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	float or
	       double specified	by arg is converted to a decimal
	       notation	character string of the	form "[-]d.ddde_dd"



     Page 13					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       where, by default, there	is one digit before the
	       decimal point character,	six digits after the decimal
	       point character and the exponent	always has at least
	       two digits.

	  74   When message contains %k$e, where k = a positive
	       integer,	arg is the kth argument	and the	float or
	       double specified	by arg is greater than or equal	to
	       1e+100, then in the message generated by	a call to
	       syslog(priority,	message, arg, ...), additional
	       exponent	digits are added as necessary.

	  75   When message contains %k$E, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), this directive
	       produces	the same effect	as the "%k$e" notation except
	       that the	string has an "E" instead of an	"e"
	       introducing the exponent.

	  76   When message contains %k$g, where k = a positive
	       integer,	arg is the kth argument	and the	exponent,
	       resulting from a	conversion to "%k$e" format of the
	       float or	double specified by arg, would be greater than
	       or equal	to -4, or less than the	default	precision of
	       6, then in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	"%f" format is
	       used for	the conversion.

	  77   When message contains %k$g, where k = a positive
	       integer and arg is the kth argument and the exponent,
	       resulting from a	conversion to "%k$e" format of the
	       float or	double specified by arg, would be less than
	       -4, or greater than or equal to the default precision
	       of 6, then in the message generated by a	call to
	       syslog(priority,	message, arg, ...), the	"%e" format is
	       used for	the conversion.

	  78   When message contains %k$G, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), this directive
	       produces	the same effect	as the "%k$g" notation except
	       that it uses the	"%k$E" format instead of the "%k$e"
	       format.

	  79   When message contains %k$g or %k$G, where k = a
	       positive	integer	and arg	is the kth argument, then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), trailing zeros are
	       removed from the	result.




     Page 14					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	  80   When message contains %k$g or %k$G, where k = a
	       positive	integer	and arg	is the kth argument, then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...), a decimal point
	       character appears in the	result only in the case	that
	       it is followed by a digit.

	  81   When message contains %k$c, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	character
	       specified by arg	is printed.

	  82   When message contains %k$s, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	character
	       pointer specified by arg	is assumed to be a string and
	       characters from the string are printed until a null
	       character is encountered.

	  83   When message contains %k$C, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	wide character
	       specified by arg	is converted to	the equivalent
	       multibyte character and printed.

	       Not tested in XPG3 mode.

	  84   When message contains %k$S, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	wide string
	       pointed to by arg is converted to the equivalent
	       multibyte character sequence until a null wide
	       character is reached and	the result of the conversion
	       is printed.

	       Not tested in XPG3 mode.

	  85   When message contains %k$p, where k = a positive
	       integer and arg is the kth argument, then in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	pointer	to
	       void specified by arg is	converted to an	implementation
	       defined sequence	of printable characters.

	  86   When message contains %k$n, where k = a positive
	       integer and arg is the kth argument, then on a call to
	       syslog(priority,	message, arg, ...), arg	is a pointer
	       to an integer into which	is written the number of



     Page 15					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       characters written so far by this call to the function.

	  87   When message contains %k$l?, where k = a	positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	i, o, u, x, X, n), then	in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	i | o |	u | x |	X], then arg is	taken
	       to be a long integer and	converted accordingly;
	       b. when ? = [n],	then arg is taken to be	a pointer to a
	       long integer which is written accordingly.

	  88   When message contains %k$h?, where k = a	positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	i, o, u, x, X, n), then	in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	i | o |	u | x |	X], then arg is
	       converted as if the h were not there;
	       b. when ? = [n],	then arg is taken to be	a pointer to a
	       short integer which is written accordingly.

	  89   When message contains %k$.?, where k = a	positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, s, S),	then
	       in the message generated	by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | lo], then the result is
	       equivalent to "%k$?";
	       b. when ? = [d |	hi | lo], arg =	0 then arg is
	       converted to a null string;
	       c. when ? = [f |	e], then no decimal point character
	       occurs in the decimal notation character	string that
	       arg is converted	to;
	       d. when ? = [g],	then :
		    i. for ((arg >= 1E-04) && (arg < 1)) || ((arg <=
		    -1E-04) && (arg > -1)), the	result is printed in
		    'f'	format with one	significant digit;
		    ii.	for ((arg < 1E-04) && (arg > -1E-04)) || ((arg
		    >= 1) && (arg <= -1)), no decimal point character
		    occurs in the decimal notation character string
		    that arg is	converted to;
	       e. when ? = [s |	S], then the result is converted to a
	       null string.

	       The S conversion	character is not tested	in XPG3	mode.

	  90   When message contains %k$.m?, where k = a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character" (d, hi, lo, f, e, g, s, S), then
	       in the message generated	by a call to
	       syslog(priority,	message, arg, ...):



     Page 16					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       a. when ? = [d |	hi | lo], and m	= an integer, then m
	       represents the minimum number of	digits that appear in
	       the converted output and	in the case that the value
	       being converted can be represented in a fewer number of
	       digits than m, it will be expanded with leading zeros;
	       b. when ? = [f |	e], and	m = an integer,	then m
	       represents the number of	digits after the decimal point
	       character in the	converted output string;
	       c. when ? = [g],	m = an integer precision and m <= 4,
	       then:
		    i. for ((arg >= 1E-m) && (arg < 1))	|| ((arg <=
		    -1E-m) && (arg > -1)), "0" is printed out;
		    ii.	for ((arg < 1E-m) && (arg > -1E-m)) || ((arg
		    >= 1) && (arg <= -1)), m decimal places of
		    precision will be printed out in the result	arg is
		    converted to;
	       d. when ? = [g],	and m =	an integer then	in the case
	       that the	exponent of the	converted number is greater
	       than or equal to	m or less than -4 then "%k$e", ("%k$E"
	       format in the case that "%k$.mG"	is given) will be used
	       for converting arg;
	       e. when ? = [s |	S], and	m = an integer,	then m
	       represents the maximum number of	characters to be
	       printed in the case that	a null character is not
	       reached;

	       The S conversion	character is not tested	in XPG3	mode.

	  91   When message contains %k$n?, where k = a	positive
	       integer,	arg is the kth argument, ? = a type conversion
	       character (d, hi, lo, x,	f, e, g, c, C, s, S) and n =
	       an integer, then	in the message generated by a call to
	       syslog(priority,	message, arg, ...), n represents the
	       minimum field width of the converted output string and
	       in the case that	the converted value has	fewer
	       characters then it will be padded on the	left with
	       spaces.

	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  92   When message contains %k$0n?, where k = a positive
	       integer,	arg is the kth argument, ? = a type conversion
	       character (d, hi, lo, x,	f, e, g) and n = an integer,
	       then in the message generated by	a call to
	       syslog(priority,	message, arg, ...), n represents the
	       minimum field width of the converted output string and
	       in the case that	the converted value has	fewer
	       characters then it will be padded on the	left with
	       zeroes, following any sign or base.

	  93   When message contains %k$n.?, where k = a positive



     Page 17					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       integer,	arg is the kth argument, ? = a type conversion
	       character (d, hi, lo, f,	e, g, s, S) and	n = an
	       integer,	then in	the message generated by a call	to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], n represents
	       the minimum field width of the converted	output string
	       and the precision of the	string is set to the default
	       value for that particular conversion type;

	       The S conversion	character is not tested	in XPG3	mode.

	  94   When message contains %k$n.m?, where k =	a positive
	       integer,	arg is the kth argument, ? = a type conversion
	       character (d, hi, lo, f,	e, g, s, S) and	n & m =	an
	       integer,	then in	the message generated by a call	to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then n
	       represents the minimum field width of the converted
	       output string, m	represents the precision of the	string
	       for that	particular conversion type and the result is
	       equivalent to the result	from "%n?" except for the
	       modification for	a precision of m;

	       The S conversion	character is not tested	in XPG3	mode.

	  95   When message contains %k$*n$?, where k and n are
	       positive	integers, arg is the kth argument, field width
	       is the nth argument and ? = a type conversion character
	       (d, hi, lo, f, e, g, c, C, s, S), then in the message
	       generated by a call to
	       syslog(priority,	message, arg, ...), the	"*" takes the
	       place of	the field width	integer, the value of which is
	       taken from an integer argument that precedes the
	       argument	to be converted	(from the nth argument).
	       A negative field	width is taken as a - flag followed by
	       a positive field	width (not required in XPG3 mode).

	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  96   When message contains %k$.*m$?, where k and m are
	       positive	integers, arg is the kth argument, precision
	       is the mth argument and ? = a type conversion character
	       (d, hi, lo, f, e, g, s, S), then	in the message
	       generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then the	"*"
	       takes the place of the precision	integer	the value of
	       which is	taken from an integer argument that precedes
	       the argument to be converted (from the mth argument);
	       A negative precision is taken as	if the precision were
	       omitted (not required in	XPG3 mode).



     Page 18					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       The S conversion	character is not tested	in XPG3	mode.

	  97   When message contains %k$*n$.?, where k and n are
	       positive	integers, arg is the kth argument, field width
	       is the nth argument and ? = a type conversion character
	       (d, hi, lo, f, e, g, s, S), then	in the message
	       generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then the	"*"
	       takes the place of the minimum field width of the
	       converted output	string and the precision of the	string
	       is set to the default value for that particular
	       conversion type;
	       A negative field	width is taken as a - flag followed by
	       a positive field	width (not required in XPG3 mode).

	       The S conversion	character is not tested	in XPG3	mode.

	  98   When message contains %k$*n$.*m$?, where	k, n and m are
	       positive	integers, arg is the kth argument, field width
	       is the nth argument, precision is the mth argument and
	       ? = a type conversion character (d, hi, lo, f, e, g, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d, hi, lo, f, e, g,	s, S], then the	first
	       "*" takes the place of the field	width integer and the
	       second "*" takes	the place of precision integer.	Both
	       take their values from integer arguments. In the	case
	       were the	'$' argument specifiers	are not	used the field
	       width argument must occur first,	the precision argument
	       second and the argument to be converted third;
	       A negative field	width is taken as a - flag followed by
	       a positive field	width (not required in XPG3 mode).
	       A negative precision is taken as	if the precision were
	       omitted (not required in	XPG3 mode).

	       The S conversion	character is not tested	in XPG3	mode.

	  99   When message contains %k$#?, where k = a	positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, o, lo, x, lX, f, e,	g, c,
	       s), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | f | e | c | s] then the result is
	       equivalent to "%k$?", (the "#" flag only	affects	? = [f
	       | e | E]	when a precision of 0 is specified);
	       b. when ? = [o |	lo] then the "#" flag increases	the
	       precision to force the first digit of the result	to be
	       a zero;
	       c. when ? = [x] then the	"#" flag increases the
	       precision to prefix a non-zero result with a "0x";
	       d. when ? = [lX]	then the "#" flag increases the



     Page 19					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       precision to prefix a non-zero result with a "0X";
	       e. when ? = [g] then "#"	flag prevents removal of
	       trailing	zeros from the result so that precision	number
	       of digits are always printed out	after the decimal
	       point character;

	       The d, hi, c and	s directives are tested	in XPG3	mode
	       only.

	  100  When message contains %k$'?, where k = a	positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [c |	C | s |	S ], the "'" flag has no
	       effect on the conversion	of arg and the result is
	       equivalent to "%k$?";
	       b. when ? = [d |	hi | u | lo | f	| e | g], the "'" flag
	       causes the non-monetary grouping	character associated
	       with the	LC_NUMERIC locale to be	inserted into the
	       value according to the non-monetary grouping rules for
	       that locale.

	       This test is not	executed in XPG3 mode.

	  101  When message contains %k$ ?, where k = a	positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [c |	C | s |	S | u |	lo], the " " flag has
	       no effect on the	conversion of arg and the result is
	       equivalent to "%k$?";
	       b. when ? = [d |	hi | f | e | g], the result is
	       equivalent to "%k$?"  except that in the	case that the
	       first character is not a	sign the " " flag prefixes the
	       result with a blank.

	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  102  When message contains %k$+?, where k = a	positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [c |	C | s |	S | u |	lo], the "+" flag has
	       no effect on the	conversion of arg and the result is
	       equivalent to "%k$?";
	       b. when ? = [d |	hi | f | e | g], the result is
	       equivalent to "%k$?"  except that the first character
	       of the result is	always a sign ('+' or '-').



     Page 20					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  103  When message contains %k$-n?, where k = a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$n?" except that it is left justified.

	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  104  When message contains %k$+-n?, where k =	a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$+n?" except that it is	left
	       justified.

	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  105  When message contains %k$ -n?, where k =	a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$ n?" except that it is	left
	       justified.

	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  106  When message contains %k$+ ?, where k = a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$+?".

	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  107  When message contains %k$- +?, where k =	a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, u, lo, f, e, g, c, C, s,
	       S), then	in the message generated by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$-+?".




     Page 21					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       The C and S conversion characters are not tested	in
	       XPG3 mode.

	  108  When message contains %k$+n.*m$?, where k and m are
	       positive	integers, arg is the kth argument, precision
	       is the mth argument, ? =	a type conversion character
	       (d, hi, lo, f, e, g, s, S) and n	= an integer, then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [s |	S | lo], the "+" flag has no effect on
	       the conversion of arg and the result is equivalent to
	       "%n.*m$?";
	       b. when ? = [d |	hi | f | e | g], the result is
	       equivalent to "%n.*m$?"	except that the	first
	       character of the	result is always a sign	('+' or	'-').

	       The S conversion	character is not tested	in XPG3	mode.

	  109  When message contains %k$-n.m?, where k = a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, s, S),	then
	       in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$n.m?" except that the result is left
	       justified.

	       The S conversion	character is not tested	in XPG3	mode.

	  110  When message contains %k$+-n.?, where k = a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, s, S),	then
	       in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$+n.?" except that it is left
	       justified.

	       The S conversion	character is not tested	in XPG3	mode.

	  111  When message contains %k$#.?, where k = a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, s), then in
	       the message generated by	a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | lo], then the resultant
	       conversion is equivalent	to "%k$#?";
	       b. when ? = [d |	hi | lo], and arg = 0 then arg is
	       converted to a null character string;
	       c. when ? = [f |	e | g],	the result is equivalent to
	       "%k$.?" except that the decimal point character is
	       always printed out;
	       d. when ? = s, the result is equivalent to "%k$.s";




     Page 22					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  112  When message contains %k$#*n$.?,	where k	and n are
	       positive	integers, arg is the kth argument, field width
	       is the nth argument and ? = a type conversion character
	       (d, hi, lo, f, e, g, s),	then in	the message generated
	       by a call to syslog(priority, message, arg, ...), the
	       result is equivalent to "%k$#.?"	except that it will
	       have a field width of at	least the value	specified by
	       the argument corresponding to *n$ and in	the case that
	       the converted value has fewer characters	then it	will
	       be padded on the	left with spaces.

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  113  When message contains %k$#.m?, where k =	a positive
	       integer,	arg is the kth argument, m = an	integer	and ?
	       = a type	conversion character (d, hi, lo, f, e, g, s),
	       then in the message generated by	a call to
	       syslog(priority,	message, arg, ...):
	       a. when ? = [d |	hi | f | e | s], the result is
	       equivalent to "%k$.m?";
	       b. when ? = [lo], the result is equivalent to "%k$.m?"
	       except that the result always has a zero	as the first
	       digit;
	       c. when ? = [g],	the result is equivalent to "%k$.m?"
	       except that the decimal point and trailing zeros	are
	       not removed;

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  114  When message contains %k$# +*n$?, where k and n are
	       positive	integers, arg is the kth argument, field width
	       is the nth argument and ? = a type conversion character
	       (d, hi, lo, f, e, g, c, s), then	in the message
	       generated by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$#*n$?"	except that the	first
	       character of a signed conversion	result is always a
	       sign ('+', '-').

	       The d, hi, c and	s directives are tested	in XPG3	mode
	       only.

	  115  When message contains %k$# +-.*m$?, where k and m are
	       positive	integers, arg is the kth argument, precision
	       is the mth argument and ? = a type conversion character
	       (d, hi, lo, f, e, g, s),	then in	the message generated
	       by a call to syslog(priority, message, arg, ...), the



     Page 23					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



	       result is equivalent to "%k$#+.*m$?" except that	it is
	       left justified.

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  116  When message contains %k$# +*n$.*m$?, where k, n	and m
	       are positive integers, arg is the kth argument, field
	       width is	the nth	argument, precision is the mth
	       argument	and ? =	a type conversion character (d,	hi,
	       lo, f, e, g, s),	then in	the message generated by a
	       call to syslog(priority,	message, arg, ...), the	result
	       is equivalent to	"%k$#*n$.*m$?" except that, in the
	       case that the first character of	a signed conversion
	       result is not a sign, a blank is	prefixed to the
	       result.

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  117  When message contains %k$#- +n?,	where k	= a positive
	       integer,	arg is the kth argument	and ? =	a type
	       conversion character (d,	hi, lo,	f, e, g, c, s),	then
	       in the message generated	by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$#n?" except that it is	left justified
	       and, in the case	that the first character of a signed
	       conversion result is not	a sign,	a blank	is prefixed to
	       the result.

	       The d, hi, c and	s directives are tested	in XPG3	mode
	       only.

	  118  When message contains %k$#-*n$.m? , where k and n are
	       positive	integers, arg is the kth argument, field width
	       is the nth argument, ? =	a type conversion character
	       (d, hi, lo, f, e, g, s) and m = an integer, then	in the
	       message generated by a call to
	       syslog(priority,	message, arg, ...), the	result is
	       equivalent to "%k$*n$.m?" except	that it	is left
	       justified.

	       The d, hi and s directives are tested in	XPG3 mode
	       only.

	  119  If the long double type is supported:
		    When message contains %k$L?, where k is a positive
		    integer, arg is the	kth argument and ? is one of
		    the	type conversion	characters f, e, g, E or G,
		    then in the	message	generated by a call to
		    syslog(priority, message, arg, ...), arg is	taken
		    to be a long double	and converted accordingly.



     Page 24					    (printed 2/21/103)






     syslog_L(LSB.os/genuRelease 1.1 (UniSoft Lsyslog_L(LSB.os/genuts)



     Untestable	aspects
	  1    When a call to syslog(priority, message,	...) creates a
	       child process and there has been	a previous call	to
	       openlog(ident, logopt, facility)	in which LOG_NOWAIT
	       was not set in logopt, then the call to syslog()	waits
	       for the child process to	terminate before returning.
	       Reason for omission: The	corresponding statement	in the
	       standard	to which conformance is	being measured is not
	       specific	enough to write	a portable test.  There	is
	       nothing to indicate what	might cause the	implementation
	       to create a child process when syslog() is called.

	  2    When a call to syslog(priority, message,	...) creates a
	       child process and there has been	no previous call to
	       openlog(), then the call	to syslog() waits for the
	       child process to	terminate before returning.
	       Reason for omission: The	corresponding statement	in the
	       standard	to which conformance is	being measured is not
	       specific	enough to write	a portable test.  There	is
	       nothing to indicate what	might cause the	implementation
	       to create a child process when syslog() is called.

	  3    When the	h or l modifier	is used	with a conversion
	       character other than those specified to work with the
	       modifier, then the behaviour is undefined.

	  4    A call to syslog(priority, message, ...), can not
	       contain both '%'	and "%k$", in one message string.
	       Reason for omission: The	corresponding statement	in the
	       standard	to which conformance is	being measured is not
	       specific	enough to write	a portable test.  The XPG does
	       not state what would happen if both were	combined in
	       one message string.

     Grey areas
	  1    The specification does not say what severity value is
	       used when priority does not contain a valid severity
	       value.

	  2    The definition of the precision states that this	is the
	       maximum number of bytes written for the S conversion.
	       However,	because	a S conversion produces	multibyte
	       sequences, it is	unclear	how to treat this in the case
	       that a multibyte	character crosses the precision
	       boundary. No assumptions	are made, though it is
	       expected	that the result	of the conversion would
	       produce a space character as the	last byte.

     RELEASE
	  LSB-os 1.1 (00/11/23)





     Page 25					    (printed 2/21/103)



