Recently I was on an operational call and heard the people running my code placing the code in the /tmp directory and running as root. I had not planned on that. So I want to add some checks to my code (using ksh93):
What I can't find is a means to check the case where my code was run with sudo or "su -". The above 'whomai' returns the users name, not the fact it was run with root access through sudo. There are many reasons to use sudo, but in this case I want my app to run as a normal user with normal permissions, no extra help.
Is this possible? any ideas? I've done some google searching and all the references I can find are on how to use sudo, not how to identify it is being used.
We have HP 9000 running UX.
Does anybody know a reputable or even a strong maintenance firm that DOESN'T have a help desk the other side of the planet?
We've been approached by Newcorp but thay seem rubbish.
Please give me some recommendations.
Sorry if this is posted in the wrong room but I... (3 Replies)
When I ran the following find command under a "regular" user is completes but it limited because of perms.
find / -name "*.*" | xargs grep something > ok
But when I try to run it under su, it hangs and never completes.
Any suggestion? (4 Replies)
Hi Guys,
Is there any one can help me with the below error message dispalys on the LED panel.
10112633 u0.1-p1-v2
I bought a second hand IBM 7029 6C3 online several days ago. On the fist day, it can be ran well. but on second day, when i tried to boot up the machine, after few mins, the... (2 Replies)
Hi, I have written a script and placed in an application and the script can be executed manually only. But somehow one of the method in the script is being called and bringing the application down. But we are not able to find any instance of script running.
Is there a way to findout whether the... (1 Reply)
I am writing a BASH script to update a webserver and then restart Apache. It looks basically like this:
#!/bin/bash
rsync /path/on/local/machine/ foo.com:path/on/remote/machine/
ssh foo.com sudo /etc/init.d/apache2 reloadrsync and ssh don't prompt for a password, because I have DSA encryption... (9 Replies)
I want to test if script.sh is being run with nohup ... but $0 does not contain nohup part...
purpose: script.sh should only be ran with nohup if user forgets nohup then it should echo "run with nohup" && exit....... (2 Replies)
Hi,
I am running below code
For I in $var
do
.......some line of code.......
nohup Sqlplus apps/apps <<EOF &
My_proc($I)
Exit
EOF
done
Nohup and & is used for parallel processing.
Can someone help in determining if the procedure with different arguments
Was called paralley or... (3 Replies)
Hi,
Can we able to identify how many times any script was ran per day/week/month/year wise (2 Replies)
Discussion started by: penqueen
2 Replies
LEARN ABOUT OPENSOLARIS
gksu
GKSU(1) General Commands Manual GKSU(1)NAME
gksu - a Gtk+ su frontend
SYNOPSIS
gksu [ options ] <command>
gksudo [ options ] <command>
DESCRIPTION
This manual page documents briefly gksu and gksudo
gksu is a frontend to su and gksudo is a frontend to sudo. Their primary purpose is to run graphical commands that need root without the
need to run an X terminal emulator and using su directly.
OPTIONS
These programs follow the usual GNU command line syntax, with long options starting with two dashes (`-'). A summary of options is
included below.
Common Options:
--user <user>, -u <user>
Calls <command> as the specified user
--message <message>, -m <message>
Replaces the standard message shown to ask for password for the argument passed to the option
--sudo-mode, -S
Use sudo instead of su as backend authentication system. Notice that the X authorization magic will not work when using sudo for
target users other than root.
--title <title>, -t <title>
Replaces the default title with the argument
--icon <icon>, -i <icon>
Replaces the default window icon with the argument
--print-pass, -p
Asks gksu to print the password to stdout, just like ssh-askpass. Useful to use in scripts with programs that accept receiving the
password on stdin.
--disable-grab, -g
Disables the "locking" of the keyboard, mouse, and focus done by the program when asking for password
--ssh-fwd, -s
Strip the host part of the $DISPLAY variable, so that GKSu will work on SSH X11 Forwarding.
--login, -l
Makes this a login shell. Beware this may cause problems with the Xauthority magic. Run xhost to allow the target user to open win-
dows on your display! This is ignored if running with sudo as backend for authentication.
--preserve-env, -k
Preserve the current environments, does not set $HOME nor $PATH, for example.
FILES
/etc/gksu.conf
Configuration file to setup system-wide defaults for gksu/gksudo. It provides an option to force the display grabing, also.
RETURN VALUE
On success, gksu will return 0. If an authentication error ocurred, it will exit with error code 3. If the user canceled the dialog or
closed the window, it will return error code 2. On other error conditions, gksu will return 1.
NOTE
Note that <command> and all its arguments should be passed as one single argument to gksu just like one would to when using su.
SEE ALSO su(1), gksuexec(1).
AUTHOR
This manual page was written by Gustavo Noronha Silva <kov@debian.org> for the Debian GNU/Linux system (but may be used by others).
2003 GKSU(1)