Sponsored Content
Full Discussion: PAM closing SSH session
Top Forums UNIX for Dummies Questions & Answers PAM closing SSH session Post 302653359 by iamanewb on Friday 8th of June 2012 05:02:36 PM
Old 06-08-2012
Nothing gets shown.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Closing ssh when process run on remote

Hi! I currently run a very long script (two hour left...) on a remote computer through a ssh session. I wonder whats happend if I close the ssh session, or even, the terminal. Is the script running on remote will stop? Thanks for your answers, Tp (1 Reply)
Discussion started by: tipi
1 Replies

2. Solaris

closing of ssh section through script

Hi we have a script which establish connection to two other UNIX server through ssh for transfering files There was no exit command after each ssh connection the script ends with done whether this will close all the ssh connection established throgh script which running under cron... (4 Replies)
Discussion started by: GIC1986
4 Replies

3. Shell Programming and Scripting

closing a telnet session on error, in a shell script

I am using a shell script to telnet into a remote unix server and execute certain commands. But if any command being executed remotely, throws an error, the script just hangs. And the telnet session does not get closed. I want to be able to close the session and complete the script execution in... (1 Reply)
Discussion started by: farahzaiba
1 Replies

4. UNIX for Dummies Questions & Answers

Closing console connected to another machine via ssh

Hi, I have ssh'd into a UNIX server at work from my linux desktop and executed a tar command to backup up some directories to a tape drive. I was wondering would the tar command still execute to completion if I closed my terminal console on my desktop that is connected to the server, would the... (1 Reply)
Discussion started by: mojoman
1 Replies

5. OS X (Apple)

Opening and Closing Shares via ssh

Might anyone have an idea on how to mount an xserve share via ssh, then close the share connection? (3 Replies)
Discussion started by: unimachead
3 Replies

6. Shell Programming and Scripting

could not send commands SSH session with Net::SSH::Expect

I am using Net::SSH::Expect to connect to the device(iLO) with SSH. After the $ssh->login() I'm able to view the prompt, but not able to send any coommands. With the putty I can connect to the device and execute the commands without any issues. Here is the sample script my $ssh =... (0 Replies)
Discussion started by: hansini
0 Replies

7. HP-UX

ssh session getting hung (smilar to hpux telnet session is getting hung after about 15 minutes)

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

8. Solaris

SSH and PAM authentication issues on Solaris 10

This is a zone running Solaris 10u8 on a 6320 blade. The global zone is also running 10u8. One my users is attempting to change his password and getting a following screen: $ ssh remotesys Password: Warning: Your password has expired, please change it now. New Password: Re-enter new... (1 Reply)
Discussion started by: bluescreen
1 Replies

9. Emergency UNIX and Linux Support

PAM? cannot login, ssh or su

look at this, as root user change passwd and su -: I cannot ssh in or rlogin either, (3 Replies)
Discussion started by: bigearsbilly
3 Replies

10. Emergency UNIX and Linux Support

Nohup process getting killed after closing PUTTY session

I am running a process in nohup . nohup getkeys.ksh 132 > 132.out & When I close the putty terminal,The process is getting killed . default_signal_handler called for signal no: 1 Is there a way to keep the process running even If I close the terminal (2 Replies)
Discussion started by: prasperl
2 Replies
plink(1)							 PuTTY tool suite							  plink(1)

NAME
plink - PuTTY link, command line network connection tool SYNOPSIS
plink [options] [user@]host [command] DESCRIPTION
plink is a network connection tool supporting several protocols. OPTIONS
The command-line options supported by plink are: -V Show version information and exit. -pgpfp Display the fingerprints of the PuTTY PGP Master Keys and exit, to aid in verifying new files released by the PuTTY team. -v Show verbose messages. -load session Load settings from saved session. -ssh Force use of SSH protocol (default). -telnet Force use of Telnet protocol. -rlogin Force use of rlogin protocol. -raw Force raw mode. -serial Force serial mode. -P port Connect to port port. -l user Set remote username to user. -m path Read remote command(s) from local file path. -batch Disable interactive prompts. -pw password Set remote password to password. CAUTION: this will likely make the password visible to other users of the local machine (via com- mands such as `w'). -L [srcaddr:]srcport:desthost:destport Set up a local port forwarding: listen on srcport (or srcaddr:srcport if specified), and forward any connections over the SSH con- nection to the destination address desthost:destport. Only works in SSH. -R [srcaddr:]srcport:desthost:destport Set up a remote port forwarding: ask the SSH server to listen on srcport (or srcaddr:srcport if specified), and to forward any con- nections back over the SSH connection where the client will pass them on to the destination address desthost:destport. Only works in SSH. -D [srcaddr:]srcport Set up dynamic port forwarding. The client listens on srcport (or srcaddr:srcport if specified), and implements a SOCKS server. So you can point SOCKS-aware applications at this port and they will automatically use the SSH connection to tunnel all their connec- tions. Only works in SSH. -X Enable X11 forwarding. -x Disable X11 forwarding (default). -A Enable agent forwarding. -a Disable agent forwarding (default). -t Enable pty allocation (default if a command is NOT specified). -T Disable pty allocation (default if a command is specified). -1 Force use of SSH protocol version 1. -2 Force use of SSH protocol version 2. -C Enable SSH compression. -i path Private key file for authentication. -s Remote command is SSH subsystem (SSH-2 only). -N Don't start a remote command or shell at all (SSH-2 only). -sercfg configuration-string Specify the configuration parameters for the serial port, in -serial mode. configuration-string should be a comma-separated list of configuration parameters as follows: o Any single digit from 5 to 9 sets the number of data bits. o `1', `1.5' or `2' sets the number of stop bits. o Any other numeric string is interpreted as a baud rate. o A single lower-case letter specifies the parity: `n' for none, `o' for odd, `e' for even, `m' for mark and `s' for space. o A single upper-case letter specifies the flow control: `N' for none, `X' for XON/XOFF, `R' for RTS/CTS and `D' for DSR/DTR. MORE INFORMATION
For more information on plink, it's probably best to go and look at the manual on the PuTTY web page: http://www.chiark.greenend.org.uk/~sgtatham/putty/ BUGS
This man page isn't terribly complete. See the above web link for better documentation. PuTTY tool suite 2004-03-24 plink(1)
All times are GMT -4. The time now is 04:01 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy