Sponsored Content
Full Discussion: Killing Idle session
Special Forums Cybersecurity Killing Idle session Post 4268 by Holistic on Monday 23rd of July 2001 08:46:21 AM
Old 07-23-2001
thanx but...this prameter only works for ROOT and not regular users. i have trired putting this prameter in .profile of the user, in the /etc/default/login, in the /etc/default/telnetd for telnet sessions and none of them have been successful...Smilie Smilie

Last edited by Holistic; 07-24-2001 at 05:51 PM..
 

9 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Killing idle user processes

I'm looking for some help, please! I'm trying to kill any idle user processes over 40 Minutes. I have tried putting TMOUT=2400 within the users .profile However this does not seem to be working. We run aix 4.3.3 with ORACLE 7.3 The above works o.k. when the user is only within the... (3 Replies)
Discussion started by: annette
3 Replies

2. Shell Programming and Scripting

script for killing idle users

I need a script that will look for idle users and kill there proc. (7 Replies)
Discussion started by: jdel80
7 Replies

3. Shell Programming and Scripting

Killing idle users TIA

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

4. UNIX for Dummies Questions & Answers

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

Still it is not working. I had given 200 in putty but still it is expiring within 1 minute. (1 Reply)
Discussion started by: vamshikrishnab
1 Replies

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... (7 Replies)
Discussion started by: vamshikrishnab
7 Replies

6. Shell Programming and Scripting

Help in killing the session !

Hello, I am new to unix scripts and have been experimenting with do-while structure. I have run into a problem. my script is, --- while true do ./redir --lport=55083 --caddr=14.121.119.21 --cport=55083 2>&1 >> /tmp/out.txt echo "Restarting `date`" done --- As you can see, i didnt handle... (3 Replies)
Discussion started by: script_newbie
3 Replies

7. Shell Programming and Scripting

Kill idle script is killing unnecessarly

Hi All,I have a problem with my kill idle script.my script is supposed to kill the user sessions which are idle for more than 2 hours.But is is killing the sessions which are idle for less than 2 hrs also.I dont know the exact time after which the script is killing,but it is less than 2 hours i am... (3 Replies)
Discussion started by: prabhu_kumar
3 Replies

8. Solaris

Kill idle dt session

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. HP-UX

Get blank screen when killing a UNIX session on HP-UX

Hi, I have this Unix script that kills a user session. When I run it, my screen goes blank. How do I prevent the blank screen? Ex: I open 2 Unix sessions. The main PID for my 1st session is 1234. In the second session I issue a "kill -HUP 1234". The first session gets killed but the second... (5 Replies)
Discussion started by: rm-r
5 Replies
telnetd(8)						      System Manager's Manual							telnetd(8)

NAME
telnetd - The DARPA telnet protocol server SYNOPSIS
telnetd [-debug [port]] [-D modifier ...] FLAGS
Starts telnetd manually, rather than through inetd, on alternate TCP port number port (if specified). Prints out debugging information. modifiers are: Prints information about negotiation of telnet options Same as options with additional processing information Displays the data stream received by telnetd Displays data written to the pty Not yet implemented DESCRIPTION
The telnetd daemon is a server that supports the DARPA (Defense Advanced Research Projects Agency) standard telnet virtual terminal proto- col. telnetd is invoked by the Internet server (see inetd(8)) normally for requests to connect to the telnet port as indicated by the /etc/services file (see services(4)). The -debug flag may be used, to start up telnetd manually. If started up this way, port may be specified to run telnetd on an alternate TCP port number. The -D options may be used for debugging purposes. This allows telnetd to print out debugging information to the connection, allowing the user to see what telnetd is doing. The telnetd daemon operates by allocating a pseudoterminal device (see pty(7)) for a client, then creating a login process that has the slave side of the pseudoterminal as stdin, stdout, and stderr. telnetd manipulates the master side of the pseudo-terminal, implementing the telnet protocol and passing characters between the remote client and the login process. When a telnet session is started up, telnetd sends telnet options to the client side, indicating a willingness to do remote echo of charac- ters, to suppress go ahead, to do remote flow control, and to receive terminal type information, terminal speed information, and window size information from the remote client. If the remote client is willing, the remote terminal type is propagated in the environment of the created login process. The pseudoterminal allocated to the client is configured to operate in cooked mode, and with XTABS and CRMOD enabled (see tty(7)). The telnetd daemon is willing to do: echo, binary, suppress go ahead, and timing mark. telnetd is willing to have the remote client do: line mode, binary, terminal type, terminal speed, window size, toggle flow control, environment, X display location, and suppress go ahead. The telnetd daemon never sends telnet go ahead commands. Note that binary mode has no common interpretation except between similar operating systems (Unix compatible systems in this case). Note also that the terminal type name received from the remote client is converted to lowercase. The telnet command uses the default Type-of-Service value recommended by RFC1060, which is as follows: Low delay You can configure this value by specifying it in the /etc/iptos file. For more information, see iptos(4). By default, the telnetd daemon starts the login dialog using the login string specified in the message field of the /etc/gettydefs file. If you want to use a customized banner, create an /etc/issue.net or /etc/issue file. The telnetd daemon reads the file that exists and writes its contents over a new telnet connection prior to starting the login dialog. If both files exist, only the /etc/issue.net file is used. CAUTIONS
Some telnet commands are only partially implemented. Because of bugs in the original 4.2BSD telnet(1), telnetd performs some dubious protocol exchanges to try to discover if the remote client is, in fact, a 4.2BSD telnet(1). FILES
Specifies the command path. Specifies the path name for the network issue identification file. Specifies the path name for the issue identification file. RELATED INFORMATION
Commands: telnet(1). Files: iptos(4), issue(4), issue.net(4). delim off telnetd(8)
All times are GMT -4. The time now is 03:43 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy