On 9 Nov, Don Lewis wrote:
> On 9 Nov, Bruce Evans wrote:
>> On Sat, 8 Nov 2003, Don Lewis wrote:
>>> This is totally consistent until I "kill
>>> -HUP" syslogd, which I believe causes syslogd to close and open
>>> /dev/console, after which the syslog output appears correct on the
>>> console. W
On 9 Nov, Bruce Evans wrote:
> For a non-half-baked fix, do somethng like:
> - never block in ttymsg(), but always wait for output to drain using
> tcdrain() in a single child process. It's probably acceptable for
> this to not report errors to ttymsg()'s caller.
> - limit children better.
On 9 Nov, Bruce Evans wrote:
> On Sat, 8 Nov 2003, Don Lewis wrote:
>
>> I've been seeing some wierd things for many months when using a serial
>> console on my -CURRENT box. I finally had a chance to take a closer
>> look today.
>>
>> It looks like the problem is some sort of interference betwe
On Sat, 8 Nov 2003, Don Lewis wrote:
> I've been seeing some wierd things for many months when using a serial
> console on my -CURRENT box. I finally had a chance to take a closer
> look today.
>
> It looks like the problem is some sort of interference between kernel
> output to the console and u
I've been seeing some wierd things for many months when using a serial
console on my -CURRENT box. I finally had a chance to take a closer
look today.
It looks like the problem is some sort of interference between kernel
output to the console and userland writes to /dev/console. I typically
see
