From: arisawa <arisawa@ar.aichi-u.ac.jp>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] bug in rc(1) ?
Date: Sat, 29 Nov 2014 13:42:56 +0900 [thread overview]
Message-ID: <23F46ED5-A8A6-4677-A01E-6CF1BCC51C7D@ar.aichi-u.ac.jp> (raw)
rc(1) says:
rfork [nNeEsfFm]
Become a new process group using rfork(flags) where
flags is composed of the bitwise OR of the rfork flags
specified by the option letters (see fork(2)). If no
flags are given, they default to ens. The flags and
their meanings are: n is RFNAMEG; N is RFCNAMEG; e is
RFENVG; E is RFCENVG; s is RFNOTEG; f is RFFDG; F is
RFCFDG; and m is RFNOMNT.
this sounds to me
rfork
is equivalent to
rfork ens
or am I misunderstanding?
Kenji Arisawa
next reply other threads:[~2014-11-29 4:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 4:42 arisawa [this message]
2014-11-29 4:57 ` minux
2014-11-30 10:27 ` arisawa
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=23F46ED5-A8A6-4677-A01E-6CF1BCC51C7D@ar.aichi-u.ac.jp \
--to=arisawa@ar.aichi-u.ac.jp \
--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).