Sponsored Content
Full Discussion: Shell exit due to inactivity
Top Forums Shell Programming and Scripting Shell exit due to inactivity Post 302455469 by sriki32 on Tuesday 21st of September 2010 05:56:02 PM
Old 09-21-2010
Shell exit due to inactivity

I am installing an executable files. It takes around 30 minutes. During this time...the shell pops the msg "due to inactivity shell pops out in 60 seconds. I dont want this to happen. the terminal shouldnt exit at all. Is there any way that it doesnt exit.I am using putty with ksh
 

10 More Discussions You Might Find Interesting

1. SCO

Apparent logoff’s due to inactivity.

I have run across an issue with the last two Dell Poweredge servers I have attempted to deploy. I seems that when a telnet session sits idle for 5 to 30 minutes (seems random) the session is being closed and users are logged off. If the session has user activity there is no problem staying... (0 Replies)
Discussion started by: gadgetman
0 Replies

2. UNIX for Advanced & Expert Users

User inactivity at OS level

Dear friends, Can anyone let me know how to configure various OS mentioned below to get user ids deactivated automatically if not logged in at all for a period of, say, 45 days? 1. UNIX / Linux / AIX / Tru64 2. It is OK whether the solution is by running OS commands / running scripts written... (1 Reply)
Discussion started by: bache_gowda
1 Replies

3. Solaris

solaris 9 console inactivity timeout

All, I log into Solaris 9 server through a command line at the console and want enable a inactivity timer to log out of the server after 5 minutes. How can it be done? (1 Reply)
Discussion started by: bubba112557
1 Replies

4. AIX

Can't login root account due to can't find root shell

Hi, yesterday, I changed root's shell in /etc/passwd, cause a mistake then I can not log in root account (can't find correct shell). I attempted to log in single-mode, however, it prompted for single-mode's password then I type root's password but still can not log in. I'm using AIX 5L version 5.2... (2 Replies)
Discussion started by: neikel
2 Replies

5. Shell Programming and Scripting

command does not return exit status due to tee

Hi, I am using /bin/sh. I want to display the stdout and stderr on the terminal as well as save it in a file, so I'm using this command. gmake all 2>&1 | tee log But even if gmake fails, it's always giving 0 as exit status, i suppose because of tee. # false 2>&1 | tee Log # echo $? 0... (2 Replies)
Discussion started by: anand_bh
2 Replies

6. Red Hat

inactivity default to 30 days

Hi All, On red hat ent 4. How do I make the inactivity a default to 30 days? What config file I need to modify so that I will not modify /etc/shadow? Thanks for any comment you may add. (1 Reply)
Discussion started by: itik
1 Replies

7. UNIX for Dummies Questions & Answers

lock the console after 5 minutes of inactivity.

How would i force The server console to be locked automatically after 5 minutes ? I want it to happen for X as well as terminal session of the machine. My Linux distribution details. LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID:... (11 Replies)
Discussion started by: pinga123
11 Replies

8. AIX

last - find out inactivity

I am on AIX 6.1, and need to find out who has not accessed the system within 1, 2, or 3 months depending upon the filter I specify. The output I need to have is the account name and the last time accessed: i.e. kart Mar 27 05:13 - 05:13 (00:00) Please advise. (5 Replies)
Discussion started by: Daniel Gate
5 Replies

9. Solaris

User inactivity

Simple question: for determining whether the user has exceeded the maximum amount of "inactivity" (as set in the shadow file) what date is the current login being compared to? Is it wtmp data or something? (3 Replies)
Discussion started by: thmnetwork
3 Replies

10. Solaris

Korn shell - evaluating string gives wrong results due to limitations

Anyone ever seen this? Someone mentioned this the other day.... If you do, for instance, in korn shell, echo $(5.2+2.5), it gives the result of 6 regardless. Can't remember why but it was the limitation of the korn shell. (5 Replies)
Discussion started by: psychocandy
5 Replies
exit(1)                                                            User Commands                                                           exit(1)

NAME
exit, return, goto - shell built-in functions to enable the execution of the shell to advance beyond its sequence of steps SYNOPSIS
sh exit [n] return [n] csh exit [ ( expr )] goto label ksh *exit [n] *return [n] DESCRIPTION
sh exit will cause the calling shell or shell script to exit with the exit status specified by n. If n is omitted the exit status is that of the last command executed (an EOF will also cause the shell to exit.) return causes a function to exit with the return value specified by n. If n is omitted, the return status is that of the last command exe- cuted. csh exit will cause the calling shell or shell script to exit, either with the value of the status variable or with the value specified by the expression expr. The goto built-in uses a specified label as a search string amongst commands. The shell rewinds its input as much as possible and searches for a line of the form label: possibly preceded by space or tab characters. Execution continues after the indicated line. It is an error to jump to a label that occurs between a while or for built-in command and its corresponding end. ksh exit will cause the calling shell or shell script to exit with the exit status specified by n. The value will be the least significant 8 bits of the specified status. If n is omitted then the exit status is that of the last command executed. When exit occurs when executing a trap, the last command refers to the command that executed before the trap was invoked. An end-of-file will also cause the shell to exit except for a shell which has the ignoreeof option (See set below) turned on. return causes a shell function or '.' script to return to the invoking script with the return status specified by n. The value will be the least significant 8 bits of the specified status. If n is omitted then the return status is that of the last command executed. If return is invoked while not in a function or a '.' script, then it is the same as an exit. On this man page, ksh(1) commands that are preceded by one or two * (asterisks) are treated specially in the following ways: 1. Variable assignment lists preceding the command remain in effect when the command completes. 2. I/O redirections are processed after variable assignments. 3. Errors cause a script that contains them to abort. 4. Words, following a command preceded by ** that are in the format of a variable assignment, are expanded with the same rules as a vari- able assignment. This means that tilde substitution is performed after the = sign and word splitting and file name generation are not performed. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | |Availability |SUNWcsu | +-----------------------------+-----------------------------+ SEE ALSO
break(1), csh(1), ksh(1), sh(1), attributes(5) SunOS 5.10 15 Apr 1994 exit(1)
All times are GMT -4. The time now is 11:59 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy