[Bug 382096] Re: syslog(3) doesn't cover openlog()'s ident being NULL

[Michael Kerrisk]

Upstream man-pages-3.41 patches as follows:

--- a/man3/syslog.3
+++ b/man3/syslog.3
@@ -66,6 +66,13 @@ opens a connection to the system logger for a program.
 The string pointed to by
 .I ident
 is prepended to every message, and is typically set to the program name.
+If
+.I ident
+is NULL, the program name is used.
+(POSIX.1-2008 does not specify the behavior when
+.I ident
+is NULL.)
+
 The
 .I option
 argument specifies flags which control the operation of

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to manpages in Ubuntu.
https://bugs.launchpad.net/bugs/382096

Title:
  syslog(3) doesn't cover openlog()'s ident being NULL

Status in “manpages” package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 9.04, manpages-dev 3.15-1.

  syslog(3) documents openlog(ident, option, facility).  It doesn't
  describe what happens if openlog is passed NULL as an ident.  It does
  say that syslog itself will do this if syslog is called without
  openlog having been called previously.  So, either I can pass NULL to
  openlog myself, or syslog may do so, but what will that do in terms of
  the data logged?

  Empirically, it seems the basename of argv[0] will be used.  This
  should be documented.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/manpages/+bug/382096/+subscriptions