06-16-2005
I didn't think it would...
I justed wanted to be certain. Is there a way to limit the number of concurrent sessions for a user?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I have customers on our AIX/UNIX node startup a process that becomes stranded or orphaned and must be killed. I would like to create a script to check for these orphan processes and kill them. I can have cron run this job. The customers process will run and after 24 hours time out leaving an... (4 Replies)
Discussion started by: rjohnson
4 Replies
2. Shell Programming and Scripting
I need a script that will look for idle users and kill there proc. (7 Replies)
Discussion started by: jdel80
7 Replies
3. AIX
Hello list,
Have a problem that's highlighting gaps in my knowledge; can you assist?
We have a script that's tacked onto our trading application which allows branch managers etc. to kill off the sessions of other users at their branch. A menu option in the application spawns a shell running... (8 Replies)
Discussion started by: alexop
8 Replies
4. HP-UX
Hi,
In my network we uses the NetTerm program to connect us to HP-UX 10.x server from windows workstations, but in some cases the user doesn't logout and close it by window's x button. The problem is that in HP-UX the user and all his tasks remain active and when he enter again HP-UX creates a... (12 Replies)
Discussion started by: efrenba
12 Replies
5. Shell Programming and Scripting
I need a script to kill those process id whose idle time is more than 30min
plz help me (3 Replies)
Discussion started by: salil2012
3 Replies
6. AIX
Dear Friends ,
I am using DB2 database in AIX 5.3 server . In my server some IDLE process are generated after several times which I need to kill it manually each and every time .
The process I query like following :
root@bagpuss $ ps auxw|sort -r +3|head -10
USER PID %CPU %MEM ... (3 Replies)
Discussion started by: shipon_97
3 Replies
7. Shell Programming and Scripting
Hi All,I have a problem with my kill idle script.my script is supposed to kill the user sessions which are idle for more than 2 hours.But is is killing the sessions which are idle for less than 2 hrs also.I dont know the exact time after which the script is killing,but it is less than 2 hours i am... (3 Replies)
Discussion started by: prabhu_kumar
3 Replies
8. Solaris
Hi,
i need to kill the idle dt sessions through script, can anyone tell me how to do?
RJS (2 Replies)
Discussion started by: rajasekg
2 Replies
9. Shell Programming and Scripting
Hello..
I have many sleepy users on my Solaris box and need to kill them if they are idle for more than 45 minutes for example...I know who -u gives and the idle time but unable to make a awk line to get the condition perfect. Please help...:wall: (9 Replies)
Discussion started by: wimaxpole
9 Replies
10. Shell Programming and Scripting
Hi,
I need a script that can automatically kill all processes named "webrepn" and "webrebw" if idle for more than 30 minutes.
Then I will have a Cron Job to run the script every night or 2-3 times a day depends on how this script helps.
Right now, I run "ps -ef | grep webrebn" and "kill -9... (7 Replies)
Discussion started by: MaggieL
7 Replies
LEARN ABOUT PHP
systemd-logind
SYSTEMD-LOGIND.SERVICE(8) systemd-logind.service SYSTEMD-LOGIND.SERVICE(8)
NAME
systemd-logind.service, systemd-logind - Login manager
SYNOPSIS
systemd-logind.service
/lib/systemd/systemd-logind
DESCRIPTION
systemd-logind is a system service that manages user logins. It is responsible for:
o Keeping track of users and sessions, their processes and their idle state. This is implemented by allocating a systemd slice unit for
each user below user.slice, and a scope unit below it for each concurrent session of a user. Also, a per-user service manager is
started as system service instance of user@.service for each logged in user.
o Generating and managing session IDs. If auditing is available and an audit session ID is already set for a session, then this ID is
reused as the session ID. Otherwise, an independent session counter is used.
o Providing PolicyKit-based access for users for operations such as system shutdown or sleep
o Implementing a shutdown/sleep inhibition logic for applications
o Handling of power/sleep hardware keys
o Multi-seat management
o Session switch management
o Device access management for users
o Automatic spawning of text logins (gettys) on virtual console activation and user runtime directory management
User sessions are registered with logind via the pam_systemd(8) PAM module.
See logind.conf(5) for information about the configuration of this service.
See sd-login(3) for information about the basic concepts of logind such as users, sessions and seats.
See the logind D-Bus API Documentation[1] for information about the APIs systemd-logind provides.
For more information on the inhibition logic see the Inhibitor Lock Developer Documentation[2].
SEE ALSO
systemd(1), systemd-user-sessions.service(8), loginctl(1), logind.conf(5), pam_systemd(8) sd-login(3)
NOTES
1. logind D-Bus API Documentation
https://www.freedesktop.org/wiki/Software/systemd/logind
2. Inhibitor Lock Developer Documentation
https://www.freedesktop.org/wiki/Software/systemd/inhibit
systemd 237 SYSTEMD-LOGIND.SERVICE(8)