06-14-2006
hi everyone
i try to do something like this
i go to the admin account (root) and did
id
giving me
uid=0(root) gid=1(other)
now in the first script cs-customers i did something like this
echo"starting to search for customers files"
login:root
password:
#id
uid=0(root) gid=1(other)
ksh cs-search
#disconnect from the admin account
if test -s b.log
........
fi
question 1 .is it true to write like this
2. my goal is not to touch any of the .login or /etc/host file
i just want to connect to root because if the script and then disconnect from it . i want to connect to root without passwd only when i running the cs-customers . is it correct what i wrote???
thanks all for quick response
8 More Discussions You Might Find Interesting
1. Cybersecurity
Hi All,
If I want to have two user accounts from the same grop in UNIX Solaries. However, I want one of them to be used only for FTP while the other for TELNET. Can anybody tell me how to do that?
Best Regards (13 Replies)
Discussion started by: omran
13 Replies
2. Solaris
I have a sunfire V240 but nobody seems to know the root password. I can get into ALOM but not console mode. Is there a hack or something that cn get me back into this system lo reload it? (5 Replies)
Discussion started by: dewsdwarfs
5 Replies
3. Shell Programming and Scripting
Hi all,
I encountered a problem where my script stops running the remaining checks after becoming an admin that is written within the script.
For example:
=========================================
#!/bin/sh
check 1 # Runs successfully
check 2 # Runs successfully
/com/bin/admin #... (1 Reply)
Discussion started by: seanchew
1 Replies
4. AIX
Hi Friends,
I am trying to write a script for finding all the users with the GID 0 i.e. Admin users. can you please help me on this. (1 Reply)
Discussion started by: anoopraok
1 Replies
5. What is on Your Mind?
I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
Discussion started by: bobwilson
3 Replies
6. Shell Programming and Scripting
Can anyone create or give me a script that I can use to email a user automatically when I kill one of their processes?
Or
Can you give me a script to allow me to email a user (entering email manually) when a process is killed? Like showing what the PID was and a reason the admin killed it? Is... (2 Replies)
Discussion started by: JoeGazz84
2 Replies
7. What is on Your Mind?
I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that.
Can we get "DAY" shifts in any one of the admin Job ?
Can't we have shift timings in any company ?
Eventhough the... (7 Replies)
Discussion started by: Jacktts
7 Replies
8. Solaris
I have a good friend leaving my place of employment. He's an old greybeard. His first job was sorting punch cards. I'm serious.
I'm looking for suggestions on a short shell script to write in his card to say good bye.
Please be creative and obfusticating!
have fun with it.
... (4 Replies)
Discussion started by: os2mac
4 Replies
SETUID(1) General Commands Manual SETUID(1)
NAME
setuid - run a command with a different uid.
SYNOPSIS
setuid username|uid command [ args ]
DESCRIPTION
Setuid changes user id, then executes the specified command. Unlike some versions of su(1), this program doesn't ever ask for a password
when executed with effective uid=root. This program doesn't change the environment; it only changes the uid and then uses execvp() to find
the command in the path, and execute it. (If the command is a script, execvp() passes the command name to /bin/sh for processing.)
For example,
setuid some_user $SHELL
can be used to start a shell running as another user.
Setuid is useful inside scripts that are being run by a setuid-root user -- such as a script invoked with super, so that the script can
execute some commands using the uid of the original user, instead of root. This allows unsafe commands (such as editors and pagers) to be
used in a non-root mode inside a super script. For example, an operator with permission to modify a certain protected_file could use a
super command that simply does:
cp protected_file temp_file
setuid $ORIG_USER ${EDITOR:-/bin/vi} temp_file
cp temp_file protected_file
(Note: don't use this example directly. If the temp_file can somehow be replaced by another user, as might be the case if it's kept in a
temporary directory, there will be a race condition in the time between editing the temporary file and copying it back to the protected
file.)
AUTHOR
Will Deich
local SETUID(1)