|
|
Sponsored Content
Operating Systems
Solaris
kill user session
Post 302130260 by fredginting on Saturday 4th of August 2007 08:07:50 AM
08-04-2007
|
|
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
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
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
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
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
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
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
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
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
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
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
LEARN ABOUT OSX
kill.d
kill.d(1m) USER COMMANDS kill.d(1m) NAME
kill.d - snoop process signals as they occur. Uses DTrace. SYNOPSIS
kill.d DESCRIPTION
kill.d is a simple DTrace program to print details of process signals as they are sent, such as the PID source and destination, signal num- ber and result. This program can be used to determine which process is sending signals to which other process. Since this uses DTrace, only users with root privileges can run this command. EXAMPLES
Default output, print process signals as they are sent. # kill.d FIELDS
FROM source PID COMMAND source command name TO destination PID SIG destination signal ("9" for a kill -9) RESULT result of signal (-1 is for failure) DOCUMENTATION
See the DTraceToolkit for further documentation under the Docs directory. The DTraceToolkit docs may include full worked examples with ver- bose descriptions explaining the output. EXIT
kill.d will run forever until Ctrl-C is hit. AUTHOR
Brendan Gregg [Sydney, Australia] SEE ALSO
dtrace(1M), truss(1) version 0.90 May 14, 2005 kill.d(1m)