Re: b_to_q to a clist with no reserved cblocks

2002-03-15 Thread Bill Fenner
I don't know exactly what causes the b_to_q message. It is most likely a race in close. You can first-open tty's that are blocked in last-close, and having this open succeed is very important for unblocking the close usi9ng comcontrol /dev/foo drainwait small, but the tty system doesn't seem

b_to_q to a clist with no reserved cblocks

2002-03-10 Thread Robert Watson
Just noticed the following for the first time today? (a) b_to_q console message, and (b), the truncated 'Mar' which presumably has to do with syslogd getting killed, some buffer getting flushed, or the like. The b_to_q thing is what I'm wondering about. # reboot Mar 10 18:36:39 reboot:

Re: b_to_q to a clist with no reserved cblocks

2002-03-10 Thread Bruce Evans
On Sun, 10 Mar 2002, Robert Watson wrote: Just noticed the following for the first time today? (a) b_to_q console message, and (b), the truncated 'Mar' which presumably has to do with syslogd getting killed, some buffer getting flushed, or the like. The b_to_q thing is what I'm wondering