Laughably, I got bitten again:
The selector field is separated from the action field
by one or more tab characters.
A tab is a tab, not a few spaces. Again, I copied
a syslog.conf line from another xterm after an upgrade
and spent half an hour wondering why my logfile stays empty.
This is entirely user error, but anyway:
is it on purpose that we require the separators
to be tabs, not spaces? I understand this is
what the original syslog had.
Would there be any opposition to also allowing spaces?
The '\t' seems to be hardcoded into usr.sbin/syslogd.c
but it seems easy enough to extend it to allow ' ' as well.
If we stay with tabs only, should the manpage emphasize "not spaces"?
Also, making the mistake I made results in the line
just being ignored; the log file is never written to.
Should the starting syslogd complain about lines
with space but not tabs?
