Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: Automating pbrun /bin/su not working, whenever manually it is working using putty
Top Forums Shell Programming and Scripting Automating pbrun /bin/su not working, whenever manually it is working using putty Post 302961497 by RudiC on Monday 30th of November 2015 12:11:05 PM
Old 11-30-2015
From the puttydocumentation:
Quote:
3.8.3.6 -m: read a remote command or script from a file

The -m option performs a similar function to the ‘Remote command’ box in the SSH panel of the PuTTY configuration box (see section 4.18.1). However, the -m option expects to be given a local file name, and it will read a command from that file.
With some servers (particularly Unix systems), you can even put multiple lines in this file and execute more than one command in sequence, or a whole shell script; but this is arguably an abuse, and cannot be expected to work on all servers. In particular, it is known not to work with certain ‘embedded’ servers, such as Cisco routers.

Did you consider using plink (from the putty family)?
 

10 More Discussions You Might Find Interesting

1. Solaris

/usr/bin/cut not working with largefiles on Solaris 10

I have a person running a perl script that is parsing > 2G log files and pipes to cut -d " " -f 1,6,7,8... The script itself is in a nfs mounted home directory. It runs fine when started from a solaris 8 box but fails after about 400 lines when started from the solaris 10 box. The solaris... (1 Reply)
Discussion started by: wottie
1 Replies

2. Shell Programming and Scripting

#/usr/bin/csh -f not working as expected?

Hey everyone, A coworker of mine has written a csh script that starts with #!/usr/bin/csh -f. It's my understanding that the -f should skip the .cshrc and .login files, but here's the problem: In the script "line" is used, and I happen to have a "line" in my ~/bin. When the script is ran my... (4 Replies)
Discussion started by: effigy
4 Replies

3. Shell Programming and Scripting

#!/bin/bash has stopped working

Hi I'm writing a script and I've put #!/bin/bash as the first line so that I can just type my scripts name 'whodate' at PS1 instead of ./whodate. This has suddenly stopped working for me. It used to be the case that I could start a script with #!/bin/bash and it would work, but for this script... (2 Replies)
Discussion started by: zorrokan
2 Replies

4. Shell Programming and Scripting

Script is not working from cron while working manually

Hello, I am facing a very strange problem when I run my script manuallu ./Fetchcode which is using to connect with MKS integrity from linux end it workks fine but when I run it from cron it doesn't work.Can someone help me 1) How could I check my script when it is running from cron like... (3 Replies)
Discussion started by: anuragpgtgerman
3 Replies

5. Shell Programming and Scripting

Getting issue while running it from cron while manually working fine

Hello, I am working one one script where I am using the below code which is using to connect with MKS client when I run my script manually it works effiecently i.e. it connects with MKS client but when I run it from CRON it doesn't connect. 1)Can some one tell when it is running from cron... (1 Reply)
Discussion started by: anuragpgtgerman
1 Replies

6. Shell Programming and Scripting

/usr/local/bin/expr function not working

Legends, I am not able to set "expr" function in ksh script. Below is the sample code i used, and output is as "Syntax error" Please help me to come out of it. OUTPUT (9 Replies)
Discussion started by: sdosanjh
9 Replies

7. Solaris

Putty SSH connection not working

I am trying to connect to a solaris server using putty from a indows client. SSH connection is not working. The terminal indow just gives an error message "Network error:Connection refused". I verified SSHD and its running correctly! #svcs -p ssh STATE STIME FMRI online 17:54:44... (3 Replies)
Discussion started by: herbich1985
3 Replies

8. Shell Programming and Scripting

Script not working in cron but working fine manually

Help. My script is working fine when executed manually but the cron seems not to catch up the command when registered. The script is as follow: #!/bin/sh for file in file_1.txt file_2.txt file_3.txt do awk '{ print "0" }' $file > tmp.tmp mv tmp.tmp $file done And the cron... (2 Replies)
Discussion started by: jasperux
2 Replies

9. Shell Programming and Scripting

Script working when run manually but not in crontab showing path not found

i have a script running using variable defined in .profile when i run that script manually its working but when i run the same script through cron its giving path not found I had defined path in .profile (3 Replies)
Discussion started by: raj_saini20
3 Replies

10. Shell Programming and Scripting

Nested if not working with /usr/xpg4/bin/awk

Hi, I am trying to do if inside the If in /usr/xpg4/bin/awk. But I am getting below error : /usr/xpg4/bin/awk -v a="${THREADIDARR }" 'BEGIN {FS="|"; n=split(a,b," "); for(i=1; i<=n; i++) c]=1;} length($3) == 0{ftag == 1{{print}}; length($3) != 0{$3 in c{ftag=1;print;} !$3 in c{ftag=0;}}'... (4 Replies)
Discussion started by: nes
4 Replies

LEARN ABOUT DEBIAN

plink

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 10:42 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy