In message <[EMAIL PROTECTED]>, Chuck Paterson writes:
> Is there reason to believe that we won't have dead lock
>problems from the M_WAITOK? It seems like that if anything in
>the path needed to full fill the malloc needs to log there
>is a problem.
We don't otherwise treat the /dev/console file descriptor magically.
Think about ktracing a process which writes to /dev/console,
debugging it and so on...
One can successfully argue that the relationship between the console
device and syslogd is needlessly incestous but until somebody
restructures the console code to be more sanely (or even just at
all) layered that is a "Sigh.. wouldn't it be nice if..." kind of
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
[EMAIL PROTECTED] | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message