From: Heiko Dudzus <heiko.dudzus@gmx.de>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] cron and lib/profile
Date: Tue, 27 Mar 2007 19:21:30 +0200 [thread overview]
Message-ID: <8651978ecfd9dbac02422222459d25ed@voidness.de> (raw)
In-Reply-To: <627937.472.qm@web56201.mail.re3.yahoo.com>
smurfasmurf wrote:
> Cron (w. host=local) does not seem to read $home/lib/profile, so all
> the binds there are missing. Should it not behave as if the user logged
> in and typed the command manually?
With host=local, the command runs in a namespace as in /lib/namespace.
If you need the bindings made in your lib/profile you can use the
explicit name of the CPU server as hostname.
In the latter case, rx(1) and rexexec(8) are used. Rexexec does:
execl("/bin/rc", "rc", "-lc", buf, nil);
to run the commands in it. (The -l flag causes rc to read lib/profile.)
whereas, if host is 'local', cron does:
execl("/bin/rc", "rc", "-c", buf, nil);
The I can't tell if the difference in behaviour is intended. But you
can work around it that way.
Heiko
next prev parent reply other threads:[~2007-03-27 17:21 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 [this message]
2007-03-27 17:33 ` Russ Cox
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=8651978ecfd9dbac02422222459d25ed@voidness.de \
--to=heiko.dudzus@gmx.de \
--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).