02-08-2007
Logging off users
What is the best way to logoff users from my Unix system? I have done a search and found that you can do a w or who - find who is on, and ps-ef | grep <user> and kill their processes. But what if you have a bunch of users and you need them off the system quickly? Killing individual processes would take too long.
Much thanks.
outta.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have been asked to write a unix script to log and report all users logging on to our unix boxes as either the root or oracle users only on a 24 hour basis.
This should trap the logon and logoff time,if possible what they are doing and their username.
Thanks in Advance (2 Replies)
Discussion started by: irehman
2 Replies
2. UNIX for Dummies Questions & Answers
Hello All!
Does anyone know of a nice way to log commands in solaris 8.
What I need is a program or script that saves any command that a user does in solaris command prompt. So when Steven logs in on a system, it should record everything he does, from an ls to exit with timestamps. I've been... (6 Replies)
Discussion started by: dozy
6 Replies
3. Solaris
Hello,
I'm administrating new installed cluster that runs Legato Networker and Oracle 9. And I want to restrict the use of root to my self and givr the application and DBA the proper and needed privileges to do their duties without hassle in addition I would like to log users activities.
my... (0 Replies)
Discussion started by: sh_ksa
0 Replies
4. Solaris
I am looking for solutions to address my need to log to a file whenever a user logs out or session disconnects. (1 Reply)
Discussion started by: mhm4
1 Replies
5. UNIX for Advanced & Expert Users
We installed ssh on our AIX 5.3 box. The issue we are facing is that we dont get the users listed when we use 'w' or 'who'. After going through google without success, checked the www.openssh.org site. The FAQ section posted the solution that -
How do I go about this? Has anyone faced an issue... (2 Replies)
Discussion started by: ranj@chn
2 Replies
6. Solaris
I would like to know how to prevent users connecting to a server using SSH as root.
I would still like them to be able to login with their username and then change to su.
But I would like to prevent them logging in directly as root.
I have searched the forum and read that I should set... (3 Replies)
Discussion started by: Sepia
3 Replies
7. Shell Programming and Scripting
Hi,
How do force users to log off Unix through shell? (2 Replies)
Discussion started by: Wahmed9
2 Replies
8. Solaris
We recently underwent a security audit and have a new requirement to not allow users to stay logged on overnight. In order to place this policy into effect i need a way to check for idle users and log them off. Is there any good way to enforce this policy in Solaris 10 and make it work in such a... (11 Replies)
Discussion started by: goose25
11 Replies
9. Shell Programming and Scripting
Hi Guys!
I am sure that this question might appeared previously, but I still don't know how to show a list of logged out users. Please help with this!
Thanks in advance:) (5 Replies)
Discussion started by: saloliubliu
5 Replies
10. Linux
When unlocking a Linux server's console there's no event indicating successful logging
Is there a way I can fix this ?
I have the following in my rsyslog.conf
auth.info /var/log/secure
authpriv.info /var/log/secure (1 Reply)
Discussion started by: walterthered
1 Replies
KILL(1) Linux Programmer's Manual KILL(1)
NAME
kill - terminate a process
SYNOPSIS
kill [ -s signal | -p ] [ -a ] [ -- ] pid ...
kill -l [ signal ]
DESCRIPTION
The command kill sends the specified signal to the specified process or process group. If no signal is specified, the TERM signal is sent.
The TERM signal will kill processes which do not catch this signal. For other processes, it may be necessary to use the KILL (9) signal,
since this signal cannot be caught.
Most modern shells have a builtin kill function, with a usage rather similar to that of the command described here. The `-a' and `-p'
options, and the possibility to specify pids by command name is a local extension.
OPTIONS
pid... Specify the list of processes that kill should signal. Each pid can be one of five things:
n where n is larger than 0. The process with pid n will be signaled.
0 All processes in the current process group are signaled.
-1 All processes with pid larger than 1 will be signaled.
-n where n is larger than 1. All processes in process group n are signaled. When an argument of the form `-n' is given, and it
is meant to denote a process group, either the signal must be specified first, or the argument must be preceded by a `--'
option, otherwise it will be taken as the signal to send.
commandname
All processes invoked using that name will be signaled.
-s signal
Specify the signal to send. The signal may be given as a signal name or number.
-l Print a list of signal names. These are found in /usr/include/linux/signal.h
-a Do not restrict the commandname-to-pid conversion to processes with the same uid as the present process.
-p Specify that kill should only print the process id (pid) of the named processes, and not send any signals.
SEE ALSO
bash(1), tcsh(1), kill(2), sigvec(2), signal(7)
AUTHOR
Taken from BSD 4.4. The ability to translate process names to process ids was added by Salvatore Valente <svalente@mit.edu>.
Linux Utilities 14 October 1994 KILL(1)