im looking to write a script to end user sessions which are on a paticular program and have been for over an hour so I can free up the system a bit.
I understand that the "who" command lists the current users logged into the system, however it does not let me see what program they are on and how long they have been on it.
If i do a
ps -ef | grep <username>
then this does provide me with the information I need, question is how do I get it to grep not just one username but every user that is logged into the system currently.
from the who command get the user logged in and save in file and from ps -ef get the processes running for more than hours and use grep -f saved_file for the processes of user currently logged in.
Cheers RudiC
My ps doesnt like those formats so Ive decided to go along with this which gives me what I require thing is now I don't know how I can kill the user off using the PID without any intervention.
ps -aef | grep Aug | grep me1010
The PID for the user is in the third column along
---------- Post updated at 09:00 AM ---------- Previous update was at 08:59 AM ----------
This is the output of the command Ive just mentioned, PID is in the third column
As root you can issue kill PID which will send the default TERM (#15) to that process. If that doesn't work, issue kill -9 PID which cannot be blocked by the receiving process. It may be neccessary to inform users beforehand, e.g. using write user .
Does your ps not allow for any formatting/column selection?
@02JayJay02
Please post what Operating System and version you have and what Shell you are running.
There is much variation in the ps command.
Please post what version of Progress you are running.
Do not, I repeat do not ever issue "kill -9" to a Progress database session which is connected to the current Progess instance. It will corrupt your database. Obviously no problem if the database has been restarted in the meantime and these are orphan clients which the database engine could not clean up for some reason (like they were stuck on I/O to a failed disc drive).
Please note that there is a proper procedure for removing Progess client sessions through the Progress promon utility.
If these are telnet clients, issuing kill -15 to the telnet process will trigger a hangup and cause the database engine to clean up the dead session. This is a safe approach because it triggers Before Image rollback of any active transactions .
Please note that there is a proper sequence of kill signals which will be documented for your version of Progress.
SunOS 5.10
Progress Version 9.1E
Im using the bash shell
Thankyou for the info I have been told never to issue a Kill -9 command as it is very dangerous to do, I am aware of the Progress commands however I am not familiar with them, you wouldn't happen to have any documentation on progress commands?
