From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] cron and lib/profile
Date: Tue, 27 Mar 2007 13:33:20 -0400 [thread overview]
Message-ID: <ee9e417a0703271033q24220084h4999747075f5b308@mail.gmail.com> (raw)
In-Reply-To: <8651978ecfd9dbac02422222459d25ed@voidness.de>
This is left over from when localcron was a separate program.
Then it didn't even create a new name space. It just ran as
the local user in the name space in which it started.
It would probably make sense to change cron to do:
putenv("service", "rx");
execl("/bin/rc", "rc", "-lc", buf, nil);
to be more like rexexec. Perhaps $service should be
"cron", but "rx" seems okay.
Russ
next prev parent reply other threads:[~2007-03-27 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-26 17:08 gas
2007-03-27 17:21 ` Heiko Dudzus
2007-03-27 17:33 ` Russ Cox [this message]
2007-03-27 19:05 ` gas
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=ee9e417a0703271033q24220084h4999747075f5b308@mail.gmail.com \
--to=rsc@swtch.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).