% setenv NAME value C shell
$ NAME=value; export NAME Bourne or Korn shell
As a rule, Csh doesn't need to export it's variables - it does it
automatically.
Post the contents of your ~/.cshrc...
Maybe this will help:
Bourne Shell
The original Bourne shell has one file that it reads when you log in: it's
called .profile and is in your home directory. Put all your setup commands
there.
The Bourne shell doesn't read .profile when you start a subshell , though.
Subshell setup information has to come from environment variables that were
set in .profile when you first logged in or from commands you typed since.
C Shell
C shell users have three shell setup files available:
* The .cshrc file is read any time a C shell starts - that includes
shell escapes and shell scripts. [1] This is the place to put commands that
should run every time you start a shell. For instance, shell variables like
cdpath and prompt should be set here. Aliases should, too. Those things
aren't passed to subshells through the environment, so they belong in
.cshrc.
[1] If you write a csh script, you should probably
use the -f option to keep C shell scripts from reading .cshrc. Of course,
even better, you probably shouldn't use csh for scripts.
* The .login file is read when you start a login shell. Here's where
you should set:
* Environment variables (which UNIX will pass to subshells
automatically)
* Commands like tset and stty
* Commands you want to run every time you log in - checking for mail
and news, running fortune, checking your calendar for the day, etc.
Note that .cshrc is read before .login.
* The shell reads .logout when you end a login shell.
Korn Shell
The Korn shell is a lot like the Bourne shell. A login Korn shell will read
the .profile first. The .profile can set the ENV environment variable to the
pathname of a file (typically $HOME/.kshrc). Then any Korn shell during that
login session (including a subshell) will read the file named by $ENV as it
starts up, before it runs other commands.
bash
bash is something of a cross between the Bourne and C shells. A login bash
will read .bash_profile, .bash_login, or .profile. A bash subshell - but not
a login shell - will read a file named .bashrc in your home directory. The
shell reads .bash_logout when you end a login shell; you can set a trap to
handle non-login shells.
tcsh
tcsh is like the C shell, with one exception: if you put a file named
.tcshrc in your home directory, tcsh will read it instead of .cshrc.
> -----Original Message-----
> From: Loke Kit Kai [SMTP:[EMAIL PROTECTED]]
> Sent: Tuesday, October 02, 2001 3:58 PM
> To: [EMAIL PROTECTED]
> Subject: RE: [newbie] Command not found
>
> i default my shell to csh... how do I make the login script export the
> path
> to subshells? or how do I change to other shell since my root account have
> no problem?
>
>
**********************************************************************
This email and any files sent with it are intended only for the named
recipient. If you are not the named recipient please telephone/email
the sender immediately. You should not disclose the content or
take/retain/distribute any copies.
**********************************************************************
Norwich Union Life & Pensions Limited
Registered Office 2 Rougier Street
York YO90 1UU
Registered in England Number 3253947
A member of the Norwich Union Marketing Group
which is regulated by the Personal Investment Authority.
Member of the Association of British Insurers.
For further Enquires 01603 622200
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
