Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!linus!philabs!cmcl2!seismo!lll-crg!lll-lcc!ucdavis!ucbvax!ucsfcgl!ucsfcca!dick
From: dick@ucsfcca.UUCP (Dick Karpinski)
Newsgroups: net.unix,net.unix-wizards
Subject: Re: Solution to cron+script+syslog problem
Message-ID: <441@ucsfcca.UUCP>
Date: Thu, 20-Feb-86 19:27:22 EST
Article-I.D.: ucsfcca.441
Posted: Thu Feb 20 19:27:22 1986
Date-Received: Mon, 24-Feb-86 06:59:18 EST
References: <671@well.UUCP>
Reply-To: dick@ucsfcca.UUCP (Dick Karpinski)
Organization: UCSF Computer Center
Lines: 22
Keywords: cron shell syslog environment rlogin
Xref: linus net.unix:6620 net.unix-wizards:14082
Summary: rlogin for short

In article <671@well.UUCP> rlw@well.UUCP (Bob Weissman) writes:
>
>The problem is the lack of environment under cron.  Little goodies
>you expect to be set, such as $USER and $PATH don't exist.  In fact
>the entire environment, as printed out by printenv under cron is:
>HOME=/
>
>So the solution was to check for unset variables and set the ones you
>need.
>
If you are running 4.2 BSD, doesn't rlogin to this machine provide
all the environment just like the one you use while developing?
That is, if "rlogin ucsfcca" is the first executable line of my
C-shell script and "logout" is the last, I think things will work
much as they would during development of the shellscript.  Right?

Dick
-- 
Dick Karpinski    Manager of Unix Services, UCSF Computer Center
UUCP: ...!ucbvax!ucsfcgl!cca.ucsf!dick   (415) 666-4529 (12-7)
BITNET: dick@ucsfcca   Compuserve: 70215,1277  Telemail: RKarpinski
USPS: U-76 UCSF, San Francisco, CA 94143