Skip site navigation (1)Skip section navigation (2) 
Date:      Wed, 5 Jan 2000 21:57:10 -0500 (EST)
From:      "Crist J. Clark" <cjc@cc942873-a.ewndsr1.nj.home.com>
To:        keramida@ceid.upatras.gr
Cc:        ben@scientia.demon.co.uk (Ben Smithurst), osiris2002@yahoo.com (Joss Roots), freebsd-questions@FreeBSD.ORG
Subject:   Re: HELP: cron & /etc/periodic question. (it was the PATH environ.)
Message-ID:  <200001060257.VAA18062@cc942873-a.ewndsr1.nj.home.com>
In-Reply-To: <20000105235223.B391@hades.hell.gr> from Giorgos Keramidas at "Jan 5, 2000 11:52:23 pm"
next in thread | previous in thread | raw e-mail | index | archive | help 
Giorgos Keramidas wrote,
> On Tue, Jan 04, 2000 at 08:49:17PM +0000, Ben Smithurst wrote:
> > Joss Roots wrote:
> > 
> > > I discovered that changing the relative path to an absolute one
> > > resolves the problem and the scripts is actually executed. cron was
> > > just ignoring the script, which called another 2 scripts. but when I
> > > added the full path, it worked.
> > >
> > > OK now the user root, should export his PATH environmental variable,
> > > so I am using tcsh how can I do this.
> > 
> > I don't use tcsh, so I don't know. I think it's something like "setenv
> > PATH /foo:/bar".
> 
> It seems that changing the `path' variable or the `PATH' environment
> variable affects both these variables.  I am using /bin/csh from a
> fairly up-to-date 3.4-STABLE system.
> 
>     [hades!charon:~] /bin/csh
>     You have mail.
>     % echo $path
>     /sbin /bin /usr/sbin /usr/bin
>     % echo $PATH
>     /sbin:/bin:/usr/sbin:/usr/bin
>     % set path = ( . )
>     % echo $path
>     .
>     % echo $PATH
>     .
>     % setenv PATH /bin:
>     % echo $path
>     /bin .
>     % echo $PATH
>     /bin:
>     % exit

RTFM, csh(1):

           setenv
           setenv name
           setenv name value
                   The first form lists all current environment variables.  It
                   is equivalent to printenv(1).  The last form sets the value
                   of environment variable name to be value, a single string.
                   The second form sets name to an empty string.  The most
                   commonly used environment variables USER, TERM, and PATH
                   are automatically imported to and exported from the csh
                   variables user, term, and path; there is no need to use
                   setenv for these.
-- 
Crist J. Clark                           cjclark@home.com


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message

Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200001060257.VAA18062>