From nobody  Tue Nov 24 08:45:00 1998
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA10187;
          Tue, 24 Nov 1998 08:45:00 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199811241645.IAA10187@hub.freebsd.org>
Date: Tue, 24 Nov 1998 08:45:00 -0800 (PST)
From: support@uunet.ca
To: freebsd-gnats-submit@freebsd.org
Subject: /usr/sbin/syslogd stops logging
X-Send-Pr-Version: www-1.0

>Number:         8847
>Category:       i386
>Synopsis:       /usr/sbin/syslogd stops logging
>Confidential:   no
>Severity:       serious
>Priority:       low
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Nov 24 08:50:01 PST 1998
>Closed-Date:    Wed Dec 30 11:10:34 PST 1998
>Last-Modified:  Wed Dec 30 11:13:40 PST 1998
>Originator:     Support
>Release:        2.2.6-RELEASE
>Organization:
Support
>Environment:
FreeBSD machine.name 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Wed Mar 25
02:2:49 GMT 1998 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386
>Description:
After a random period of time, syslog will stop logging but will
not exit. It must be killed and restarted manually. Oddly enough,
it *will* log itself being killed, but otherwise it logs nothing.
>How-To-Repeat:
Simply wait and log a whole *pile* of stuff. We're logging a lot
of stuff on one of these machines and syslogd seems to not handle
it very well. Considering upgrading machine to 3.0-RELEASE if no
workaround or patch information becomes available.
>Fix:
None, unless you consider restarting it manually a 'fix'.
>Release-Note:
>Audit-Trail:

From: support@uunet.ca
To: freebsd-gnats-submit@FreeBSD.ORG
Cc:  Subject: i386/8847: /usr/sbin/syslogd stops logging
Date: Tue, 24 Nov 1998 08:45:00 -0800 (PST)

 >Number:         8847
 >Category:       i386
 >Synopsis:       /usr/sbin/syslogd stops logging
 >Confidential:   no
 >Severity:       serious
 >Priority:       low
 >Responsible:    freebsd-bugs
 >State:          open
 >Quarter:
 >Keywords:
 >Date-Required:
 >Class:          sw-bug
 >Submitter-Id:   current-users
 >Arrival-Date:   Tue Nov 24 08:50:01 PST 1998
 >Last-Modified:
 >Originator:     Support
 >Organization:
 Support
 >Release:        2.2.6-RELEASE
 >Environment:
 FreeBSD machine.name 2.2.6-RELEASE FreeBSD 2.2.6-RELEASE #0: Wed Mar 25
 02:2:49 GMT 1998 jkh@time.cdrom.com:/usr/src/sys/compile/GENERIC i386
 >Description:
 After a random period of time, syslog will stop logging but will
 not exit. It must be killed and restarted manually. Oddly enough,
 it *will* log itself being killed, but otherwise it logs nothing.
 >How-To-Repeat:
 Simply wait and log a whole *pile* of stuff. We're logging a lot
 of stuff on one of these machines and syslogd seems to not handle
 it very well. Considering upgrading machine to 3.0-RELEASE if no
 workaround or patch information becomes available.
 >Fix:
 None, unless you consider restarting it manually a 'fix'.
 >Audit-Trail:
 >Unformatted:
 
 To Unsubscribe: send mail to majordomo@FreeBSD.org
 with "unsubscribe freebsd-bugs" in the body of the message
 
 

From: skynyrd@opus.cts.cwu.edu
To: FreeBSD-gnats-submit@FreeBSD.org, support@uunet.ca
Cc:  Subject: Re: i386/8847: /usr/sbin/syslogd stops logging
Date: Tue, 29 Dec 1998 19:24:14 -0800 (PST)

 Can you have a look at:
 
     http://www.freebsd.org/cgi/query-pr.cgi?pr=8865
 
 and tell me if your 'random' period of time might actually correspond to
 some interval in /etc/newsyslog.conf?
 
 Also please advise if there is anything else your case has in common with bin/8865.
 
 -Chris
 

From: UUNET Canadian Support <support@uunet.ca>
To: skynyrd@opus.cts.cwu.edu
Cc: FreeBSD-gnats-submit@FreeBSD.org, support@uunet.ca
Subject: Re: i386/8847: /usr/sbin/syslogd stops logging 
Date: Wed, 30 Dec 1998 10:03:00 -0500

 Hi Chris,
 
 I am not quite sure why this message was mailed to support@uunet.ca.  Could
 further explaination be provide as to what you are looking for and how
 this applies to uunet canada.   
 
 Thanks,
 
 Henry
 
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 Technical Support in Canada        
 UUNET, an MCI WorldCom company 
 support@uunet.ca      (416) 216-5101,  (888) 886 3865   fax:  (416) 368-5473
 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
 --------
 >
 >Can you have a look at:
 >
 >    http://www.freebsd.org/cgi/query-pr.cgi?pr=8865
 >
 >and tell me if your 'random' period of time might actually correspond to
 >some interval in /etc/newsyslog.conf?
 >
 >Also please advise if there is anything else your case has in common with bin/8865.
 >
 >-Chris
 >

From: Chris Timmons <skynyrd@opus.cts.cwu.edu>
To: freebsd-gnats-submit@freebsd.org
Cc:  Subject: Re: i386/8847: /usr/sbin/syslogd stops logging
Date: Wed, 30 Dec 1998 11:09:11 -0800 (PST)

 ---------- Forwarded message ----------
 Date: Wed, 30 Dec 1998 10:15:27 -0600 (CST)
 From: Michael Hughes <mhughes@logroad.bridge.com>
 To: skynyrd@opus.cts.cwu.edu
 Cc: freebsd-bugs@FreeBSD.ORG
 Subject: Re: i386/8847: /usr/sbin/syslogd stops logging
 
   I thought I would add something here, I had them same thing happen to me
 just about a month ago.  The system had been up for about 3 month.  I had
 processes haning and alike.  Come to find out, I had used the scroll lock
 to look at some error message on the console that root was logged in as.
 Since I run X as a use, I didn't even think about root being logged in
 on the console.  I hit scroll, and syslog entries flew by.  Hope this
 helps, if nothing else FYI.
 
State-Changed-From-To: open->closed  
State-Changed-By: cwt 
State-Changed-When: Wed Dec 30 11:10:34 PST 1998 
State-Changed-Why:  
Closed by request of support@uunet.ca, which was an unfortunate choice 
for a reply-to address by the submitter.  I believe that PR #8865 is 
describing the same problem, so we will continue our efforts there. 
>Unformatted:
