Subject: Re: Bug found: help to isolate it
To: Charles Shannon Hendrix <shannon@widomaker.com>
From: Lista de NetBSD Users <list10@sepc.edu.mx>
List: netbsd-users
Date: 05/21/2002 11:21:51
On Tue, 21 May 2002, Charles Shannon Hendrix wrote:
> On Sun, May 19, 2002 at 03:10:40PM +0200, Manuel Bouyer wrote:
>
> > BTW, I suspect you have some very special setup. I have > 20
> > NetBSD servers (i386, alpha, sparc), some of them with very large
> > uptime (> 500 days) and the only time I've seen that was when someone
> > hit the 'scroll lock' on the console. Unlocking it unwedged syslogd.
>
> Is there a way to have the console scroll through it's buffers even
> when scroll-lock is on?  You could then still freeze a screen, but not
> otherwise hurt the system.

Dont know....

I could have a *special config file* for my kernels...
I remember NetBSD-1.2 and my problem of talkd not working...
The solution was uncomment "options COMPAT_43" and compile
a new kernel.

http://mail-index.netbsd.org/netbsd-help/1996/12/18/0000.html

I never knew if this was a bug... And maybe this situation of
syslogd is simmilar.

Sometimes happen rare things...

Thanks

Heron Gallegos