Sponsored Content
Full Discussion: kill user session
Operating Systems Solaris kill user session Post 302130264 by reborg on Saturday 4th of August 2007 08:35:23 AM
Old 08-04-2007
Never use kill -9 on a process as a first resort.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

User login session

Having a problem on AIX 4.3.3 with the following error when more than 2 users try and sign onto the server. 3004-312 All available login sessions are in use. ???? (1 Reply)
Discussion started by: Docboyeee
1 Replies

2. HP-UX

tracing a user's session

hi, does anyone knows how to trace a user session on a unix system: i want to log these things 1- login 2- date of starting session 3- date of closing session i've tryed who and last but they don't give closing time of session regards hmaiida (2 Replies)
Discussion started by: hmaiida
2 Replies

3. UNIX for Dummies Questions & Answers

Deleting a user session

I logged on yesterday and ran something that made my ID hang. I X'd out of the session and then logged on again and my ID from the original session is still there. I checked again this morning and the ID is still there (I checked using the WHO command). How can I kill that first session using... (7 Replies)
Discussion started by: jbrubaker
7 Replies

4. AIX

user session restriction

I want to restrict user's loging according to number of session. example the user named "patrik" can be login concurrently from 12 stations thru telnet the 13th if some body tries to telnet 13th session it should not allow, until any of the 12 sessions are closed. is it possibel ...i think... (2 Replies)
Discussion started by: pchangba1
2 Replies

5. AIX

user session restriction

hi, I am facing a problem from the remote system if i login to my AIX5.3 machine as root (thru telnet) the session does not expire for 2 hours even if the session is kept ideal But whenever i do the same thing from some other user then the session is lost within 10 minutes (if session is kept... (2 Replies)
Discussion started by: pchangba
2 Replies

6. Solaris

Elegant Solutions to kill telnet/ssh session

We have a generic user account "user1" setup on Solaris 8 that is used by an application. I dont want users to telnet/ssh using this account. Instead if they want to gain access, they must su or sudo to this after logging in with their own ID. My earlier attempts to accomplish this by disabling... (7 Replies)
Discussion started by: boshyd
7 Replies

7. Shell Programming and Scripting

Function to kill the established rsh session

HI I know that it sounds crazy :eek: appreciated if any one provided me a solution for my below case , the below script is checking the Database availability on many servers by establishing rsh session ( one by one ) , sometime one of the servers goes down and while this the script taking... (0 Replies)
Discussion started by: bejo4ever
0 Replies

8. Solaris

Kill idle dt session

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

Write a scripts to kill idle user for 60 min. & email user list to admin in text file

Folks, I have written one script for following condition by referring some of online post in this forum. Please correct it if I'm missing something in it. (OS: AIX 5.3) List the idle user. (I used whoidle command to list first 15 user and get username, idle time, pid and login time).... (4 Replies)
Discussion started by: sumit30
4 Replies

10. Red Hat

Network User Session

dear colleagues, please help, i have a linux server (linux 5.3) running oracle 10g database for application. there are 98 users who are using that oracle application over LAN. but during the working hours the user session is increased (min 150 users) bcos one user is working on different client... (7 Replies)
Discussion started by: Abrar
7 Replies
PAM_SYSTEMD(8)							    pam_systemd 						    PAM_SYSTEMD(8)

NAME
pam_systemd - Register user sessions in the systemd control group hierarchy SYNOPSIS
pam_systemd.so DESCRIPTION
pam_systemd registers user sessions in the systemd control group hierarchy. On login, this module ensures the following: 1. If it does not exist yet, the user runtime directory /run/user/$USER is created and its ownership changed to the user that is logging in. 2. The $XDG_SESSION_ID environment variable is initialized. If auditing is available and pam_loginuid.so run before this module (which is highly recommended), the variable is initialized from the auditing session id (/proc/self/sessionid). Otherwise an independent session counter is used. 3. A new control group /user/$USER/$XDG_SESSION_ID is created and the login process moved into it. On logout, this module ensures the following: 1. If $XDG_SESSION_ID is set and kill-session-processes=1 specified, all remaining processes in the /user/$USER/$XDG_SESSION_ID control group are killed and the control group is removed. 2. If last subgroup of the /user/$USER control group was removed the $XDG_RUNTIME_DIR directory and all its contents are removed, too. If the system was not booted up with systemd as init system, this module does nothing and immediately returns PAM_SUCCESS. OPTIONS
The following options are understood: kill-session-processes= Takes a boolean argument. If true, all processes created by the user during his session and from his session will be terminated when he logs out from his session. kill-only-users= Takes a comma separated list of user names or numeric user ids as argument. If this option is used the effect of the kill-session-processes= options will apply only to the listed users. If this option is not used the option applies to all local users. Note that kill-exclude-users= takes precedence over this list and is hence subtracted from the list specified here. kill-exclude-users= Takes a comma separated list of user names or numeric user ids as argument. Users listed in this argument will not be subject to the effect of kill-session-processes=. Note that that this option takes precedence over kill-only-users=, and hence whatever is listed for kill-exclude-users= is guaranteed to never be killed by this PAM module, independent of any other configuration setting. controllers= Takes a comma separated list of control group controllers in which hierarchies a user/session control group will be created by default for each user logging in, in addition to the control group in the named 'name=systemd' hierarchy. If omitted, defaults to an empty list. reset-controllers= Takes a comma separated list of control group controllers in which hierarchies the logged in processes will be reset to the root control group. debug= Takes a boolean argument. If yes, the module will log debugging information as it operates. Note that setting kill-session-processes=1 will break tools like screen(1). Note that kill-session-processes=1 is a stricter version of KillUserProcesses=1 which may be configured system-wide in systemd- logind.conf(5). The former kills processes of a session as soon as it ends, the latter kills processes as soon as the last session of the user ends. If the options are omitted they default to kill-session-processes=0, kill-only-users=, kill-exclude-users=, controllers=, reset-controllers=, debug=no. MODULE TYPES PROVIDED
Only session is provided. ENVIRONMENT
The following environment variables are set for the processes of the user's session: $XDG_SESSION_ID A session identifier, suitable to be used in file names. The string itself should be considered opaque, although often it is just the audit session ID as reported by /proc/self/sessionid. Each ID will be assigned only once during machine uptime. It may hence be used to uniquely label files or other resources of this session. $XDG_RUNTIME_DIR Path to a user-private user-writable directory that is bound to the user login time on the machine. It is automatically created the first time a user logs in and removed on his final logout. If a user logs in twice at the same time, both sessions will see the same $XDG_RUNTIME_DIR and the same contents. If a user logs in once, then logs out again, and logs in again, the directory contents will have been lost in between, but applications should not rely on this behaviour and must be able to deal with stale files. To store session-private data in this directory the user should include the value of $XDG_SESSION_ID in the filename. This directory shall be used for runtime file system objects such as AF_UNIX sockets, FIFOs, PID files and similar. It is guaranteed that this directory is local and offers the greatest possible file system feature set the operating system provides. EXAMPLE
#%PAM-1.0 auth required pam_unix.so auth required pam_nologin.so account required pam_unix.so password required pam_unix.so session required pam_unix.so session required pam_loginuid.so session required pam_systemd.so kill-session-processes=1 SEE ALSO
pam.conf(5), pam.d(5), pam(8), pam_loginuid(8), systemd-logind.conf(5), systemd(1) AUTHOR
Lennart Poettering <lennart@poettering.net> Developer systemd 10/07/2013 PAM_SYSTEMD(8)
All times are GMT -4. The time now is 04:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy