01-12-2009
csh is already my default shell. If I'm running csh scripts, are all of those files (/etc/csh.cshrc, /etc/csh.login, $HOME/.cshrc, $HOME/.login, $HOME/.tcshrc, $HOME/.history) still processed? If so, that explains it. The .cshrc file is huge.
How can I make csh skip those files? You see, csh is the default shell at my company, and the .cshrc is necessary because it sets up a lot of environment variables for our software. I can't remove the .cshrc... so can I skip it?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I just set up an ftp server with Red Hat 5.2. I am doing the work, I'm baby stepping, but it seems like every step I get stuck. Currently, I'm trying to set up a crontab job, but I'm getting the following message: /bin/sh: /usr/bin/vi: No such file or directory. I see that vi exists in /bin/vi,... (3 Replies)
Discussion started by: kwalter
3 Replies
2. Shell Programming and Scripting
Hi,
1. How to Write csh CGI-BIN script which return a web page which show the environment of the executed script ?
2. How do we read command line on csh and ksh ?
Thank's (2 Replies)
Discussion started by: 7eleven
2 Replies
3. UNIX for Dummies Questions & Answers
Hi All,
Can somebody tell me the difference between /bin, /usr/bin, /sbin ?
Thanx in advance,
Saneesh Joseph (3 Replies)
Discussion started by: saneeshjose
3 Replies
4. Shell Programming and Scripting
Hey everyone,
A coworker of mine has written a csh script that starts with #!/usr/bin/csh -f. It's my understanding that the -f should skip the .cshrc and .login files, but here's the problem: In the script "line" is used, and I happen to have a "line" in my ~/bin. When the script is ran my... (4 Replies)
Discussion started by: effigy
4 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I have a problem I don't understand with fuser.
I launch a simple shell script mysleep.sh:
I launch the command fuser -fu mysleep.sh but fuser doesn't return anything excepted:
mysleep:
Then I modify my script switching from #!/bin/sh to #!/bin/ksh
I launch the command fuser -fu... (4 Replies)
Discussion started by: Peuj
4 Replies
6. Shell Programming and Scripting
Hi,
I have a script which I need to modify. It contains the following statement at the beginning -
1. What does this mean ?
#!/bin/csh -f
2. If I run the following code in a script on C SHELL it runs normally.
host=0
if ; then
host="<<something>>"
fi
But, in the script... (7 Replies)
Discussion started by: angshuman_ag
7 Replies
7. OS X (Apple)
Q1. I understand that /usr/local/bin means I can install/uninstall stuff in here and have any chance of messing up my original system files or effecting any other users. I created this directory myself.
But what about the directory I didn't create, namely /Users/m/bin? How is that directory... (1 Reply)
Discussion started by: michellepace
1 Replies
8. AIX
Hi,
I am planning to install a version of Informatica on my AIX box. It requires a specific java build in pap6470_27sr2-20141101_01(SR2).
The current link for IBM 64-bit SDK for AIX®, JavaTM Technology Edition, Version 7 Release 1 has a more recent version in j7r164redist.7.1.0.75.bin.
Is... (4 Replies)
Discussion started by: meetpraveens
4 Replies
9. UNIX for Beginners Questions & Answers
I tried to source the csh file into the bin/sh(input file is srcinput.sh ).
Its(csh -f ...csh) not working.
I tried to source like csh -f D:/sample/expand/env.csh
env.csh sets the environment and it source another .csh file using
source fname.csh.
fname.csh it sets one... (2 Replies)
Discussion started by: SA_Palani
2 Replies
10. Shell Programming and Scripting
Some question about the usage of shell scripts:
1.) Are the commands of the base shell scripts a subset of bash commands?
2.) Assume I got a long, long script WITHOUT the first line.
How can I find out if the script was originally designed für "sh" or "bash"?
3.) How can I check a given... (3 Replies)
Discussion started by: pstein
3 Replies
LEARN ABOUT OPENDARWIN
su
SU(1) BSD General Commands Manual SU(1)
NAME
su -- substitute user identity
SYNOPSIS
su [-flm] [login] [-c shell arguments]
DESCRIPTION
su requests the password for login and switches to that user and group ID after obtaining proper authentication. A shell is then executed,
and any additional shell arguments after the login name are passed to the shell. If su is executed by root, no password is requested and a
shell with the appropriate user ID is executed.
The options are as follows:
-c Invoke the following command in a subshell as the specified user.
-f If the invoked shell is csh(1), this option prevents it from reading the ``.cshrc'' file.
-l Simulate a full login. The environment is discarded except for HOME, SHELL, PATH, TERM, and USER. HOME and SHELL are modified as
above. USER is set to the target login. PATH is set to ``/bin:/usr/bin''. TERM is imported from your current environment. The
invoked shell is the target login's, and su will change directory to the target login's home directory. This option is identical to
just passing "-", as in "su -".
-m Leave the environment unmodified. The invoked shell is your login shell, and no directory changes are made. As a security precau-
tion, if the target user's shell is a non-standard shell (as defined by getusershell(3)) and the caller's real uid is non-zero, su
will fail.
The -l and -m options are mutually exclusive; the last one specified overrides any previous ones.
Only users in group ``wheel'' (normally gid 0) or group ``admin'' (normally gid 20) can su to ``root''.
By default (unless the prompt is reset by a startup file) the super-user prompt is set to ``#'' to remind one of its awesome power.
SEE ALSO
csh(1), login(1), sh(1), skey(1), kinit(1), kerberos(1), passwd(5), group(5), environ(7)
ENVIRONMENT
Environment variables used by su :
HOME Default home directory of real user ID unless modified as specified above.
PATH Default search path of real user ID unless modified as specified above.
TERM Provides terminal type which may be retained for the substituted user ID.
USER The user ID is always the effective ID (the target user ID) after an su unless the user ID is 0 (root).
HISTORY
A su command appeared in Version 7 AT&T UNIX.
BSD
April 18, 1994 BSD