From mboxrd@z Thu Jan  1 00:00:00 1970
From: erik quanstrom <quanstro@quanstro.net>
Date: Wed, 17 Apr 2013 13:43:08 -0400
To: 9fans@9fans.net
Message-ID: <3012616258e3da50de2c97c070a8a39e@ladd.quanstro.net>
In-Reply-To: <b188ff55803531e8d316fa326f130e8d@proxima.alt.za>
References: <b188ff55803531e8d316fa326f130e8d@proxima.alt.za>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] pprint and exportfs (and others)
Topicbox-Message-UUID: 42eb2350-ead8-11e9-9d60-3106f5b1d025

On Wed Apr 17 13:38:02 EDT 2013, lucio@proxima.alt.za wrote:
> > In a few cases, the kernel will use pprint to put a diagnostic on the
> > standard error (file descriptor 2).
>
> What's wrong with kprint (or logging) for this?

that's what pprint() does.  it prints info about
the current (offending) process, and then the message.
for other kernel logging, one simply uses print.

there is no kprint in plan 9.  neither can one
syslog from the kernel.

- erik