Bug 27088

Summary:	syslogd(8) doesn't create log files if they are inexistant
Product:	Base System	Reporter:	reel <reel>
Component:	bin	Assignee:	Mike Barcroft <mike>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.3-STABLE
Hardware:	Any
OS:	Any

Description reel 2001-05-05 06:00:03 UTC

When /var is empty (due to loss of data), syslogd(8) doesn't create
them at boot time but, it tells you that they are inexistant.

How-To-Repeat: rm -rf /var/log
and reboot

Comment 1 dwmalone 2001-05-07 16:47:05 UTC

On Fri, May 04, 2001 at 09:56:50PM -0700, reel@sympatico.ca wrote:

> >Description:
> When /var is empty (due to loss of data), syslogd(8) doesn't create
> them at boot time but, it tells you that they are inexistant.

This is the correct (or atleast traditional) behaviour of syslogd,
because it doesn't know what permissions to create them with. I'll
close the PR if you've no further objections.

	David.

Comment 2 Mike Barcroft freebsd_committer

2001-07-18 05:36:41 UTC

Responsible Changed
From-To: freebsd-bugs->mike

This behaviour should be documented in syslogd(8). 
I'll take care of it.

Comment 3 Mike Barcroft freebsd_committer

2001-07-18 15:45:33 UTC

State Changed
From-To: open->closed

The behaviour of syslogd(8), with regards to not logging to 
files that do not exist, has been documented on -CURRENT. 
This change is scheduled to be merged into the -STABLE branch 
in 10 days.