From: Russ Cox <russcox@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] rc internals
Date: Fri, 4 Feb 2005 11:52:44 -0500 [thread overview]
Message-ID: <ee9e417a05020408523267f1b4@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.60.0502041123030.10711@athena>
> I'm looking into a bug in the p9p rc that pops up
> on my freebsd machine. Sometimes subshells don't
> return what they ought (or so it currently seems).
A few others have reported that bug too.
Your trace is helpful. I didn't even know about rc -r.
Try putting
print("notifyf pid %d: %s\n", getpid(), s);
at the top of notifyf.
Russ
prev parent reply other threads:[~2005-02-04 16:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 16:32 Sam
2005-02-04 16:52 ` Russ Cox [this message]
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=ee9e417a05020408523267f1b4@mail.gmail.com \
--to=russcox@gmail.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).