01-21-2009
I already see these results in my sudo log file.
i was looking for a way to captures every thing any user who sudo as root does after becoming root
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
how do i go about adding a file to sudo so a user name oracle can run the file???
for some reason my man pages dont have anything for sudo.
files sudoers exist in /etc
can anyone help this is urgent
thank you (1 Reply)
Discussion started by: TRUEST
1 Replies
2. UNIX for Advanced & Expert Users
Hi, I was wondering if someone can give me some pointers about configuring SUDO. I am trying to configure SUDO to have about 30 users run about 200 scripts as a different user. I understand that I can create an User_Alias but how do I give that User_Alias rights to run all the scripts in a certain... (5 Replies)
Discussion started by: sajjad02
5 Replies
3. UNIX for Dummies Questions & Answers
Folks;
I have a sudo question:
- I have a real user named "greg" and another generic user named "devuser" & application that must be run like start/stop as "devuser" user.
Is there a way to:
Have user Greg login into the Solaris 10 box as himself then sudo as "devuser" to be able to... (10 Replies)
Discussion started by: Katkota
10 Replies
4. Linux
Hello, I would like to know what should I put on the sudoers file to block a determined group os using just one specific command as root?
He can do anything, but not execute program X, how can I do this?
Thank you very much. (2 Replies)
Discussion started by: Zarnick
2 Replies
5. Cybersecurity
Hi,
Is it possible to stop users from copying a login shell, say bash, to another name and then executing it via sudo to gain root priviliges?
Normal users have read access to login shells, so they can copy them without any limitations. How can I stop this?
Thanks (12 Replies)
Discussion started by: melias
12 Replies
6. Ubuntu
Hello all,
Anyone fimilar with su -l command?
So when I do su -l <user> any user it doesn't prompt me for password for that user. How I enable sudo to prompt for password whenever su -l command is used.
Please help!
thanks,
-Lalit
:D (7 Replies)
Discussion started by: email-lalit
7 Replies
7. UNIX for Dummies Questions & Answers
Hello all,
I have a script (script.sh) that is owned and executed by root. Now I need to give another user (user1) sudo access to execute that script.
I edited the /etc/sudoers file, and created the following:
# Runas alias specification
Runas_Alias RO = root
user1 ALL=(RO)... (1 Reply)
Discussion started by: designbc
1 Replies
8. UNIX for Advanced & Expert Users
Hi All
I want to grant elevated privs to a user that will be running a script as a background task. It will be launched from an ssh session via an embedded command in its key that just allows that account to run that script.
I'm reading up on sudo and notice that -
user ALL=(ALL) ALL
... (2 Replies)
Discussion started by: steadyonabix
2 Replies
9. AIX
I am running AIX 6.6.5.115 and am experiencing a problem using sudo. I have shell scripts that I created for our HR user and shell scripts that I created for root administrators. I do have a need to embed a sudo command in the user shell script to run one command as root. However the two... (8 Replies)
Discussion started by: RonDeF
8 Replies
LEARN ABOUT DEBIAN
rancid-run
rancid-run(1) General Commands Manual rancid-run(1)
NAME
rancid-run - run rancid for each of the groups
SYNOPSIS
rancid-run [-V] [-f rancid.conf] [-f rancid.conf] [-m mail_rcpt] [-r device_name] [group [group ...]]
DESCRIPTION
rancid-run is a sh(1) script to run rancid(1) for a set of rancid group(s).
rancid-run reads rancid.conf(5) to configure itself, then uses control_rancid(1) to run rancid(1) for each rancid group. The set of rancid
groups can either be provided as command-line arguments or via the LIST_OF_GROUPS variable in rancid.conf(5), if the group argument is
omitted.
A lock file is maintained per-group to prevent simultaneous runs for a given group by rancid-run(1). The lock file will be named
.<group>.run.lock and will be located in /var/lib/rancid.
A log file is produced under $LOGDIR/logs for each rancid group processed. The file name will be <group>.YYYYMMDD.HHMMSS (year month day .
hour minute second).
rancid-run is normally used to run rancid from cron(8). For example:
0 * * * * /usr/local/rancid/bin/rancid-run
The command-line options are as follows:
-V Prints package name and version strings.
-f rancid.conf
Specify an alternate configuration file.
-m mail_rcpt
Specify the recipient of diff mail, which is normally rancid-<group>. The argument may be a single address, multiple comma
separated addresses, or -m may be specified multiple times.
-r device_name
Run rancid for a single device, device_name. device_name should be name, as it appears in a group's router.db. The device must be
marked "up". If a group is not specified on the command-line, rancid will be run against any group in which the device_name
appears.
The -r option alters the subject line of the diff mail. It will begin with <group name>/<device name> rather than just the group
name alone.
ENVIRONMENT
rancid-run utilizes the following environment variables from rancid.conf(5).
BASEDIR
Location of group directories, etc. This is set to the "localstatedir" by the configure script at installation time.
LIST_OF_GROUPS
List of rancid groups to collect.
PATH Search path for utilities.
TMPDIR Directory to hold temporary files.
ERRORS
If rancid fails to run or collect a device's configuration, the particular group's log file (mentioned above) should be consulted. Any
errors produced by the revision control system (CVS or Subversion) or any of the rancid scripts should be included there, whether they be a
botched cvs tree, login authentication failure, rancid configuration error, etc. If the log file produces no clues, the next debugging
step should be run the commands manually. For example, can the user who runs rancid login to the device with 'clogin hostname', and so on.
FILES
$BASEDIR/etc/rancid.conf
rancid-run configuration file.
SEE ALSO
control_rancid(1), rancid.conf(5), router.db(5)
5 October 2006 rancid-run(1)