05-20-2008
su (switching to other user)
Hi,
what is the use of the double quotes and !! in the following code segment:
su - user1 << ""!! > /dev/null 2>&1
echo "welcome user1"
EOF
!!
also what is the difference between below:
su - user1 << ""!! > /dev/null 2>&1 and
su - $USER << ""!!!> /dev/null 2>&1.
Note: $USER = user2
Jagadeesh.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello everyone,
I need to make a OS full backup. I am using the vdump command but first, I must to switch to the single-user mode.
I am working on a Compaq Tru64 Unix V4.0G.
Please, could somebody tell me which is/are the commands to do it?
I appreciate your help
Gastón (1 Reply)
Discussion started by: gmoyano
1 Replies
2. Shell Programming and Scripting
I am writing a script that has some tasks that must be run as root, then set of tasks to be run as normal user, then again as root.
is there a way to switch between users in a script?
any other alternatives?
thx (3 Replies)
Discussion started by: melanie_pfefer
3 Replies
3. UNIX for Dummies Questions & Answers
Running the following shell script,
#!/usr/bin/ksh
set -x
swdofile=/opt/SWDO_IN1V01P001_1.csv
USER='myusername'
PASSWD='mypassword'
HOST='myhostname'
ftp -n $HOST << SCRIPT
quote USER $USER
quote PASS $PASSWD
su - BRA -c put $swdofile
quit
SCRIPT
exit 0
but not managing to get the... (1 Reply)
Discussion started by: daveaasmith
1 Replies
4. Shell Programming and Scripting
Good day Guys!!!
I am currently making a script in AIX, the script runs a SAS job, the owner of the script is the root, but the SAS jobs cannot be run by the root, as it should be run by a user 'sasia'. But inside the script, root creates a logfile, so what I need is just to su to sasia for the... (3 Replies)
Discussion started by: sasia
3 Replies
5. Shell Programming and Scripting
Hi,
I have a shell script in which I need to switch to another user and execute some commands and then come back to the original user.
To make it more clear -
I have to log in as user root then 'su' to jag - execute a script called backup.sh and then logout and come back to root again..
... (1 Reply)
Discussion started by: bjagadeesh
1 Replies
6. Shell Programming and Scripting
Hi,
what is the use of the double quotes and !! in the following code segment:
su - user1 << ""!! > /dev/null 2>&1
echo "welcome user1"
EOF
!!
also what is the difference between below:
su - user1 << ""!! > /dev/null 2>&1 and
su - $USER << ""!!!> /dev/null 2>&1.
Note: $USER =... (2 Replies)
Discussion started by: bjagadeesh
2 Replies
7. UNIX for Advanced & Expert Users
I need to do a switch user in an automated mode and do a ftp using that switched id.
Scenario:
initial login xx.
switch to user-yy without manually entering the password.
ftp some files from user yy to another user zz - automated mode.
Can any unix experts can help me for my above query? (1 Reply)
Discussion started by: mjdarm
1 Replies
8. UNIX for Dummies Questions & Answers
I need to do a switch user in an automated mode and do a ftp using that switched id.
Scenario:
initial login xx.
switch to user-yy without manually entering the password.
ftp some files from user yy to another user zz - automated mode.
Can any unix experts can help me for my above query? (9 Replies)
Discussion started by: mjdarm
9 Replies
9. UNIX for Dummies Questions & Answers
Whenever i switch from root to another user, by doing su - user, it takes me to home directory of user. This is very annoying as i want to be in same dir to run different commands as root sometimes and sometimes as normal user.
How to fix this? (1 Reply)
Discussion started by: syncmaster
1 Replies
10. Shell Programming and Scripting
Hi all, I have a script that I will need to run occasionally to stop my db2 instance-
stopDB2.sh
su -l -c "db2 force application all"
su -l -c "db2 terminate"
su -l -c "db2 stop"
su -l -c "db2licd -end"
This works when I su to the instance owner (archive), and run each line. I need to... (5 Replies)
Discussion started by: jeffs42885
5 Replies
talk(1) General Commands Manual talk(1)
Name
talk, otalk - talk to another user
Syntax
talk person [ttyname]
otalk person [ttyname]
Description
The command is a visual communication program which copies lines from your terminal to that of another user.
If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on another
host, then person is of the form :
host!user
or
host.user
or
host:user
or
user@host
The form user@host is perhaps preferred.
If you want to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal name.
When first called, it sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to the user you wish to talk to. At this point, the recipient of the message should reply by typing
talk your_name@your_machine
It doesn't matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the
two parties may type simultaneously, with their output appearing in separate windows. Typing Ctrl-L will cause the screen to be reprinted,
while your erase, kill, and word kill characters will work in talk as normal. To exit, just type your interrupt character; then moves the
cursor to the bottom of the screen and restores the terminal.
Permission to talk may be denied or granted by use of the mesg command. At the outset talking is allowed. Certain commands, in particular
and disallow messages in order to prevent messy output.
In order to use the program with machines on your network that may be running earlier versions of ULTRIX, you must initiate a session with
the command (/usr/ucb/otalk) instead of the command You must also respond to a request from a machine running an older version of the pro-
gram with the command. See the Restrictions section.
Examples
The following example demonstrates how to use the command. In this case, user1, whose system (system1) is running ULTRIX V2.2 initiates a
session with user2, whose system (system2) is running ULTRIX V3.0. User1 types the following:
system1> talk user2@system2
The following message appears on the screen of user2:
Message from Talk_Daemon@system2 at 12:37 ...
talk: connection requested by user1@system1.
talk: respond with: otalk user1@system1
To establish the connection user2 follows the instructions from the Talk_Daemon and types the following at the system prompt:
system2> otalk user1@system1
Restrictions
The version of released with ULTRIX V3.0 uses a protocol that is incompatible with the protocol used in earlier versions. Starting with
ULTRIX V3.0, the program communicates with other machines running ULTRIX, V3.0 (and later), and machines running 4.3 BSD or versions of
UNIX based on 4.3 BSD.
The command is not 8-bit clean. Typing in DEC Multinational Characters (DECMCS) causes the characters to echo as a sequence of a carets (^)
followed by the character represented with its high bit cleared. This limitation makes unusable if you want to communicate using a language
which has DECMCS characters in its alphabet.
Files
to find the recipient's machine
to find the recipient's tty
See Also
mail(1), mesg(1), who(1), write(1), talkd(8c)
talk(1)