Sponsored Content
Full Discussion: Ping and repeat ?
Top Forums Shell Programming and Scripting Ping and repeat ? Post 302661631 by sabercats on Monday 25th of June 2012 01:35:24 PM
Old 06-25-2012
Thanks Methyl, yes endless loop, it works. Thanks again.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Repeat Commands

On my system I use Escape "k" to go back in commands. I read on tutorials that it is ctrl p, but that does not work on my system. Anyone know what the command to go foward is? (6 Replies)
Discussion started by: dereckbc
6 Replies

2. Shell Programming and Scripting

to copy and repeat

Hi All, I have done some looking at other threads but haven't found quite what I am looking for. I am a newbie to scripting and haven't got to where I want to you but here is my basic question. I have a script to copy a file and send it to another file with a date and time stamp. What I want to... (4 Replies)
Discussion started by: falcondown01
4 Replies

3. UNIX for Dummies Questions & Answers

repeat each record n times

I have: aa01 aa02 aa03 aa04 ab01 ab02 ab03 ab04 I would like each record printed 5 times: aa01 aa01 aa01 aa01 aa01 aa02 aa02 (6 Replies)
Discussion started by: kenneth.mcbride
6 Replies

4. Shell Programming and Scripting

repeat character with printf

It's all in the subject. I try to figure out how to repeat a character a number of time with printf. For example to draw a line in a script output. Thks (13 Replies)
Discussion started by: ripat
13 Replies

5. Shell Programming and Scripting

Repeat using for loop

I have a file like this 2011-10-10 10:46:00,1-1-13-1-1,151510,ALCLA0A84D2C 2011-10-10 10:46:00,1-1-13-1-1,151520,65537 2011-10-10 10:46:00,1-1-13-1-1,151515,46932 2011-10-10 10:46:00,1-1-13-1-1,151521,32769 2011-10-10 10:46:00,1-1-13-1-1,151522,32769 2011-10-10... (4 Replies)
Discussion started by: LavanyaP
4 Replies

6. Shell Programming and Scripting

Animation Ping on Solaris Like Cisco Ping

Hi, I develop simple animation ping script on Solaris Platform. It is like Cisco ping. Examples and source code are below. bash-3.00$ gokcell 152.155.180.8 30 Sending 30 Ping Packets to 152.155.180.8 !!!!!!!!!!!!!.!!!!!!!!!!!!!!!. % 93.33 success... % 6.66 packet loss...... (1 Reply)
Discussion started by: gokcell
1 Replies

7. Shell Programming and Scripting

How to get reason for ping failure using perls Net::Ping->new("icmp");?

Hi I am using perl to ping a list of nodes - with script below : $p = Net::Ping->new("icmp"); if ($p->ping($host,1)){ print "$host is alive.\n"; } else { print "$host is unreacheable.\n"; } $p->close();... (4 Replies)
Discussion started by: tavanagh
4 Replies

8. Shell Programming and Scripting

Repeat for different variable

Hey, I've created following script: var1=test1 setA=testA if ... touch $setA/$var1 ... fi I would like now the repeat the command touch (in this example) for different variables. So below, the varX should run 3 times (var1, var2, var4). Var3 is skipped in this example... (4 Replies)
Discussion started by: brononius
4 Replies

9. Programming

Java: Repeat a command

I came across a site to learn java and they give you practice problems to do. I was wondering if anyone can help me with this since I am totally new to Java. Here is the first problem: Write a program that will read in a name from the command line and write it out 100 times. Thank you for any... (10 Replies)
Discussion started by: totoro125
10 Replies

10. Programming

Ping test sends mail when ping fails

help with bash script! im am working on this script to make sure my server will stay online, so i made this script.. HOSTS="192.168.138.155" COUNT=4 pingtest(){ for myhost in "$@" do ping -c "$COUNT" "$myhost" &&return 1 done return 0 } if pingtest $HOSTS #100% failed... (4 Replies)
Discussion started by: mort3924
4 Replies
uucico(8)						      System Manager's Manual							 uucico(8)

NAME
uucico - UUCP file transfer daemon SYNOPSIS
uucico [ options ] DESCRIPTION
The uucico daemon processes file transfer requests queued by uucp (1) and uux (1). It is started when uucp or uux is run (unless they are given the -r option). It is also typically started periodically using entries in the crontab table(s). When invoked with -r1, --master, -s, --system, or -S, the daemon will place a call to a remote system, running in master mode. Otherwise the daemon will start in slave mode, accepting a call from a remote system. Typically a special login name will be set up for UUCP which automatically invokes uucico when a call is made. When uucico terminates, it invokes the uuxqt (8) daemon, unless the -q or --nouuxqt option is given; uuxqt (8) executes any work orders created by uux (1) on a remote system, and any work orders created locally which have received remote files for which they were waiting. If a call fails, uucico will normally refuse to retry the call until a certain (configurable) amount of time has passed. This may be over- riden by the -f, --force, or -S option. The -l, --prompt, -e, or --loop options may be used to force uucico to produce its own prompts of "login: " and "Password:". When another daemon calls in, it will see these prompts and log in as usual. The login name and password will normally be checked against a separate list kept specially for uucico rather than the /etc/passwd file; it is possible on some systems to direct uucico to use the /etc/passwd file. The -l or --prompt option will prompt once and then exit; in this mode the UUCP administrator or the superuser may use the -u or --login option to force a login name, in which case uucico will not prompt for one. The -e or --loop option will prompt again after the first session is over; in this mode uucico will permanently control a port. If uucico receives a SIGQUIT, SIGTERM or SIGPIPE signal, it will cleanly abort any current conversation with a remote system and exit. If it receives a SIGHUP signal it will abort any current conversation, but will continue to place calls to (if invoked with -r1 or --master) and accept calls from (if invoked with -e or --loop) other systems. If it receives a SIGINT signal it will finish the current conversa- tion, but will not place or accept any more calls. OPTIONS
The following options may be given to uucico. -r1, --master Start in master mode (call out to a system); implied by -s, --system, or -S. If no system is specified, call any system for which work is waiting to be done. -r0, --slave Start in slave mode. This is the default. -s system, --system system Call the named system. -S system Call the named system, ignoring any required wait. This is equivalent to -s system -f. -f, --force Ignore any required wait for any systems to be called. -l, --prompt Prompt for login name and password using "login: " and "Password:". This allows uucico to be easily run from inetd (8). The login name and password are checked against the UUCP password file, which probably has no connection to the file /etc/passwd. The --login option may be used to force a login name, in which cause uucico will only prompt for a password. -p port, --port port Specify a port to call out on or to listen to. -e, --loop Enter endless loop of login/password prompts and slave mode daemon execution. The program will not stop by itself; you must use kill (1) to shut it down. -w, --wait After calling out (to a particular system when -s, --system, or -S is specifed, or to all systems which have work when just -r1 or --master is specifed), begin an endless loop as with --loop. -q, --nouuxqt Do not start the uuxqt (8) daemon when finished. -c, --quiet If no calls are permitted at this time, then don't make the call, but also do not put an error message in the log file and do not update the system status (as reported by uustat (1)). This can be convenient for automated polling scripts, which may want to simply attempt to call every system rather than worry about which particular systems may be called at the moment. This option also sup- presses the log message indicating that there is no work to be done. -C, --ifwork Only call the system named by -s, --system or -S if there is work for that system. -D, --nodetach Do not detach from the controlling terminal. Normally uucico detaches from the terminal before each call out to another system and before invoking uuxqt. This option prevents this. -u name, --login name Set the login name to use instead of that of the invoking user. This option may only be used by the UUCP administrator or the supe- ruser. If used with --prompt, this will cause uucico to prompt only for the password, not the login name. -z, --try-next If a call fails after the remote system is reached, try the next alternate rather than simply exiting. -i type, --stdin type Set the type of port to use when using standard input. The only support port type is TLI, and this is only available on machines which support the TLI networking interface. Specifying -iTLI causes uucico to use TLI calls to perform I/O. -x type, -X type, --debug type Turn on particular debugging types. The following types are recognized: abnormal, chat, handshake, uucp-proto, proto, port, config, spooldir, execute, incoming, outgoing. Multiple types may be given, separated by commas, and the --debug option may appear multiple times. A number may also be given, which will turn on that many types from the foregoing list; for example, --debug 2 is equivalent to --debug abnormal,chat. The debugging output is sent to the debugging file, which may be printed using uulog -D. -I file, --config file Set configuration file to use. This option may not be available, depending upon how uucico was compiled. -v, --version Report version information and exit. --help Print a help message and exit. SEE ALSO
kill(1), uucp(1), uux(1), uustat(1), uuxqt(8) AUTHOR
Ian Lance Taylor <ian@airs.com> Taylor UUCP 1.07 uucico(8)
All times are GMT -4. The time now is 01:28 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy