From xaa@xaa.stack.nl  Sun Dec  8 13:03:52 1996
Received: from terra.stack.nl (terra.stack.nl [131.155.140.128])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id NAA23556
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 8 Dec 1996 13:03:50 -0800 (PST)
Received: from xaa.stack.nl (uucp@localhost) by terra.stack.nl (8.8.4) with UUCP id VAA13274 for FreeBSD-gnats-submit@freebsd.org; Sun, 8 Dec 1996 21:59:47 +0100 (MET)
Received: (from xaa@localhost) by xaa.stack.nl (8.8.4/8.8.2) id WAA01296; Sun, 8 Dec 1996 22:03:03 +0100 (MET)
Message-Id: <199612082103.WAA01296@xaa.stack.nl>
Date: Sun, 8 Dec 1996 22:03:03 +0100 (MET)
From: Mark Huizer <xaa@xaa.stack.nl>
Reply-To: xaa@xaa.stack.nl
To: FreeBSD-gnats-submit@freebsd.org
Subject: syslogd (again) won't write to /dev/ttyv*
X-Send-Pr-Version: 3.2

>Number:         2176
>Category:       bin
>Synopsis:       syslogd won't log to /dev/ttyv* devices
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    peter
>State:          closed
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Dec  8 13:10:01 PST 1996
>Closed-Date:    Tue Dec 10 15:31:07 PST 1996
>Last-Modified:  Tue Dec 10 15:31:36 PST 1996
>Originator:     Mark Huizer
>Release:        FreeBSD 3.0-CURRENT i386
>Organization:
>Environment:

	Current as of 5 december

>Description:

	syslogd won't log any messages to /dev/ttyv* devices. This
	happens on two machines that had working syslogd's and did
	a make world with recent currents (both 5 december or later).
	Since I can't switch to the virtual console too, I think it's
	not even opened for writing

>How-To-Repeat:

	put something in /etc/syslogd.conf that logs to
	/dev/ttyvsomething and see if it logs or opens the device

>Fix:
	
	

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->analyzed 
State-Changed-By: peter 
State-Changed-When: Sun Dec 8 19:13:02 PST 1996 
State-Changed-Why:  
I think this is actually a syscons problem, not a syslogd one. 

There is a known problem recently introduced into syscons that would 
explain this.  Please try turning a getty on the virtual console that you 
wish to log to, that should make it the data show up without having to 
change syslogd. 

The syscons problems are described in detail by Bruce Evans in a reply 
to PR2118 called "failure to write output to vc without input". 
State-Changed-From-To: analyzed->feedback 
State-Changed-By: peter 
State-Changed-When: Tue Dec 10 09:52:39 PST 1996 
State-Changed-Why:  
I've changed syslogd so that it maintains it's original behavior 
of keeping an open file on the tty.  This should allow switching to 
the screen again, like it always used to do. 

Please check that rev 1.16 of syslogd.c works as expected. 
Responsible-Changed-From-To: freebsd-bugs->peter 
Responsible-Changed-By: peter 
Responsible-Changed-When: Tue Dec 10 09:54:39 PST 1996 
Responsible-Changed-Why:  
This is related to my changes here. 
State-Changed-From-To: feedback->closed 
State-Changed-By: peter 
State-Changed-When: Tue Dec 10 15:31:07 PST 1996 
State-Changed-Why:  
Submitter confirms working. 
>Unformatted:
