I have an RS6000 server running AIX and on occasion all users are logged out of the server "connection closed by foreign host" is the error message. Normally a user can press enter and get a Login prompt, but they get the message "connection refused" and then the users can wait a minute or so and... (2 Replies)
hello all
say im logged in to account ar root , but I can't change any thing there ( like username )
if someone is already logged in also . how can I know who is ( user name ) also connected to the user im using ? (2 Replies)
I have searched the forums but have not mangaed to quite find what im looking for. I have used to /etc/passwd command to present me a list of all users the who command to present all users currently logged on, but what i want to know is what command can i use to display users that are registered... (12 Replies)
How do I find this out? I have a feeling its a simple command such as who, but I just don't know what it is. I've had a search on here but either I can't put it into the right search criteria or there isn't a topic on it.
Thanks.
EDIT: Delete this thread, as I posted it I noticed the... (0 Replies)
My admin needs a shell script in Korn that will show conditions based on users logged in. I have never used the Korn shell and have no clue what I am doing, can anyone help.
here are the conditions that need to be returned.
if users are below 5
displays should be: performance is high
if... (1 Reply)
how to find out total number of users logged in a server from uptime . i mean to say i need the total output of unix command . who gives the out put at a particular time . I need at all time from which machine who has connected , (3 Replies)
In a professional environment with traditional application you often want (or are asked) to report the users.
Traditionally there is the who command
who | awk '{print $1}'telnetd or sshd register the users in the utmp file, to be shown with who, w, users, finger, pinky, ...
In addition they... (1 Reply)
Discussion started by: MadeInGermany
1 Replies
LEARN ABOUT OPENDARWIN
renice
RENICE(8) BSD System Manager's Manual RENICE(8)NAME
renice -- alter priority of running processes
SYNOPSIS
renice [priority | [-n increment]] [[-p] pid ...] [[-g] pgrp ...] [[-u] user ...]
DESCRIPTION
The renice utility alters the scheduling priority of one or more running processes. The following who parameters are interpreted as process
ID's, process group ID's, user ID's or user names. The renice'ing of a process group causes all processes in the process group to have their
scheduling priority altered. The renice'ing of a user causes all processes owned by the user to have their scheduling priority altered. By
default, the processes to be affected are specified by their process ID's.
The following options are available:
-g Force who parameters to be interpreted as process group ID's.
-n Instead of changing the specified processes to the given priority, interpret the following argument as an increment to be applied to
the current priority of each process.
-u Force the who parameters to be interpreted as user names or user ID's.
-p Reset the who interpretation to be (the default) process ID's.
For example,
renice +1 987 -u daemon root -p 32
would change the priority of process ID's 987 and 32, and all processes owned by users daemon and root.
Users other than the super-user may only alter the priority of processes they own, and can only monotonically increase their ``nice value''
within the range 0 to PRIO_MAX (20). (This prevents overriding administrative fiats.) The super-user may alter the priority of any process
and set the priority to any value in the range PRIO_MIN (-20) to PRIO_MAX. Useful priorities are: 20 (the affected processes will run only
when nothing else in the system wants to), 0 (the ``base'' scheduling priority), anything negative (to make things go very fast).
FILES
/etc/passwd to map user names to user ID's
SEE ALSO nice(1), rtprio(1), getpriority(2), setpriority(2)STANDARDS
The renice utility conforms to IEEE Std 1003.1-2001 (``POSIX.1'').
HISTORY
The renice utility appeared in 4.0BSD.
BUGS
Non super-users cannot increase scheduling priorities of their own processes, even if they were the ones that decreased the priorities in the
first place.
BSD June 9, 1993 BSD