Hi ,
I would like to automate a script to ping all the unix servers perodically thru
cronjob.
Is there any script out there? If so Please give me.
Thanks in advance. (2 Replies)
Hi,
I am running a shell script from a central server to multiple remote servers using the following code:
application_check()
{
# Linux/UNIX box with ssh key based login
SERVERS=`cat /tmp/server-details`
# SSH User name
USR="user"
# create new file
> /tmp/abc.log
# connect... (2 Replies)
Hi
We have some 300 servers in the Data center and some of them are running with AIX and some of them are running with Solaris.
I need a script which can be run in one of the server and that script should ping the hostname of all the 300 servers.
Also the script should notify if any server is... (9 Replies)
Hello Everyone,
How do we run vi/vim encrypted shell script without decryption on multiple servers. It is a simple bash script and vim -nx <filename> has been used to encrypt with desired password. Now I have few errors, the syntax is absolutely fine as I have run that script multiple times on... (0 Replies)
Hello,
I have access to several linux servers (mostly centos based) located in a DC in another country.
from day to day I need to login to each of them to do some work (they dont have gui/window manager installed, I work only from console), or even to just do a check like df -h for disc usage.... (3 Replies)
Hey, It's me again! Still trying to learn to become a better scripter on the job :)
New challenge for assistance, if anyone cares to help, and its two parted! First part, I wanted to create a script at work that would ping a server that was supplied in an argument, then a count (amount of times)... (5 Replies)
Hi Friends,
I have experience in redhat/ Ubuntu OS, but I am very new to solaries os.
my servers OS is Oracle Solaris 10 8/11 s10x_u10wos_17b X86.
I have a file contains 200 servers IPs one by one.
now I want a script to chaeck which IPs are pinging, not pingning.
I... (8 Replies)
Hi Team,
Need shell script to Telnet multiple node , Ping some IP and print output like pass or fail.
Need this script to check reachability of multiple nodes at same time.
Help me.
I use this but not working...
Eg.
in this script i need to telnet... (4 Replies)
Shell script for connecting multiple servers and then copying 30 days old files from those server .
HI ,
I have 6 multiple servers
pla1,pla2,pla3,pla4,pla5,pla6
1. These six servers have common shared mount point /var/share
2. Running script from /var/share to connect these servers.I... (1 Reply)
Discussion started by: rcroyal88
1 Replies
LEARN ABOUT XFREE86
nisping
nisping(1M)nisping(1M)NAME
nisping - send ping to NIS+ servers
SYNOPSIS
/usr/lib/nis/nisping [-uf] [-H hostname] [-r | directory]
/usr/lib/nis/nisping -C [-a] [-H hostname] [directory]
In the first line, the nisping command sends a ``ping'' to all replicas of an NIS+ directory. Once a replica receives a ping, it will
check with the master server for the directory to get updates. Prior to pinging the replicas, this command attempts to determine the last
update "seen" by a replica and the last update logged by the master. If these two timestamps are the same, the ping is not sent. The -f
(force) option will override this feature.
Under normal circumstances, NIS+ replica servers get the new information from the master NIS+ server within a short time. Therefore, there
should not be any need to use nisping.
In the second line, the nisping -C command sends a checkpoint request to the servers. If no directory is specified, the home domain, as
returned by nisdefaults(1), is checkpointed. If all directories, served by a given server, have to be checkpointed, then use the -a option.
On receiving a checkpoint request, the servers would commit all the updates for the given directory from the table log files to the data-
base files. This command, if sent to the master server, will also send updates to the replicas if they are out of date. This option is
needed because the database log files for NIS+ are not automatically checkpointed. nisping should be used at frequent intervals (such as
once a day) to checkpoint the NIS+ database log files. This command can be added to the crontab(1) file. If the database log files are not
checkpointed, their sizes will continue to grow.
If the server specified by the -H option does not serve the directory, then no ping is sent.
Per-server and per-directory access restrictions may apply; see nisopaccess(1). nisping uses NIS_CPTIME and NIS_PING (resync (ping) of
replicas), or NIS_CHECKPOINT (for checkpoint). Since the NIS_PING operation does not return a status, the nisping command is typically
unable to indicate success or failure for resyncs.
-a Checkpoint all directories on the server.
-C Send a request to checkpoint, rather than a ping, to each server. The servers schedule to commit all the transactions to
stable storage.
-H hostname Only the host hostname is sent the ping, checked for an update time, or checkpointed.
-f Force a ping, even though the timestamps indicate there is no reason to do so. This option is useful for debugging.
-r This option can be used to update or get status about the root object from the root servers, especially when new root
replicas are added or deleted from the list.
If used without -u option, -r will send a ping request to the servers serving the root domain. When the replicas receive a
ping, they will update their root object if needed.
The -r option can be used with all other options except with the -C option; the root object need not be checkpointed.
-u Display the time of the last update; no servers are sent a ping.
-1 No servers were contacted, or the server specified by the -H switch could not be contacted.
0 Success.
1 Some, but not all, servers were successfully contacted.
Example 1: Using nisping
This example pings all replicas of the default domain:
example% nisping
Note that this example will not ping the org_dir and groups_dir subdirectories within this domain.
This example pings the server example which is a replica of the org_dir.foo.com. directory:
example% nisping -H example org_dir.foo.com.
This example checkpoints all servers of the org_dir.bar.com. directory.
example% nisping -C org_dir.bar.com.
NIS_PATH If this variable is set, and the NIS+ directory name is not fully qualified, each directory specified will be
searched until the directory is found.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnisu |
+-----------------------------+-----------------------------+
crontab(1), nisdefaults(1), nisopaccess(1), nislog(1M), nisfiles(4), attributes(5)
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are
available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html.
12 Dec 2001 nisping(1M)