so i'm running remote scripts using the nc command and it's working great.
from the monitoring server, i run this from the command line:
which results in the following when everything is fine:
when i do a echo $? on the monitoring server, it returns an exit code of 0.
however, even whenever the check fails with something other than a OK, I still get a exit code of 0. so that proves to me that the exit code of 0 that i'm seeing on the monitoring server is only reporting that the command ran successfully....from the monitoring server.
is there anyway i can pass the exit code of the script from the remote host, back to the monitoring server?
I'm receiving an exit code 64 in our batch scheduler (BMC product control-m) executing a PERL script on UX-HP. Can you tell me where I can find a list of exit codes and their meaning. I'm assuming the exit code is from the Unix operating system not PERL. (3 Replies)
I have a Unix Script that has several exit in the middle. each returning seperate
exit codes.
I have to catch all the exit's and perform an operation say "Mail the status code" before the actual code completes.
How can i do this in KSH ? (3 Replies)
HI All,
I have created a unix script which takes 2 parameters and using sftp tranfers files to remote location
following is the script
#!/bin/ksh
#
#
# Parameter 1 is the complete path of the destination server
# Parameter 2 is the complete path of the file which is to be FTP... (1 Reply)
I know that the exit codes in scripting "$*" will returns all the parameters/arguments passwd to the script.
But I also know that "$@" will also returns the same. What is the difference between those two ? (1 Reply)
Good Morning All..
I was wondering about getting exit codes of a command in a shell script. I'm trying to run uvscan (McAfee command line scanner) and I want to have the log file say why, if at all, the process failed/exited.
Something to the extent of
If ; then
echo "This is why it... (1 Reply)
Hello,
I need to ensure that SCP does not leave any partially transmitted files on the remote server due to transmission errors.
Can it be assumed that:
1) if SCP returns a success with Exit Code == 0, a complete local file has been copied in its entirety to the remote location?
2)... (1 Reply)
how do i/is there a way to return the exit code from the remote host?
echo $? from the local host only gives 0, if the rexec command itself executes successfully. But what if in the case of the remote command failiing? echo $? on the localhost still gives 0, but I'm interested in the exit code... (4 Replies)
I am trying to run this SH on Linux and getting error at IF condition.
I want to read the EXIT code and send the failure or success message.
Please help me on this. This worked when i was running on Solaris.
#!/bin/bash
$ORACLE_HOME/bin/sqlplus abc/xyz@qwe @/home/test.sql
if ;... (4 Replies)
Discussion started by: rlmadhav
4 Replies
LEARN ABOUT SUSE
dhcping
DHCPING(8) General Commands Manual DHCPING(8)NAME
dhcping - send a DHCP request to DHCP server to see if it's up and running
SYNOPSIS
dhcping [-v] [-q] [-i] [-r] -t maxwait -c client-IP-address -s server-IP-address -h client-hardware-address [-g gateway-IP-address]
DESCRIPTION
This command allows the system administrator to check if a remote DHCP server is still functioning.
Options are:
-v Verbose, print some information.
-i Use DHCPINFORM packets.
-r Use DHCPREQUEST packets (default behaviour).
-q Quiet, print nothing on the screen.
-t maxwait
Maximum time to wait for an answer from the server in seconds. Default is 3 seconds.
-c client-IP-address
Request this IP address. Note that this is also the IP address the answer will be sent to.
-s server-IP-address
Send the DHCP packet to this IP address.
-h client-hardware-address
Use this hardware-address in the DHCP request. It can be up to sixteen octets seperated by colons (i.e. 01:02:03:04)
-g gateway-IP-address
Use this IP address for the gateway IP address in the DHCP packet. This option is currently broken.
RETURN VALUES
If everything goes okay, it returns 0. If there went something wrong, it returns 1.
SETUP
This program should be installed setuid root or ran by root only. See SECURITY for more information.
On your DHCP server, add these lines to the dhcpd.conf:
host <your monitoring host FQDN> {
hardware ethernet <your monitor host mac address>;
fixed-address <your monitoring host IP address>;
}
Then try it:
$ dhcping -c your monitoring host IP address
-s your DHCP server IP address
-h your monitor host mac address
It will either respond with "no answer" or "Got answer from: your DHCP server IP address"
The DHCP server logfile will give:
DHCPREQUEST for 192.168.1.1 from 00:20:18:56:29:8f via ed0
DHCPACK on 192.168.1.1 to 00:20:18:56:29:8f via ed0
DHCPRELEASE of 192.168.1.1 from 00:20:18:56:29:8f via ed0 (found)
Running in DHCPINFORM mode with -i:
If you see "DHCPINFORM from 192.168.1.1 via xl0: not authoritative for subnet 192.168.1.0", you should add the authoritative statement to
the subnet, See dhcpd.conf(5) for details.
When running in very verbose mode, dhcping tries to dump all data of the send and received DHCP packets. It will first dump the packet in
hex-format, then decodes the header and finally the options.
HOW IT WORKS
The client either sends a DHCPREQUEST or DHCPINFORM packet to the server and waits for an answer. Then, if a DHCPREQUEST was send, it will
send a DHCPRELEASE back to the server.
SECURITY
This program is installed setuid root as it requires the privileges to bind itself to port 68 (bootpc). Root privileges are dropped as soon
as the program has bound itself to that port.
BUGS
Currently (this may, or may not, change in the future) the ISC DHCP daemon does not write leases with a fixed IP address in the
dhcpd.leases file.
DHCPINFORM packets can only be used on subnets the server is authori- tative for. If the monitoring script runs on a subnet the server
isn't authoritative for, it should use the DHCPREQUEST packets. I also experienced some problems with ISC DHCPD v2 servers, but that is
also in the README of it.
The -V option is still working, but shouldn't be used for debugging of the packets. Better use dhcpdump(8) for that, which is available on
my website. I wanted to remove it, but decided only to do it from the documentation, not from the code. Maybe I'll need it one day for
debugging.
AUTHOR
Edwin Groothuis, edwin@mavetju.org (http://www.mavetju.org)
SEE ALSO dhcpd(8), dhclient(8), dhcpd.conf(5), dhcpdump(8)Januari 27, 2002 Januari 27, 2002 DHCPING(8)