9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] kprint
Date: Mon,  1 Oct 2001 11:31:47 -0400	[thread overview]
Message-ID: <20011001153149.AEFDC19AD2@mail.cse.psu.edu> (raw)

William is right on all counts.

I want to add:

	o storage: do you have a circular buffer, or just accept an
	ever-increasing buffer size ?

We use qnoblock(kprintoq, 1), which results in dropping
the tail of the log.  It's an 8k log, so if someone is reading
I don't expect any drops.

	o do you allow user processes to append messages themselves,
	possibly a convenient place to put daemon log messages?

As Rob's man page excerpt pointed out, if you write to
#c/cons on a bitmapped terminal and /dev/kprint is open,
the output only goes to kprint.  That seemed easier to explain
at the time.  So syslog(1, ...) gets sent to kprint if in use.

Russ



             reply	other threads:[~2001-10-01 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-01 15:31 Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-01 14:09 rog
2001-10-01 14:08 ` suspect
2001-10-01 14:16 ` William Josephson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20011001153149.AEFDC19AD2@mail.cse.psu.edu \
    --to=rsc@plan9.bell-labs.com \
    --cc=9fans@cse.psu.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).