Any way to know beforehand if SUDO is (going to be) needed?
I'm using virtual file-system in /proc/ to print out 1)current working directory (CWD): ls /proc/$PID/cwd
2)command line*: cat /proc/$PID/cmdline
and 3)# of open files: ls /proc/$PID/fdinfo | wc -l
All above snippets are part of printfs.
Now, some processes complain about SUDO privileges (e.g. init: ls: cannot access /proc/1/cwd: Permission denied).
Is it possible to know beforehand if action/command will require SUDO? For example, is there a "maximum PID number", above which no process needs SUDO?
Following snippet checks if user ran the script as SUDO, but I'd need to know beforehand if there will be an "error": if [ $UID -eq 0 ] ; then
BTW: In following printf snippet with 2 arguments, printf "%15s %s\n" CWD: "$((ls /proc/$PID/cwd) | tr '\n' ' ')"if ls returns error cannot open directory /proc/1/fd: Permission denied it outputs this error before"CWD:", like so:
Why this happens?
*tldp.org says that
Quote:
cmdline file holds the command-line arguments the process was invoked with
so I'm not sure if "command-line arguments" is what was meant by "command line".
Last edited by courteous; 12-11-2010 at 12:01 PM..
Scenario: I have two servers, A and B. Server A is using autosys to connect to server B via ssh in order to run scripts. The scripts to be run on server B must be run by user "weblogic".
So what I did was make the autosys user connect with a ssh key from server A to server B. After that I... (3 Replies)
Hi! I'm very new to unix, so please keep that in mind with the level of language used if you choose to help :D Thanks!
When attempting to use sudo on and AIX machine with oslevel 5.1.0.0, I get the following error:
exec(): 0509-036 Cannot load program sudo because of the following errors:... (1 Reply)
we are looking at changing the way we get root on our network.
in our current system if an admin needs root access he just gets the root password and uses an su.
some of our staff have decided that a sudo to "/bin/sh" will be easer.
some of our staff think a sudo to "su -" will be better.
I... (0 Replies)
Sudo In AIX, how to find out what commands have been run after a user sudo to another user? for example, user sam run 'sudo -u robert ksh' then run some commands, how can I (as root) find what commands have been run?
sudo.log only contains sudo event, no activity logging. (3 Replies)
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)
Hi All,
I running a unix command using sudo option inside shell script. Its working well. But in crontab the same command is not working and its throwing
"sudo: sorry, you must have a tty to run sudo". I do not have root permission to add or change settings for my userid. I can not even ask... (9 Replies)
Hi, Have a need to run the below command as a "karuser" from a java class which will is running as "root" user. When we are trying to run the below command from java code getting the below error.
Command:
sudo -u karuser -s /bin/bash /bank/karunix/bin/build_cycles.sh
Error:
sudo: sorry,... (8 Replies)
I want to give root access to a user called denielr on server - tsprd01, but do not want to share root password. I have sudoers configured already.
He should have all access equal to root. I made this entry in /etc/sudoers, but it is not working
denielr tsprd01 =(root) NOPASSWD: ALL
I tried to... (2 Replies)
Hello,
I have a wrapper script that I am trying to build/execute, which has two different sub scripts, which run as two separate users.
Purpose is to mask the contents of the script and allow the user to execute utlrp.sql, which requires sys level privs to execute.
User FORD logs in, and... (5 Replies)
Discussion started by: willyb
5 Replies
LEARN ABOUT CENTOS
nsenter
NSENTER(1) User Commands NSENTER(1)NAME
nsenter - run program with namespaces of other processes
SYNOPSIS
nsenter [options] [program] [arguments]
DESCRIPTION
Enters the namespaces of one or more other processes and then executes the specified program. Enterable namespaces are:
mount namespace
mounting and unmounting filesystems will not affect rest of the system (CLONE_NEWNS flag), except for filesystems which are explic-
itly marked as shared (by mount --make-shared). See /proc/self/mountinfo for the shared flag.
UTS namespace
setting hostname, domainname will not affect rest of the system (CLONE_NEWUTS flag).
IPC namespace
process will have independent namespace for System V message queues, semaphore sets and shared memory segments (CLONE_NEWIPC flag).
network namespace
process will have independent IPv4 and IPv6 stacks, IP routing tables, firewall rules, the /proc/net and /sys/class/net directory
trees, sockets etc. (CLONE_NEWNET flag).
PID namespace
children will have a set of PID to process mappings separate from the nsenter process (CLONE_NEWPID flag). nsenter will fork by
default if changing the PID namespace, so that the new program and its children share the same PID namespace and are visible to each
other. If --no-fork is used, the new program will be exec'ed without forking.
See the clone(2) for exact semantics of the flags.
If program is not given, run ``${SHELL}'' (default: /bin/sh).
OPTIONS
Argument with square brakets, such as [file], means optional argument. Command line syntax to specify optional argument --mount=/path/to
/file. Please notice the equals sign.
-t, --target pid
Specify a target process to get contexts from. The paths to the contexts specified by pid are:
/proc/pid/ns/mnt the mount namespace
/proc/pid/ns/uts the UTS namespace
/proc/pid/ns/ipc the IPC namespace
/proc/pid/ns/net the network namespace
/proc/pid/ns/pid the PID namespace
/proc/pid/root the root directory
/proc/pid/cwd the working directory respectively
-m, --mount [file]
Enter the mount namespace. If no file is specified enter the mount namespace of the target process. If file is specified enter the
mount namespace specified by file.
-u, --uts [file]
Enter the UTS namespace. If no file is specified enter the UTS namespace of the target process. If file is specified enter the UTS
namespace specified by file.
-i, --ipc [file]
Enter the IPC namespace. If no file is specified enter the IPC namespace of the target process. If file is specified enter the IPC
namespace specified by file.
-n, --net [file]
Enter the network namespace. If no file is specified enter the network namespace of the target process. If file is specified enter
the network namespace specified by file.
-p, --pid [file]
Enter the PID namespace. If no file is specified enter the PID namespace of the target process. If file is specified enter the PID
namespace specified by file.
-r, --root [directory]
Set the root directory. If no directory is specified set the root directory to the root directory of the target process. If direc-
tory is specified set the root directory to the specified directory.
-w, --wd [directory]
Set the working directory. If no directory is specified set the working directory to the working directory of the target process.
If directory is specified set the working directory to the specified directory.
-F, --no-fork
Do not fork before exec'ing the specified program. By default when entering a pid namespace enter calls fork before calling exec so
that the children will be in the newly entered pid namespace.
-V, --version
Display version information and exit.
-h, --help
Print a help message.
SEE ALSO setns(2), clone(2)AUTHOR
Eric Biederman <ebiederm@xmission.com>
AVAILABILITY
The nsenter command is part of the util-linux package and is available from Linux Kernel Archive <ftp://ftp.kernel.org/pub/linux/utils
/util-linux/>.
util-linux January 2013 NSENTER(1)