src/usr.sbin/syslogd, branch releng/5.0

Uniformly refer to a file system as "file system".

2002-12-12T17:26:04Z

Approved by: re

mdoc(7) police: markup fixes.

2002-11-27T15:31:08Z

Approved by: re

Factor out the code that determines whether a message must be skipped

2002-11-07T19:53:29Z

as a consequence of a host or program name specification into a common function, skip_pmessage. Reviewed by: roberto

Add used #include .

2002-10-27T17:46:53Z

Sync usage() with reality and sort it alphabetically.

2002-10-18T11:48:46Z

PR: 42620 Submitted by: Jeff Ito MFC after: 1 month

Add -c option to synopsis. Sort it alphabetically, too.

2002-10-18T11:42:21Z

Avoid referencing a removed (and freed) queue entry. This partially reverts

2002-10-06T17:43:04Z

revision 1.101 (which did not introduce the bug but made it harder to fix) PR: misc/40363 Submitted by: David Dunham MFC after: 2 weeks

Introduce to the !program specification a capability similar to the one

2002-09-23T11:59:19Z

that already exists for hosts: being able to specify a section that applies to every program *except* the one in question. The normal syntax for program specification is still valid. For the new capability, one uses: !-program Since there is no way to specify a program beginning with a dash in the old syntax, as it would be interpreted as the case above, the following alternative syntax to the original capability is provided: !+program This shouldn't introduce incompatibilities with any syslogd configuration in production because -stable's syslogd does not support a dash anywhere in the program specification. MFC after: 2 weeks

Make syslogd -u treat "*" as all levels by explictly setting pri_cmp

2002-09-04T21:11:25Z

for it. While I'm here, add a the ability to say "!level" in a way which should be compatible with Linux's syslogd. PR: 28935 No objections: audit MFC after: 2 weeks

Don't give up on a remote log host when we get a EHOSTUNREACH or

2002-08-25T06:05:25Z

EHOSTDOWN. These are often transient errors (when the remote host reboots, temporary network problems, etc.), and we'd rather err on the side of caution and keep trying send messages that never arrive than just give up. Note that this is not an implementation of the "back-off" methods given in the PR. Those just seem too complicated. Why not just keep trying each time? Trying and failing doesn't really consume significantly more resources than if we were successful for each message. PR: bin/31029 MFC after: 1 week