I'm not very good at shell programming though, you can use following code to kill users who are inactive for more than 30 minutes:
You can modify this as per your requirements.
Hi there.
How do I make the DB connection see the parameter variables passed to the unix script ? The code snippet below isn't working properly.
sqlplus << EOF
user1@db1/pass1
BEGIN
PACKAGE1.perform_updates($1,$2,$3);
END;
EOF
Thanks in advance,
Abrahao. (2 Replies)
Hi,
Apologies if anyone has read my recent post on the same subject in the Linux forum, just thought actually the solution might more likely come from scripting.
Essentially, I am trying to restrict access to directories based on the user's name AND their location on a session-by-session... (3 Replies)
I am not able to login in gnome session and java session in Sun solaris 9& 10 respectively through xmanager as a nis user, I am able to login in common desktop , but gnome session its not allowing , when I have given login credentials, its coming back to login screen, what shoul I do to allow nis... (0 Replies)
Our network administrators implemented some sort of check to kill idle sessions and now burden is on us to run some sort of keep alive. Client based keep alive doesn't do a very good job. I have same issue with ssh. Does solution 2 provided above apply for ssh sessions also? (1 Reply)
Besides 'who am i' and 'tty' what commands could be used to determine if a session is interactive as compared to a web process or cron process. Any command should work with the common unix variants. (3 Replies)
what is the difference between desktop session and console session in solaris
as i am wondering we use option -text for the former and -nowin for the later (1 Reply)
Discussion started by: kishanreddy
1 Replies
LEARN ABOUT HPUX
ruptime
ruptime(1) General Commands Manual ruptime(1)NAME
ruptime - show status of local machines
SYNOPSIS DESCRIPTION
outputs a status line for each machine on the local network that is running the daemon. status lines are formed from packets broadcast
once every 3 minutes between daemons (see rwhod(1M)) on each host on the network. Each status line has a field for the name of the
machine, the status of the machine (up or down), how long the machine has been up or down, the number of users logged into the machine, and
the 1-, 5- and 15-minute load averages for the machine when the packet was sent.
The status of the machine is reported as ``up'' unless no report has been received from the machine for 11 minutes or more.
The length of time that the machine has been up is shown as:
Load averages are the average number of jobs in the run queue over the last 1-, 5- and 15-minute intervals when the packet was sent.
An example status line output by might be:
The above status line would be interpreted as follows:
is presently ``up'' and has been up for 1 day, 5 hours and 15 minutes. It currently has 7 users logged in. Over the last 1-minute inter-
val, an average of 1.47 jobs were in the run queue. Over the last 5-minute interval, an average of 1.16 jobs were in the run queue. Over
the last 15-minute interval, an average of 0.80 jobs were in the run queue.
If a user has not used the system for an hour or more, the user is considered idle. Idle users are not shown unless the option is speci-
fied.
Options
If no options are specified, the listing is sorted by host name. Options change sorting order as follows:
Sort by load average.
Sort by up time.
Sort by the number of users.
Reverse the sort order.
DIAGNOSTICS
No status report files in
Ask the system administrator to check whether the daemon is running.
AUTHOR
was developed by the University of California, Berkeley.
FILES
Data files
SEE ALSO rwho(1), rwhod(1M).
ruptime(1)