That shows the exit code of "true" and "false". As you can see, they both do nothing. One returns a passing exit code, while the other returns a failing exit code. The "while" function wants an argument. It will continue parsing code inside the loop until the argument fails.
This piece of code will open four xterm windows. It will only open four, because we set our variable 'i' to 0 and increment it once per loop iteration. When it reaches the value of four, the while condition fails, and the code block will no longer be executed.
So, because "true" does nothing successfully, if you had "while true" in that code block, it would continue and continue to open xterm windows until you ran out of physical resources, and the box could no longer function.
Because "false" does nothing unsuccessfully, if you had "while false" in that code block, it would not even initialize the loop, and immediately exit without opening a single xterm window.
Hi,
whenever I am giving a 'ls' command system is going into infinite loop displaying the current home directory.
There is no separate shell script/file with ls name anywhere in the system.
I am using Solaris 10.
Any help / guidance in solving this problem is highly appreciated.
... (3 Replies)
Hi guys, I'm having a problem getting my infinite loop to loop. It simply reads in the users choice form the menu, executes the corresponding case statement and quits instead of looping back to the main menu again. I have a feeling it might be something with my if then statements within the case... (2 Replies)
Production C code compiled without the dash-g option is running, and seems to be in an infinite loop. Is there a way to tell? Is there a diagnostic tool that will report what objects or what lines of code or even what functions are being executed?
Or is my best option to kill it with a dump?
... (5 Replies)
hi all,
this is how my scrip looks like
#!/bin/sh
bindir='/opt/apps/script/bin'
datadir='/opt/apps/script/data'
dir='/opt/apps/script'
while : ; do
ls -1rt /opt/apps/script/data/check.txt*|tail -1 > /dev/null 2>&1
if ;then
chmod +rwx $bindir/dummy2.sh
... (8 Replies)
I wanted to copy (not forward but copy) all incoming email to another address of mine. It worked, but now I encountered an infinite loop problem: When the second address doesn't like the content and bounces the message back, the bounce message will be sent back and forth.
So, what I have in... (1 Reply)
Hi All,
I need to run an infinite loop.
requirement below:
function1 --> creates a file file1
function2 ---> need to call if the file creates
i am running these both function via a script --> script.sh
i need to run the function1 first and if the file file1 creates then need to run the... (3 Replies)
1. The problem statement, all variables and given/known data:
My problem is an infinite loop when i press any other key other then Y or y in the while loop. what i want it to do is return to the normal script outside of it if pressing N or n or keep asking the same question if its any other... (4 Replies)
Hi, I was debating if I should put this in the dummies or scripts section, I apologize in advance if I chose poorly.
Fairly new to Unix and BASH scripting but I thought I made it fairly well given my limited understanding. However, the output indicates that it's looping and I'm ending up with a... (5 Replies)
Im unable to stop the below infinite loop (bash script). Can someone tell me why this isnt responding to signals eg: ctrl+c (SIGINT) or ctrl+z
c=0
test_loop() {
c=$(($c+1))
echo "count value is : $c "
sleep 1
test_loop
}
Im using: SunOS 5.10
PS: If run this as... (13 Replies)
I have a script script.shwhich is scheduled to run at 11 AM everyday.
# script.sh Code:
./scb_script.sh &
unfortunately scb_script.sh is running today in infinite loop as respective files are not available.
My question, when script.sh starts running tomorrow, will the old process be... (1 Reply)
Discussion started by: JSKOBS
1 Replies
LEARN ABOUT DEBIAN
io::async::routine
IO::Async::Routine(3pm) User Contributed Perl Documentation IO::Async::Routine(3pm)NAME
"IO::Async::Routine" - execute code in an independent sub-process
SYNOPSIS
use IO::Async::Routine;
use IO::Async::Channel;
use IO::Async::Loop;
my $loop = IO::Async::Loop->new;
my $nums_ch = IO::Async::Channel->new;
my $ret_ch = IO::Async::Channel->new;
my $routine = IO::Async::Routine->new(
channels_in => [ $nums_ch ],
channels_out => [ $ret_ch ],
code => sub {
my @nums = @{ $nums_ch->recv };
my $ret = 0; $ret += $_ for @nums;
# Can only send references
$ret_ch->send( $ret );
},
on_finish => sub {
say "The routine aborted early - $_[-1]";
$loop->stop;
},
);
$loop->add( $routine );
$nums_ch->send( [ 10, 20, 30 ] );
$ret_ch->recv(
on_recv => sub {
my ( $ch, $totalref ) = @_;
say "The total of 10, 20, 30 is: $$totalref";
$loop->stop;
}
);
$loop->run;
DESCRIPTION
This subclass of IO::Async::Process contains a body of code and executes it in a sub-process, allowing it to act independently of the main
program. Once set up, all communication with the code happens by values passed into or out of the Routine via IO::Async::Channel objects.
Because the code running inside the Routine runs within its own process, it is isolated from the rest of the program, in terms of memory,
CPU time, and other resources, and perhaps most importantly in terms of control flow. The code contained within the Routine is free to make
blocking calls without stalling the rest of the program. This makes it useful for using existing code which has no option not to block
within an "IO::Async"-based program.
To create asynchronous wrappers of functions that return a value based only on their arguments, and do not generally maintain state within
the process it may be more convenient to use an IO::Async::Function instead, which uses an "IO::Async::Routine" to contain the body of the
function and manages the Channels itself.
PARAMETERS
The following named parameters may be passed to "new" or "configure":
channels_in => ARRAY of IO::Async::Channel
ARRAY reference of "IO::Async::Channel" objects to set up for passing values in to the Routine.
channels_out => ARRAY of IO::Async::Channel
ARRAY reference of "IO::Async::Channel" objects to set up for passing values out of the Routine.
code => CODE
CODE reference to the body of the Routine, to execute once the channels are set up.
METHODS
This class provides no additional methods, other than those provided by IO::Async::Process.
AUTHOR
Paul Evans <leonerd@leonerd.org.uk>
perl v5.14.2 2012-10-24 IO::Async::Routine(3pm)