I work for a small internet company, and sometimes its useful to ping a certain IP over an open amount of time. I wrote a simple script that asks what IP you'd like to ping, and then pings it and puts it into a text file so that you can save the results. What i'd like though, is to have an infinite loop that pings and puts it into a text file, and then, after a certain key is pressed, it stops that part of the script and continues on to the next part, that uses Grep, and filters out the pings so that you just get the time, and and the end part of the ping, where it tells you packet loss and such. This is what I have so far. I know it is likely completely wrong, I'm new to this, and this is what I have combining my script and what I think I want from googling how to use user input to end an infinite loop.
Last edited by Scrutinizer; 10-08-2013 at 01:27 PM..
Reason: code tags
I need a script that checks to see if ypserv is running, and if not it will restart yp.
I have a ypslave that is running Sol9, and the ypsrv daemon is dieing, I want to create a cron job that periodicly checks to see if it's running, and if it see's that it isn't, it will re-start the daemon (1 Reply)
Here is the script that i am trying to run. I get an error and i can't figure out what is the problem.
#!/bin/bash
echo "What is your name"
read NAME
if ; then
echo "My name is the same"
esle
echo "You have a nice name"
fi (11 Replies)
I am trying to print my script arguments, but i am stuck at the arrow pointed lines..please help
#!/bin/bash
echo "Number of arguments $#"
count=1
while
do
echo ${$count} <========================
count = $(expr $count +1) <==================
done (4 Replies)
I have a script that will check for integer line by line and if it encounter any blank space will echo it:
Below the script:
#!/bin/ksh
while read i
do
echo "Value is $i"
count=`expr substr "$i" 1 3`
echo $count
if &&
then
echo "Matched"
else
echo "Blank Space Found"
fi (3 Replies)
hi guys, i am a noob to shell scripting, and i would like to run a simple script, that could simply do the following: 1. SFTP to a remote server/path...and download the newest *.gz backup file on that server. (there are many *.gz files in that folder, i simply need the latest one) 2. locally... (1 Reply)
I have a file that contains these lines
User ID Username
-------- ----------
7738626,zrazak
7783535,jvincigu
7805567,ldrennan
7805583,mtsakama
I need to sort the names alphabetically
How can I sort the lines based on the user names ?
I would appreciate a quick reply anyone
... (1 Reply)
Hello all!
This is my first post and I'm very new to programming. I would like help creating a simple perl or bash script that I will be using in my work as a junior bioinformatician.
Essentially, I would like to take a tab-delimted or .csv text with 3 columns and write them to a "3D" matrix:
... (16 Replies)
Hi team,
I have two select statements and need to run them using SYSDBA user
select * from temp_temp_seg_usage;
select segment_name, tablespace_name, bytes/ (1024*1024) UsedMb from
dba_segments where segment_name='TEMP_TEMP_SEG_USAGE';
Need to run this using a shell script say named... (1 Reply)
Hi,
new to unix and scripting, and i'm trying to set up a simple "if" script to create a seperate flag file dependant on success.
So far i have the following ($5 is a variable passed to the script from the backup job)
if
then
touch /u03/backups/backup_ended.flag
else
touch... (13 Replies)
Discussion started by: richs24
13 Replies
LEARN ABOUT SUNOS
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)