06-04-2007
Some progress
The tmout functions is completely removed from the images we install.
It seems right now that we have a problem with "computer-power-pirates".
Other users who run scripts on other users personal machines to check if that machine is availible for heavy calculations. If it is, they run there heavy algorithms remote in order to speed up their own work.
How this causes the user sitting at the host to be logged out is still a mystery though.
Were beginning to think that the problem is due to that the CAD program (Catia) has only one active lib to control the license and a few other configfiles. The problem is if one user have this CAD-program "running" while idle and another user starts running the same program on the same machine the new users files overwright the first users files and what happens is that the first user get kicked out from the Catia-license server.
But why the user also gets kicked out of the unixsystem is still a mystery.
But atleast were on to it now.
10 More Discussions You Might Find Interesting
1. HP-UX
My max user parm is set to 1050. I'm currently at 1038 this is causing major slow downs on the server. I looking for a way log off "idle" user logins with out having to do it individually. :confused: (5 Replies)
Discussion started by: rfmurphy_6
5 Replies
2. AIX
How to set a timer for log out users that have been idle for a long time? It is a AIX 5L (0 Replies)
Discussion started by: wtofu
0 Replies
3. Shell Programming and Scripting
I am trying to write a script that will list the idle users on my system which is running HPUX 11.11. The script is currently written as :
who -u > /home/rfm/scripts/user.txt
echo " There are currently... "
wc -l /home/rfm/scripts/user.txt
echo " User logins on System : `uname -n` ... (3 Replies)
Discussion started by: rfmurphy_6
3 Replies
4. 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
5. Shell Programming and Scripting
Please help, im modifing an idle script to capture (not kill) users who havee been idle over a time. now i've got to work with the exection of users whos idle time gove over 24 hrs and becomes "old". please advice on how to correct...
#Clear old report, generate new data and new report
echo "\n... (1 Reply)
Discussion started by: pbonilla
1 Replies
6. Shell Programming and Scripting
hello, i am VERY new to this whole script world. I need to come up with a script that will email a user if they have an idle process past 500 minutes...any suggestions??? Thanks so much. (0 Replies)
Discussion started by: sheppy28
0 Replies
7. Shell Programming and Scripting
I wrote a script to kill users idle more than 1/2 hour, ignoring those in an exception list. Here is the script as it is now:
#! /usr/bin/awk -f
BEGIN {
system("who -u | sort +5 > /tmp/loginfile");
system("echo User Sessions Killed > /tmp/killedlogins");
... (2 Replies)
Discussion started by: PapaBear
2 Replies
8. 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
9. 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
10. AIX
Hi
The telnet sessions stay as idle users. It is not getting kicked out.
Please advise what could be the issue. only when we reboot the server these telnet sessions goes.
Below is the current output from the server. we rebooted the server three days ago:
pmut6:/> uptime
04:21PM... (8 Replies)
Discussion started by: newtoaixos
8 Replies
rwho(1) General Commands Manual rwho(1)
NAME
rwho - Shows which users are logged into hosts on the local network.
SYNOPSIS
rwho [-a]
rwho [-a] [users]
OPTIONS
Includes all users. Without this option, users whose sessions are idle an hour or more are not included in the report.
DESCRIPTION
The rwho command displays the username, hostname, and start date and time of each session for everyone on the local network who is cur-
rently logged in to a host running the rwhod daemon.
If one or more user names are specified, only the status of those users whose names are listed appears on the screen. If a user has not
typed anything for at least 3 minutes, rwho reports the idle time as a number of minutes in the last column. After an hour of inactivity,
a user is not included unless the -a option is specified. Because this command displays a lot of output, use this command with caution if
the local network has a large number of users.
Status information is broadcast once every 3 minutes by each network host running the rwhod daemon. Any activity (such as a user logging on
or off) that takes place between broadcasts is not reflected until the next broadcast.
EXAMPLES
To get a report of all users currently logged into hosts on the local network, enter:
$ rwho
bob host2:pts5 Nov 17 06:30 :20 bob host7:console Nov 17 06:25 :25 franz
host1:pts0 Nov 17 11:20 :51 franz host1:pts8 Nov 16 15:33 :42 franz host4:console
Nov 17 16:32 pietro host1:console Nov 17 13:14 :31 pietro host1:pts7 Nov 17 13:15 :47 server
host2:console Nov 17 06:58 :20 luis host2:pts6 Nov 17 09:22
FILES
Indicates data files received from remote rwhod daemons.
SEE ALSO
Commands: ruptime(1), rwhod(8)
rwho(1)