Another crude way to deal with this would be slowing down the input. I don't think Windows has the very basic functionality needed to do this, but with busybox-w32 you can do:
This will flatten any whitespace in your input file. I'm not sure how to avoid that without using an external script file. Does it matter for your input?
Quote:
Originally Posted by zaainabbas
I have tested it with several commands. Plink send them one by one and as i already mentioned that when i exit the configuration mode, it resumes normal operation. The problem only comes when router goes into configuration mode.
plink does not wait. It is a very primitive non-terminal with no such feature. It sends as fast as the socket will allow it.
The usual problem with scripting interactive interfaces is periods of time when anything you type will be ignored. This seldom matters to a human, but a program which will happily send the entire buffer while the router's occupied examining its own navel.
Last edited by Corona688; 08-02-2017 at 12:43 PM..
When running top, I notice a bit more I/O wait time than usual. Is there a tool or piece of software out there that can me help evaluate the performance of these operations on my machine? Thanks! (5 Replies)
:cool:
I need to execute a shell script to do the following:
cat a file
run two back ground processes using the first two values from the file
wait till those background processes finish
run two more background processes using the next two values from the file
wait till those background... (1 Reply)
I have a one line bat script run off a XP machine that tar's and compresses some files from a Sol 8 box. It goes something like this (a bit simplified)....
plink -pw <passwd> user@host "tar -cvf - -C / tmp/a_file | compress " > a_file.tar.Z
So this works....and it's worked many times. But now... (3 Replies)
Did not use 'wait' yet.
How I understand by now the wait works only for child processes, started background.
Is there any other way to watch completion of any, not related process (at least, a process, owned by the same user?)
I need to start a background process, witch will be waiting... (2 Replies)
Hello, I have been trying to figure out why the wait isnt waiting for the sleep process to complete till now and have found out that since sleep runs as different process and not a child process the wait isnt waiting.
script:
cat test|while read i
do
echo $i
sleep 30 &
done
wait
ps... (4 Replies)
Hello,
On a HP-UX 10.20 server I've executed something similar to this command:
# echo 'selall;info;wait;infolog;view;done' | /usr/sbin/cstm
But it returns sometype of "argument list too long" error.
I suppose there is a way to fix it by using xargs but I can't figure it out.
Any... (7 Replies)
Hi,
I am facing a strange issue,
when i call a script from my while loop in background it doesnt go in background, despite the wait i put below the whil loop it goes forward even before the process put in background is completed.
cat abc.txt | while read -u4 line
do
#if line contains #... (2 Replies)
Iam having a script which is used to load users and dumpfile in any given schema.Iam trying to autolog the script and have added two fucntion in it.
function init_stdout_redirect {
OUT_LOG=$1
OUT_PIPE=$(mktemp -u)
# Create the output pipe
mkfifo $OUT_PIPE
# Save stdout and... (15 Replies)
hi,
Can anybody help me about the odd output file yielded by the following command:
plink --noweb --allow-no-sex --bfile input_file --assoc --adjust --out output_file
In fact, I'd like to perform a simple Bonferroni basic association test, and I obtains the following output file (extract... (1 Reply)
Discussion started by: boro82
1 Replies
LEARN ABOUT SUNOS
in.rdisc
in.rdisc(1M) System Administration Commands in.rdisc(1M)NAME
in.rdisc, rdisc - network router discovery daemon
SYNOPSIS
/usr/sbin/in.rdisc [-a] [-f] [-s] [send-address] [receive-address]
/usr/sbin/in.rdisc -r [-p preference] [-T interval] [send-address] [receive-address]
DESCRIPTION
in.rdisc remains part of the software distribution of the Solaris Operating Environment. It is, however, not used by default. in.routed(1M)
includes the functionality provided by in.rdisc. See routeadm(1M) for details of how to specify the IPV4 routing daemon.
in.rdisc implements the ICMP router discovery protocol. The first form of the command is used on hosts and the second form is used on
routers.
in.rdisc can be invoked in either the first form (host mode) or second form (router mode).
On a host, in.rdisc populates the network routing tables with default routes. On a router, advertises the router to all the hosts.
Host (First Form)
On a host, in.rdisc listens on the ALL_HOSTS (224.0.0.1) multicast address for ROUTER_ADVERTISE messages from routers. The received mes-
sages are handled by first ignoring those listed router addresses with which the host does not share a network. Among the remaining
addresses, the ones with the highest preference are selected as default routers and a default route is entered in the kernel routing table
for each one of them.
Optionally, in.rdisc can avoid waiting for routers to announce themselves by sending out a few ROUTER_SOLICITATION messages to the
ALL_ROUTERS (224.0.0.2) multicast address when it is started.
A timer is associated with each router address. The address will no longer be considered for inclusion in the routing tables if the timer
expires before a new advertise message is received from the router. The address will also be excluded from consideration if the host
receives an advertise message with the preference being maximally negative or with a lifetime of zero.
Router (Second Form)
When in.rdisc is started on a router, it uses the SIOCGIFCONF ioctl(2) to find the interfaces configured into the system and it starts lis-
tening on the ALL_ROUTERS multicast address on all the interfaces that support multicast. It sends out advertise messages to the ALL_HOSTS
multicast address advertising all its IP addresses. A few initial advertise messages are sent out during the first 30 seconds and after
that it will transmit advertise messages approximately every 600 seconds.
When in.rdisc receives a solicitation message, it sends an advertise message to the host that sent the solicitation message.
When in.rdisc is terminated by a signal, it sends out an advertise message with the preference being maximally negative.
OPTIONS -a Accept all routers independent of the preference they have in their advertise messages. Normally, in.rdisc only accepts
(and enters in the kernel routing tables) the router or routers with the highest preference.
-f Run in.rdisc forever even if no routers are found. Normally, in.rdisc gives up if it has not received any advertise message
after soliciting three times, in which case it exits with a non-zero exit code. If -f is not specified in the first form
then -s must be specified.
-r Act as a router, rather than a host.
-s Send three solicitation messages initially to quickly discover the routers when the system is booted. When -s is specified,
in.rdisc exits with a non-zero exit code if it can not find any routers. This can be overridden with the -f option.
-p preference Set the preference transmitted in the solicitation messages. The default is zero.
-T interval Set the interval between transmitting the advertise messages. The default time is 600 seconds.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWroute |
+-----------------------------+-----------------------------+
SEE ALSO in.routed(1M), routeadm(1M), ioctl(2), gateways(4), attributes(5), icmp(7P), inet(7P)
Deering, S.E., editor, ICMP Router Discovery Messages, RFC 1256, Network Information Center, SRI International, Menlo Park, California,
September 1991.
SunOS 5.10 5 Nov 2004 in.rdisc(1M)