9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <charles.forsyth@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] pprint and exportfs (and others)
Date: Wed, 17 Apr 2013 17:52:33 +0100	[thread overview]
Message-ID: <CAOw7k5g2BsJXqmgvFzbi36XCigzefmyBKycKSxwtHnB9TXGXiQ@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1083 bytes --]

In a few cases, the kernel will use pprint to put a diagnostic on the
standard error (file descriptor 2).
One of those is a warning that the process has used more than 100 file
descriptors.
That message is possibly obsolete and could be removed, but there are
others, such as
notifying an uncaught trap that are probably helpful to make visible.
In any case, as things stand, a busy exportfs might have many file
descriptors open,
provoking the diagnostic. Unfortunately, aux/listen and aux/listen1 connect
file
descriptor 2 to the incoming network connection. If the connection's
protocol is
not a simple, unstructured, textual one, diagnostics on the standard error
will cause confusion, in particular to devmnt.c if 9p is used.

/rc/bin/service files that start applications that run special protocols
might want to
redirect file descriptor 2; alternatively, perhaps aux/listen shouldn't
redirect fd 2 by
default: the few commands that do connect the remote user to shells, or
equivalent, including
telnetd and sshd could dup 1 to 2 when that was sensible.

[-- Attachment #2: Type: text/html, Size: 1310 bytes --]

             reply	other threads:[~2013-04-17 16:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-17 16:52 Charles Forsyth [this message]
2013-04-17 17:35 ` lucio
2013-04-17 17:43   ` erik quanstrom
2013-04-17 17:52     ` lucio
2013-04-17 21:07       ` Charles Forsyth
2013-04-17 21:55         ` cinap_lenrek
2013-04-18  2:20           ` erik quanstrom
2013-04-20 19:15 ` cinap_lenrek

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=CAOw7k5g2BsJXqmgvFzbi36XCigzefmyBKycKSxwtHnB9TXGXiQ@mail.gmail.com \
    --to=charles.forsyth@gmail.com \
    --cc=9fans@9fans.net \
    /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).