04-03-2019
Well, I am the one with the root privileges. However the app - WebSphere MQ - is running under its own nonpriviliged user account. When I log in remotely, I am also using my own nonprivileged user then use sudo to change privileges if needed.
The problem were visible to all nonprivileged user and even root user, running most commands,
ps -ef shows all processes for all users. Almost. ps aux is listing all processes for all users, even those not attached to a terminal.
Now I do not have the opportunity to repeat the situation, but my guess is that ps aux would be able to show all the entries I wanted for.
--Trifo
10 More Discussions You Might Find Interesting
1. Solaris
Hi ,
I need to count all processes contains the pattren "FND"
For Example:
I was reteriving the details of all processes related to "FND" by this command
$ ps -ef | grep FND
but now I just wanna count them .
Regards
Adel (2 Replies)
Discussion started by: ArabOracle.com
2 Replies
2. UNIX for Dummies Questions & Answers
I have written a function that fills an array and another function where if a parameter is supplied it will jump to that part of the array and cat it to the screen.
I need to put in some checks to make sure the parameter supplied is firstly a number and then not a number great than the length of... (2 Replies)
Discussion started by: magnia
2 Replies
3. Programming
I need a mechanism to fork child processes and all child processes should connect to a server.but the number of child processes should be limited(for ex:50)
Here's my pseudo, but I cant figure out how to limit the child process number. Should I use a semaphore? or what?
for(;;)... (3 Replies)
Discussion started by: xyzt
3 Replies
4. Shell Programming and Scripting
Hi all
Is there away to create a script with dynamic number of parameter..
like the kill command in UNIX
kill -9 xxx xxx
cheers (4 Replies)
Discussion started by: co0oly
4 Replies
5. Shell Programming and Scripting
Hi
Is there a way to count how many processes a script has started, count how many of these have finished, and make the script wait if their difference goes over a given threshold?
I am using a script to repeatedly execute a code (~100x) which converts 2 data files into one .plt which is in... (4 Replies)
Discussion started by: drbones
4 Replies
6. Shell Programming and Scripting
Hey I'm new in linux,
I'm looking for a code to check whether the parameter is a number or a string.
I have already tried this code:
eerste=$(echo $1 | grep "^*$">aux)
if
But it doesn't work.:confused:
Thanks (2 Replies)
Discussion started by: Eclecticaa
2 Replies
7. AIX
Hi,
Is there a maximum number of processes kernel parameter in AIX.
Solaris has max_nprocs,
HP-UX has nproc,
I can only find max user process (maxuproc) for AIX.
Thanks,
Wilson. (3 Replies)
Discussion started by: wilsonee
3 Replies
8. AIX
Morning,
Somebody can tell me in AIX 6.1 what is the different between the maxuproc (lsattr -El sys0 | grep max) and the for a user.
Example:
Oracle is limited by :
#ulimit -u
processes(per user) unlimited
But lsattr -El sys0| grep maxuproc show me :
maxuproc 16384
So... (1 Reply)
Discussion started by: bacup540
1 Replies
9. UNIX for Dummies Questions & Answers
// AIX 6.1 & Power 7 server
I have maxuproc set to 16384.
lsattr -El sys0 -a maxuproc
maxuproc 16384 Maximum number of PROCESSES allowed per user True
What is the maximum number of maxuproc we can go for?
If I increase maxuproc to the higher number, what would be ramifications?
I... (1 Reply)
Discussion started by: Daniel Gate
1 Replies
10. Red Hat
Hi Guys,
I am running RHEL6 and now my processes reach maximum limit.
How do I increase the maxuproc value?
Can I increase the value without rebooting the server?
Thanks in advance...
Please Help!!! (5 Replies)
Discussion started by: Phuti
5 Replies
LEARN ABOUT LINUX
sudo_root
sudo_root(8) System Manager's Manual sudo_root(8)
NAME
sudo_root - How to run administrative commands
SYNOPSIS
sudo command
sudo -i
INTRODUCTION
By default, the password for the user "root" (the system administrator) is locked. This means you cannot login as root or use su. Instead,
the installer will set up sudo to allow the user that is created during install to run all administrative commands.
This means that in the terminal you can use sudo for commands that require root privileges. All programs in the menu will use a graphical
sudo to prompt for a password. When sudo asks for a password, it needs your password, this means that a root password is not needed.
To run a command which requires root privileges in a terminal, simply prepend sudo in front of it. To get an interactive root shell, use
sudo -i.
ALLOWING OTHER USERS TO RUN SUDO
By default, only the user who installed the system is permitted to run sudo. To add more administrators, i. e. users who can run sudo, you
have to add these users to the group 'admin' by doing one of the following steps:
* In a shell, do
sudo adduser username admin
* Use the graphical "Users & Groups" program in the "System settings" menu to add the new user to the admin group.
BENEFITS OF USING SUDO
The benefits of leaving root disabled by default include the following:
* Users do not have to remember an extra password, which they are likely to forget.
* The installer is able to ask fewer questions.
* It avoids the "I can do anything" interactive login by default - you will be prompted for a password before major changes can happen,
which should make you think about the consequences of what you are doing.
* Sudo adds a log entry of the command(s) run (in /var/log/auth.log).
* Every attacker trying to brute-force their way into your box will know it has an account named root and will try that first. What they do
not know is what the usernames of your other users are.
* Allows easy transfer for admin rights, in a short term or long term period, by adding and removing users from the admin group, while not
compromising the root account.
* sudo can be set up with a much more fine-grained security policy.
* On systems with more than one administrator using sudo avoids sharing a password amongst them.
DOWNSIDES OF USING SUDO
Although for desktops the benefits of using sudo are great, there are possible issues which need to be noted:
* Redirecting the output of commands run with sudo can be confusing at first. For instance consider
sudo ls > /root/somefile
will not work since it is the shell that tries to write to that file. You can use
ls | sudo tee /root/somefile
to get the behaviour you want.
* In a lot of office environments the ONLY local user on a system is root. All other users are imported using NSS techniques such as
nss-ldap. To setup a workstation, or fix it, in the case of a network failure where nss-ldap is broken, root is required. This tends to
leave the system unusable. An extra local user, or an enabled root password is needed here.
GOING BACK TO A TRADITIONAL ROOT ACCOUNT
This is not recommended!
To enable the root account (i.e. set a password) use:
sudo passwd root
Afterwards, edit the sudo configuration with sudo visudo and comment out the line
%admin ALL=(ALL) ALL
to disable sudo access to members of the admin group.
SEE ALSO
sudo(8), https://wiki.ubuntu.com/RootSudo
February 8, 2006 sudo_root(8)