11-11-2010
no, this isn't DOS, it's tcsh.
let me clarify.
I have the 'set prompt' command in my ~/.cshrc which runs at login.
for some reason this isn't working, as I detailed in my previous post.
to check what happens to the prompt, i just typed the 'set prompt' command in my shell and saw my prompt changes accordingly, but when i change dir the prompt is reset to showing only one level of directories (and not 3 as i wanted). this is probably what causing the default settings from ~/.cshrc not to work.
what can dynamically change $prompt like that?
p.s.
i don't have $PS1 set in my shell by default
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
How to change the UNIX prompt to the default one, after i changed it using PS1?
Thanx and Regards,
Saneesh Joseph. (7 Replies)
Discussion started by: saneeshjose
7 Replies
2. UNIX for Dummies Questions & Answers
Hello,
Why tcsh shell is not recommended ? then which one is better ?
Also can you please let me know how to change own shell and config file? (3 Replies)
Discussion started by: darshakraut
3 Replies
3. UNIX for Dummies Questions & Answers
Can anyone tell me how to reset the command prompt back to the original 'bas'h prompt as these have all been changed via the /etc/profile to add username and hostname but some are too long. I just want to run it in a local .profile to put it back.
Thanks (2 Replies)
Discussion started by: skewbie
2 Replies
4. Shell Programming and Scripting
Hi folks
This is our prompt at the moment
oracle@pinkipinki:/opt/oracle> grep 'set prompt' .cshrc
set prompt = "$user@`uname -n`:$cwd> "
We wish to have in production the same prompt, but red.
Howto do that? I tried a lot a internet manuals, but it doesn't work. (1 Reply)
Discussion started by: slashdotweenie
1 Replies
5. HP-UX
Hi,
I need to find tcsh shell version info on several boxes.
I made a script and running on boxes through SSH.
This is what i am doing :
echo /bin/tcsh -c 'echo $version' | ssh "box name"
but i dont see anything.
if i run /bin/tcsh -c 'echo $version' on ocal machine i see the... (2 Replies)
Discussion started by: kailash19
2 Replies
6. UNIX for Dummies Questions & Answers
Hello,
I have this problem:
I have a server to which I ssh, and it has a special prompt request. The prompt is done by a ?prompt command.
It is fine with SSH, since the prompt I guess gets some input, but when I use SCP, the copy always fails.
So, I was wondering if there is maybe a... (1 Reply)
Discussion started by: lastZenMaster
1 Replies
7. UNIX for Dummies Questions & Answers
Hi, issue with my prompt, other gets their name, my comes with command number. Why?
{118} /home/markb > echo $SHELL
/bin/tcsh
{119} /home/markb > echo $SHELL
/bin/tcsh
{120} /home/markb >
my .cshrc has this....
set prompt="%{\0330;%n@%M : %~%L \007%} `pwd` >%{\033
... (3 Replies)
Discussion started by: samnyc
3 Replies
8. Shell Programming and Scripting
Hello,
I am writing a script that requires the user to enter a string of numbers:
ex: 134 345 865 903
This command only allows for one variable to be entered:
set "var" = $<
and than once I got the array I want to change it to a list with each input on a different line:
... (1 Reply)
Discussion started by: smarones
1 Replies
9. Shell Programming and Scripting
The campus system that I use has switched to using winbind. In the old days, I was able to specify tcsh as my shell with the usual entry in /etc/passwd. But I'm told winbind doesn't have user specific entries, and now my ssh login defaults to a bash shell. Can anybody advise how I can... (2 Replies)
Discussion started by: LeoKSimon
2 Replies
10. Shell Programming and Scripting
Need assistance in getting a solution for a TCSH shell environment variable .
I read on internet that leading zeros as octal numbers and redhat doesnt supports octals but Solaris works on TCSH shell. Is there any way we can fix this . All my script has 08 or 09
$ @ x = 5 + 08
@: Badly formed... (8 Replies)
Discussion started by: ajayram_arya
8 Replies
SU(1) BSD General Commands Manual SU(1)
NAME
su -- substitute user identity
SYNOPSIS
su [-] [-flm] [login [args]]
DESCRIPTION
The su utility requests appropriate user credentials via PAM and switches to that user ID (the default user is the superuser). A shell is
then executed.
PAM is used to set the policy su(1) will use. In particular, by default only users in the ``admin'' or ``wheel'' groups can switch to UID 0
(``root''). This group requirement may be changed by modifying the ``pam_group'' section of /etc/pam.d/su. See pam_group(8) for details on
how to modify this setting.
By default, the environment is unmodified with the exception of USER, HOME, and SHELL. HOME and SHELL are set to the target login's default
values. USER is set to the target login, unless the target login has a user ID of 0, in which case it is unmodified. The invoked shell is
the one belonging to the target login. This is the traditional behavior of su.
The options are as follows:
-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.
- (no letter) The same as -l.
-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 (or -) and -m options are mutually exclusive; the last one specified overrides any previous ones.
If the optional args are provided on the command line, they are passed to the login shell of the target login. Note that all command line
arguments before the target login name are processed by su itself, everything after the target login name gets passed to the login shell.
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.
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).
FILES
/etc/pam.d/su PAM configuration for su.
EXAMPLES
su man -c catman
Runs the command catman as user man. You will be asked for man's password unless your real UID is 0.
su man -c 'catman /usr/share/man /usr/local/man'
Same as above, but the target command consists of more than a single word and hence is quoted for use with the -c option being passed
to the shell. (Most shells expect the argument to -c to be a single word).
su -l foo
Simulate a login for user foo.
su - foo
Same as above.
su - Simulate a login for root.
SEE ALSO
csh(1), sh(1), group(5), passwd(5), environ(7), pam_group(8)
HISTORY
A su command appeared in Version 1 AT&T UNIX.
BSD
September 13, 2006 BSD