From owner-freebsd-current Sat Nov 25 12:26:15 2000 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (flutter.freebsd.dk [212.242.40.147]) by hub.freebsd.org (Postfix) with ESMTP id D459737B479; Sat, 25 Nov 2000 12:26:09 -0800 (PST) Received: from critter (localhost [127.0.0.1]) by critter.freebsd.dk (8.11.1/8.11.1) with ESMTP id eAPKQ2T20475; Sat, 25 Nov 2000 21:26:02 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: Chuck Paterson Cc: current@FreeBSD.ORG, arch@FreeBSD.ORG Subject: Re: RFC: /dev/console -> /var/log/messages idea/patch In-Reply-To: Your message of "Sat, 25 Nov 2000 12:27:54 MST." <200011251927.MAA17860@berserker.bsdi.com> Date: Sat, 25 Nov 2000 21:26:02 +0100 Message-ID: <20473.975183962@critter> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <200011251927.MAA17860@berserker.bsdi.com>, 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 item. -- Poul-Henning Kamp | UNIX since Zilog Zeus 3.20 phk@FreeBSD.ORG | 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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message