I am learning shell scripting for the first time. I use AT&T Korn Shell, Version AJM 93u+ 2012-08-01, compiled from source on NetBSD.
So far I have managed to set up what I think is a useful and pleasing shell prompt, which can be seen in the image attached to this post.
The prompt is a multi-line prompt, as follows:
Line 1 (reverse video) shows the TERM variable, together with TTY, SHELL, and the date and time as it was when the prompt was updated.
(The print -f statement formats this line so that the text is right-aligned and the reverse-video bar takes up the whole width of the terminal, even if it is resized. It uses the COLUMNS variable to achieve this.)
Line 2 shows the host I am connected to (obscured for security).
Line 3 shows the job number and current working directory.
Line 4 shows the user name and the prompt itself.
I have just one problem: unless I symlink /bin/ksh93 to /bin/sh (the default shell on NetBSD) I get errors about "bad substitution". I am certain my prompt is causing this problem, but I still don't know enough to say what is wrong. Would somebody be so kind as to look at my PS1 and tell me where I am going wrong, and where I can improve it? I have learned quite a bit about if...then and case statements while learning how to do this prompt, but I am still unclear about brackets, single quotes and double quotes.
The following is the relevant part of my .kshrc file. I have split the PS1 lines for readability but they are all on one line in the file.
I want to be able to run a script on one server, that will spawn another shell which runs some commands on another server..
I have seen some code that may help - but I cant get it working as below:
spawn /usr/bin/ksh
send "telnet x <port_no>\r"
expect "Enter command: "
send "LOGIN:x:x;... (2 Replies)
well i have this code here..and it works fine in kornshell..
#!/bin/ksh
home=c:/..../
input=$1
sed '1,3d' $input > $1.out
line=""
cat $1.out | while read a
do
line="$line $a"
done
echo $line > $1
rm $1.out
however...now i want it just in normal sh mode..how to convert this?... (21 Replies)
My client`s system is an AIX 4.2 and using the Kron shell. I was just wondering if it is possible to have the prompt autocompletion enabled on it without changing shell version.
By autocompletion, I mean to automatically complete the filenames or directories we type in using the Tab key. (2 Replies)
Hi All
I have writing a Korn Shell script to execute it on many of our servers. But some servers don't have Korn Shell installed, they use Borne Shell.
Some operations like calculation don't work :
cat ${file1} | tail -$((${num1}-${num2})) > ${file2}
Is it possible to activate Korn Shell... (3 Replies)
Hello,
I want to connect to Database through shell command line.
Here is my command from putty,
$ sqlplus -S ora/ora@ORA
But I am not able to connact to database.
If this command succed, what is the expected output on shell prompt?
Could you please let me know how to connact to... (3 Replies)
Can anybody help me with this small script , the script works fine and launches the IE from
c:\documents and settings \test\my documents>ksh prompt
$RunURL1.sh
this scitpt works and launches the ie from ksh , but when i schedule it to run the script then i get the error box saying command:1... (2 Replies)
Could some one tell me the difference btw Bourne shell and the Kshell? Which is more flexible and reliable in terms of portability and efficiency. When i type the following command ..
$ echo $SHELL
yields me
/bin/sh
Does this tells me that I am in Bourne shell. If yes, how can i get... (6 Replies)
I'm attempting to set up a two-line prompt using Korn.
This is what I've set up in .kshrc
PS1='$(print -n "`logname`@`hostname`:";if ] then; print -n "~${PWD#$HOME}"; else; print -n "$PWD";fi;print "\n$ ")'
And in .profile,
ENV="$HOME/.kshrc"; export ENV
The hosts that in use are... (10 Replies)
Discussion started by: capnpepper
10 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
06-14-2014
