06-13-2008
Thanks ! "kill -9" did the job
9 More Discussions You Might Find Interesting
1. Cybersecurity
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: (4 Replies)
Discussion started by: securhack
4 Replies
2. Shell Programming and Scripting
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)
Discussion started by: 435 Gavea
2 Replies
3. Shell Programming and Scripting
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)
Discussion started by: en7smb
3 Replies
4. Solaris
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)
Discussion started by: durgaprasadr13
0 Replies
5. HP-UX
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)
Discussion started by: yoda9691
1 Replies
6. Shell Programming and Scripting
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)
Discussion started by: jgt
3 Replies
7. Shell Programming and Scripting
I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time.
Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 Replies
8. Solaris
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
9. 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
REDIR(1) General Commands Manual REDIR(1)
NAME
redir - redirect tcp connections
SYNOPSIS
redir [--laddr=incoming.ip.address] [--caddr=host] [--debug] [--syslog] [--name=str] [--timeout=n] [--bind_addr=my.other.ip.address] [--ftp=type]
[--transproxy] [--connect=host:port] --lport=port --cport=port [--bufsize=n] [--max_bandwidth=n] [--random_wait=n] [--wait_in_out=n]
redir --inetd [--caddr=host] [--debug] [--syslog] [--name=str] [--timeout=n] [--ftp=type] [--transproxy] [--connect=host:port] --cport=port
[--bufsize=n] [--max_bandwidth=n] [--random_wait=n] [--wait_in_out=n]
DESCRIPTION
Redir redirects tcp connections coming in to a local port to a specified address/port combination.
It may be run either from inetd or as a standalone daemon. Depending on how redir was compiled, not all options may be available.
OPTIONS
--lport
Specifies port to listen for connections on (when not running from inetd)
--laddr
IP address to bind to when listening for connections (when not running from inetd)
--cport
Specifies port to connect to.
--caddr
Specifies remote host to connect to. (localhost if omitted)
--inetd
Run as a process started from inetd, with the connection passed as stdin and stdout on startup.
--debug
Write debug output to stderr or syslog.
--name Specify program name to be used for TCP wrapper checks and syslog logging.
--timeout
Timeout and close the connection after n seconds of inactivity.
--syslog
Log information to syslog.
--bind_addr
Forces redir to pick a specific address/interface to bind to when it listens for incoming connections.
--ftp When using redir for an FTP server, this will cause redir to also redirect ftp connections. Type should be specified as
either "port", "pasv", or "both", to specify what type of FTP connection to handle. Note that --transproxy often makes one
or the other (generally port) undesirable.
--transproxy
On a linux system with transparent proxying enabled, causes redir to make connections appear as if they had come from their
true origin. (see /usr/share/doc/redir/transproxy.txt)
--connect
Redirects connections through an HTTP proxy which supports the CONNECT command. Specify the address and port of the proxy
using --caddr and --cport. --connect requires the hostname and port which the HTTP proxy will be asked to connect to.
--bufsize n
Set the bufsize (defaut 4096) in bytes. Can be used combined with --max_bandwidth or --random_wait to simulate a slow con-
nection.
--max_bandwidth n
Reduce the bandwidth to be no more than n bits/sec. The algorithme is basic, the goal is to simulate a slow connection, so
there is no pic acceptance.
--random_wait n
Wait between 0 and 2 x n milliseconds before each "packet". A "packet" is a bloc of data read in one time by redir. A
"packet" size is always less than the bufsize (see also --bufsize).
--wait_in_out n
Apply --max_bandwidth and --random_wait for input if n=1, output if n=2 and both if n=3.
SEE ALSO
inetd(1)
local REDIR(1)