Every session is expiring within 1 minute if it kept idle. Post: 302197704

9 More Discussions You Might Find Interesting

1. Cybersecurity

Killing Idle session

does any one know how to kill an idle session? I want to kill any idle sessions after 30 min... Local or remote.... i want to do this without a script or TCP wrappers...i want to know if there is a file that i can configure..... ThAnks:rolleyes:

2. AIX

Knowing when is the user id expiring

HI, Do we have a command in AIX which will let us know when is the user id password getting expired!! Any advice will be of great help!! Thanks, Siddharth

3. Shell Programming and Scripting

FTP session expiring when transferring files... Need some solution

Hi All, I am running a ftp script which is running fine even with crontab. But the problem is that when I connect to ftp server and transfer files , i observe that ftp session expires after few minutes and the file transfer is not completed as there are alot of files to be transfered . ...

4. Solaris

Extension of passwd expiring

Hi all, Anyway to reset the passwd expiring time without user having to reset it themselve? Beside altering the maximum number of days the password is valid in the shadow file, is there any other ways? Reason, user forgot passwd and the account passwd cannot be reset, same passwd is need for...

5. Solaris

Every session is expiring within 1 minute if it kept idle.

Hi, I am accessing a solaris server via client machine. My problem is that every session is expiring within 1 minute if it kept idle. I am facing problem as i have to enter the credentials around 30 to 40 times per day. I tried to set the TMOUT variable but it does n't work. Please help...

6. Solaris

Kill idle dt session

Hi, i need to kill the idle dt sessions through script, can anyone tell me how to do? RJS

7. UNIX for Dummies Questions & Answers

Non expiring password

Which files store the information about user with non expiring password in case of HP-UNIX like /etc/shadow in linux Two threads by Anu_1 merged

8. Shell Programming and Scripting

Take minute per minute from a log awk

Hi, I've been trying to develop a script that performs the parsing of a log every 1 minute and then generating some statistics. I'm fairly new to programming and this is why I come to ask if I can lend a hand. this is my log: xxxx 16/04/2012 17:00:52 - xxxx714 - E234 - Time= 119 ms....

9. Solaris

Expiring password notifications

I have a Solaris 10 server that notified one of my users/database administrators of another users account expiring within X amount of days. It attempted to email the user@ server.com, which failed and was forwarded from the mailer-daemon@ server.com, to the DBA. She's not listed as an alias for...

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)