It wouldn't even work locally. Go ahead and try it, see what happens. su will run, and cd will not run inside it - but it will run, after su quits, because that's what semicolon means. Run this command, wait for it to quit, then run that other command.
To feed something into a program, you need to use redirection.
What I do to run scripts remotely is something like:
The final EOF can't be indented, at all.
When in doubt, replace 'ssh' with 'cat' to see exactly what script you're trying to send to the far side!
I have a linux box build11 which can be pinged from build18 (Windows) box. And we can only login to the box (using SSH) from build18 box. Plz help to characterize the problem, network, DNS, DHCP, etc (or whatever which I am unsure)
Any idea what may be the reason ? :confused:
Thanks in... (4 Replies)
i have this SSH command which runs perfectly on command prompt in sunOS
ssh -o Port=${portno} ${uname}@${server} find ${dir_path} -name '***'
output : /usr/local/home/***
My problem is when i run same command in my script
#!/usr/bin/ksh
res=`ssh -o Port=${portno} ${uname}@${server}... (1 Reply)
Hi,
I have a solaris 8 machine.
I see ssh is running in the machine
sbnismwp2# ps -aef | grep ssh
root 947 945 0 04:34:45 ? 0:00 /export/opt/SSHtecagt/sbin/ssh-mgmt-sysmonitor
root 945 1 0 04:34:45 ? 0:00 /export/opt/SSHtecagt/sbin/ssh-mgmt-agent... (11 Replies)
Hi,
I am writing a script on Solaris 10 and want to execute a remote ssh command. Normally this command should just return the value 0000000000002356 but when using ssh it seems it is passing the result to the shell to execute.
ssh root@10.5.112.145 `/usr/bin/nawk -F\, '$1=="USG" && $2=="01"... (3 Replies)
I have a Solaris 9 server that does not return a ping. When I try to log in via SSH I eventually get in. I am logged in now.
I know this is a wide open question, but can you recommend some things I should check?
.
Thanks in advance,
~R (2 Replies)
Hi all,
I am using the below code to ping a code and print whehter the connection is successful or not.
use Net::Ping;
$p = Net::Ping->new();
my $host = "x.x.x.x";
# print "$host is alive.\n" if $p->ping($host);
if ($p->ping($host,3))
{
print... (0 Replies)
Hello all,
I am writing a script that pings various machines to check connectivity.
If a machine is available, the prompt returns a result immediately:
root@ops # ping 172.21.5.5
172.21.5.5 is alive
BUT
if a machine is Down , the reply takes a long time to come. The issue is I want to... (1 Reply)
I cant ping to some of my machines, but ping works.
I attach screenshots. Port is open and it is 22.
I can't figure out why i cant access.
https://www.unix.com/attachments/unix-for-advanced-and-expert-users/7492d1541541072-cant-ssh-but-ping-works-sshlisten-jpg... (17 Replies)
Discussion started by: tomislav91
17 Replies
LEARN ABOUT DEBIAN
mrtg-ping-probe
MRTG-PING-PROBE(1) General Commands Manual MRTG-PING-PROBE(1)NAME
mrtg-ping-probe - ping probe module for Multi Router Traffic Grapher
DESCRIPTION
mrtg-ping-probe is a ping probe module for MRTG 2.x. It is used to monitor the round trip time and packet loss to networked devices. MRTG
uses the output of mrtg-ping-probe to generate graphs visualizing minimum and maximum round trip times or packet loss.
mrtg-ping-probe is not run directly, but is called by MRTG as a helper when it needs to determine ping time to a host.
Act responsibly: do not use mrtg-ping-probe to ping devices without the owner's permission. Just imagine if 10,000 people decided to ping
your hosts! mrtg-ping-probe is meant to be used within your network to get round trip time performance figures for your network.
OPTIONS
To use mrtg-ping-probe you need to configure MRTG to call it from within the definition of a target host. This is done in the MRTG config
file, which is usually /etc/mrtg.conf.
Here's an example snippet: change the target name and IP address to suit your needs.
Target[your.target.ping]: `/usr/bin/mrtg-ping-probe 123.456.789.123`
SetEnv[your.target.ping]: MRTG_INT_IP="123.456.789.123" MRTG_INT_DESCR="ping"
MaxBytes[your.target.ping]: 100
AbsMax[your.target.ping]: 200
Options[your.target.ping]: gauge, growright
YLegend[your.target.ping]: ping time (ms)
ShortLegend[your.target.ping]: ms
Legend1[your.target.ping]: Maximum Round Trip Time in ms
Legend2[your.target.ping]: Minimum Round Trip Time in ms
Legend3[your.target.ping]: Maximal 5 Minute Maximum Round Trip Time in ms
Legend4[your.target.ping]: Maximal 5 Minute Minimum Round Trip Time in ms
LegendI[your.target.ping]: Max:
LegendO[your.target.ping]: Min:
Pay close attention to the backticks in the first line which tell MRTG to execute the nominated external program. Note also that you need
to use the "gauge" option, since the results of subsequent ping probes are independant values and not an incrementing counter.
SEE ALSO mrtg(1).
The latest release of mrtg-ping-probe can be found on the web at http://pwo.de/projects/mrtg/
AUTHOR
This manual page was written by Jonathan Oxer <jon@debian.org>, for the Debian project (but may be used by others).
April 14, 2003 MRTG-PING-PROBE(1)