documentation: sb-posix:syslog -- please describe PRIORITY

Bug #811707 reported by mon_key
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SBCL
Won't Fix
Undecided
Unassigned

Bug Description

Please indicate that "severity level PRIORITY" is an (integer 0 *).

Actually, on this system a negative integer is feasible but syslog complains about it...
 (sb-posix:syslog -1 "hey syslog does this make you wince")
 => "sbcl: syslog: unknown facility/priority: ffffffff"

It might also be useful to indicate what the various levels indicate, e.g.:

0 -- sb-posix:log-emerg system is unusable
1 -- sb-posix:log-alert action must be taken immediately
2 -- sb-posix:log-crit critical conditions
3 -- sb-posix:log-err error conditions
4 -- sb-posix:log-warning warning conditions
5 -- sb-posix:log-notice normal, but significant, condition
6 -- sb-posix:log-info informational message
7 -- sb-posix:log-debug debug-level message

What sucks is that this information is already availabe in sbcl/contrib/sb-posix/constants.lisp but doesn't seet to get incorporated/exposed in any user friendly way. IOW, the user has to know that the above symbols exist in order to inspect them...

Likewise, the same situation holds for sb-posix:openlog and the optional FACILITY arg.
E.g. all of the following are available and documented and mostly unexposed.

sb-posix:log-authpriv
sb-posix:log-cons
sb-posix:log-cron
sb-posix:log-daemon
sb-posix:log-ftp
sb-posix:log-kern
sb-posix:log-pid
sb-posix:log-lpr
sb-posix:log-mail
sb-posix:log-news
sb-posix:log-ndelay
sb-posix:log-nowait
sb-posix:log-odelay
sb-posix:log-perror
sb-posix:log-syslog
sb-posix:log-user
sb-posix:log-uucp
sb-posix:log-local0
sb-posix:log-local1
sb-posix:log-local2
sb-posix:log-local3
sb-posix:log-local4
sb-posix:log-local5
sb-posix:log-local6
sb-posix:log-local7

--
/s_P\

Revision history for this message
Douglas Katzman (dougk) wrote :

The translation from C name to Lisp name is easily deducible.
It's not incumbent upon SBCL sources to document the meaning of the constants. They're in the man page.
Compare to https://golang.org/pkg/log/syslog/#Priority

Changed in sbcl:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.