Sponsored Content
Full Discussion: Drop Users
Top Forums UNIX for Dummies Questions & Answers Drop Users Post 82398 by reborg on Wednesday 31st of August 2005 02:30:46 PM
Old 08-31-2005
Find the root process of their login session and kill it, for example if they log in using telnet, find the spawned instance of telnet for their session and kill that.
 

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Dynamic Drop down boxes

Hello All, I am trying to come up with this interface with the backend on perl. The interface needs drop down boxes with dynamic chain loading ( as in contents of the 1st drop down box will populate the second drop down and so on) Any idea how I can do this? Kindly help Regards, Garric (13 Replies)
Discussion started by: garric
13 Replies

2. UNIX for Dummies Questions & Answers

Drop a Column from a File

Hi, I need to drop a column from a file. My .txt file having 20 columns first column as GroupBy column which is not necessery in further processing. So i need to create a new files without this column. Please help how to do this? Thanks, Raamc :rolleyes: (4 Replies)
Discussion started by: Raamc
4 Replies

3. UNIX for Dummies Questions & Answers

read and drop files

I have hundreds of small files in csv format. I want to read them one at a time, insert the data into a table and then delete it. data1 to data999.txt files needs to be read and data to be added to a table. mysql -e"LOAD DATA INFILE 'data1.txt' INTO TABLE my_table;" if echo $? = 0 then rm... (1 Reply)
Discussion started by: shantanuo
1 Replies

4. Shell Programming and Scripting

using sed but want to drop last line

Howdy all. I have some scripts that read a text file looking for a keyword, then returning all the text until another keyword and puts it into a new file. Problem is, sed returns the entire last line that contains the 2nd keyword, and I don't want it! Here's an example of the sed script line: ... (21 Replies)
Discussion started by: atc98092
21 Replies

5. Shell Programming and Scripting

Script to drop oracle DB users on HP, LINUX, SOLARIS

Hi everybody, i need help from all of you. I have many users who are no more work in our Company. Some who get objects are Locked. There Many users and many Database Servers. And it'll take long for me to finished this job. That's why i need your help to provide me anyone Scripts... (2 Replies)
Discussion started by: Sonson
2 Replies

6. Shell Programming and Scripting

drop down structure in file

I have file like this 120, rahim, d40 115, rahul, d40 113, begum, d40 I want to group this file like this 120, rahim, d40 115, rahul, 113, begum, can any one help me on this thanks in advance (1 Reply)
Discussion started by: trichyselva
1 Replies

7. Shell Programming and Scripting

Drop down menu

How to create a drop down menu in either bash or ksh? (3 Replies)
Discussion started by: proactiveaditya
3 Replies

8. Web Development

Dynamic Drop Down Menu

I need to create a dynamic drop down menu which is populated by entries such as; htdocs/client1/index.php htdocs/client2/index.php htdocs/client3/index.php htdocs/client4/index.php etc. So htdocs/client*/index.php Is this possible? I know how to do this using normal arrays, but not... (2 Replies)
Discussion started by: JayC89
2 Replies

9. UNIX for Dummies Questions & Answers

DNS Drop out

My boss use a MacBook and he encounter with DNS drop out and he cannot surf website for 1-2 mins. The DNS Service of my company is on UNIX server. I try to delete some unused IP of DNS Server in resolv.conf and dhcp.conf and I try to update root.hint file but The problem is not fixed. Please... (5 Replies)
Discussion started by: thsecmaniac
5 Replies

10. What is on Your Mind?

Should We Keep or Drop the Bottom Toolbar?

Well, it's been a few months now since we started running the toolbar on the bottom with some navigation menu, search, link to code tag video, some social networking tools, etc. So, the question of the day is: Should we keep it, maybe develop more toolbar apps, or dump it? Please vote ... (13 Replies)
Discussion started by: Neo
13 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 03:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy