Sponsored Content
Full Discussion: IPC-using fork() in a loop
Top Forums Programming IPC-using fork() in a loop Post 302450023 by saman_glorious on Wednesday 1st of September 2010 09:45:29 AM
Old 09-01-2010
fflush(stdout) does not even help

Quote:
Originally Posted by dawwin
Try to add
Code:
fflush(stdout);

After each call of printf()
I did but again i get the same result, printf does not print anything and i don't know what happens to the childs...

[root@localhost Randomized Dissemination]# ./a.out
downloader peers randomly selected
parent exited..
 

10 More Discussions You Might Find Interesting

1. Programming

fork() and IPC

Hey all. I recently ported a multithreaded program from WinNT to LINUX using pthreads. Everything works fine, except that it turns out the drivers for the hardware I'm working with aren't thread safe. So, now I have to find a way to make this multi-process instead of multi-threaded. I just... (1 Reply)
Discussion started by: TelePlayer
1 Replies

2. Shell Programming and Scripting

Endless loop - Fork function failed?

I need a quick script that will serve as a sort of "real time monitor" for watching some log files. I am using Bourne shell in HP-UX 10.20. I have basically created a script that never ends, unless of course I manually terminate it. Here's the script (it's called qhistory): clear echo "REAL... (3 Replies)
Discussion started by: cdunavent
3 Replies

3. Programming

fork() in for loop

hello, Every time i use fork() in the for loop, my college network(which i work in) either gets slow or hangs up.Can any 1 explain why it is so? Of course there is no use of doing it though. But still i want to clear my doubt. Thanks (2 Replies)
Discussion started by: cyno
2 Replies

4. UNIX for Dummies Questions & Answers

Ipc

I have a parent that is passing data to child A and then child A has to process it and pass to child B. I am able to pass the data to child A but am not able to pass it to child B. Child B seems to only be receiving the last data instead of the whole data. I saw one example in a book but it uses... (1 Reply)
Discussion started by: scmay
1 Replies

5. UNIX for Dummies Questions & Answers

Ipc Details

hai, i am doing my masters degree in computers.please any one tell me about fork(),semaphores,mutex,messaging queues,messaging using pipes ,and msgget(),msgrecv() funtions in ipc programming . i have exam on that i have a book but in that they not given clearly. hope u will ... (2 Replies)
Discussion started by: G.Vishnuvardhan
2 Replies

6. Programming

[C] Problem with IPC

Hi! I'm trying to write this program: in my intentions it should get a message and send it to a second process (pid_upost), then to a third process (pid1, pid2, pid3, depending on the choice made when a new message is inserted). This program should write the message in a file (message1, message2 or... (1 Reply)
Discussion started by: Kaminski
1 Replies

7. Solaris

errors on Netra-440: "IPC Warning: ipc: tcp_protocol: bad magic number"

I was asked to look into a problem with a Sun Netra 440 in another department. On the server in question, the relevant 'uname -a' information is, "SunOS host1 5.9 Generic_118558-16 sun4u sparc SUNW,Netra-440". That information aside, while the other admin is logged into the ALOM, these errors are... (0 Replies)
Discussion started by: Borealis
0 Replies

8. Shell Programming and Scripting

Inifinite Loop on fork

I am trying to ping through a list of devices in parallel. When the code below is executed, I enter a infinite loop. I want to used the number of lines in the file as my boundry. I am a perl rookie and just cant see whats wrong. would appreciate help ... use Net::Ping; # $filename... (0 Replies)
Discussion started by: popeye
0 Replies

9. Programming

C Socket Client/Server Fork Loop

Hello people. I'm trying to do something like a search engine. Server runs in the background by using ./server & which has data from a textfile stored in an array. Client then runs by using ./client It will then prompt "Search for:" For example, if I searched for Products called Instant... (0 Replies)
Discussion started by: andylbh
0 Replies

10. HP-UX

IPC settings on HP-UX

Hi Experts, Need your help for checking te interprocess communications settings on HP-UX box. Using ipcs command I am able to view Message queue,semapohores etc, but from that output I m not able to understand how to determine if there is any issue with ipc settings and how to resolve that? (1 Reply)
Discussion started by: sai_2507
1 Replies
IO::Async::Process(3pm) 				User Contributed Perl Documentation				   IO::Async::Process(3pm)

NAME
"IO::Async::Process" - start and manage a child process SYNOPSIS
use IO::Async::Process; use IO::Async::Loop; my $loop = IO::Async::Loop->new; my $process = IO::Async::Process->new( command => [ "tr", "a-z", "n-za-m" ], stdin => { from => "hello world ", }, stdout => { on_read => sub { my ( $stream, $buffref ) = @_; while( $$buffref =~ s/^(.*) // ) { print "Rot13 of 'hello world' is '$1' "; } return 0; }, }, on_finish => sub { $loop->stop; }, ); $loop->add( $process ); $loop->run; DESCRIPTION
This subclass of IO::Async::Notifier starts a child process, and invokes a callback when it exits. The child process can either execute a given block of code (via fork(2)), or a command. EVENTS
The following events are invoked, either using subclass methods or CODE references in parameters: on_finish $exitcode Invoked after the process has exited by normal means (i.e. an exit(2) syscall from a process, or "return"ing from the code block), and has closed all its file descriptors. on_exception $exception, $errno, $exitcode Invoked when the process exits by an exception from "code", or by failing to exec(2) the given command. $errno will be a dualvar, containing both number and string values. Note that this has a different name and a different argument order from "Loop->open_child"'s "on_error". If this is not provided and the process exits with an exception, then "on_finish" is invoked instead, being passed just the exit code. CONSTRUCTOR
$process = IO::Async::Process->new( %args ) Constructs a new "IO::Async::Process" object and returns it. Once constructed, the "Process" will need to be added to the "Loop" before the child process is started. PARAMETERS
The following named parameters may be passed to "new" or "configure": on_finish => CODE on_exception => CODE CODE reference for the event handlers. Once the "on_finish" continuation has been invoked, the "IO::Async::Process" object is removed from the containing "IO::Async::Loop" object. The following parameters may be passed to "new", or to "configure" before the process has been started (i.e. before it has been added to the "Loop"). Once the process is running these cannot be changed. command => ARRAY or STRING Either a reference to an array containing the command and its arguments, or a plain string containing the command. This value is passed into perl's exec(2) function. code => CODE A block of code to execute in the child process. It will be called in scalar context inside an "eval" block. setup => ARRAY Optional reference to an array to pass to the underlying "Loop" "spawn_child" method. fdn => HASH A hash describing how to set up file descriptor n. The hash may contain the following keys: via => STRING Configures how this file descriptor will be configured for the child process. Must be given one of the following mode names: pipe_read The child will be given the writing end of a pipe(2); the parent may read from the other. pipe_write The child will be given the reading end of a pipe(2); the parent may write to the other. Since an EOF condition of this kind of handle cannot reliably be detected, "on_finish" will not wait for this type of pipe to be closed. pipe_rdwr Only valid on the "stdio" filehandle. The child will be given the reading end of one pipe(2) on STDIN and the writing end of another on STDOUT. A single Stream object will be created in the parent configured for both filehandles. socketpair The child will be given one end of a socketpair(2); the parent will be given the other. The family of this socket may be given by the extra key called "family"; defaulting to "unix". The socktype of this socket may be given by the extra key called "socktype"; defaulting to "stream". If the type is not "SOCK_STREAM" then a IO::Async::Socket object will be constructed for the parent side of the handle, rather than "IO::Async::Stream". Once the filehandle is set up, the "fd" method (or its shortcuts of "stdin", "stdout" or "stderr") may be used to access the "IO::Async::Handle"-subclassed object wrapped around it. The value of this argument is implied by any of the following alternatives. on_read => CODE The child will be given the writing end of a pipe. The reading end will be wrapped by an "IO::Async::Stream" using this "on_read" callback function. into => SCALAR The child will be given the writing end of a pipe. The referenced scalar will be filled by data read from the child process. This data may not be available until the pipe has been closed by the child. from => STRING The child will be given the reading end of a pipe. The string given by the "from" parameter will be written to the child. When all of the data has been written the pipe will be closed. stdin => ... stdout => ... stderr => ... Shortcuts for "fd0", "fd1" and "fd2" respectively. stdio => ... Special filehandle to affect STDIN and STDOUT at the same time. This filehandle supports being configured for both reading and writing at the same time. METHODS
$pid = $process->pid Returns the process ID of the process, if it has been started, or "undef" if not. Its value is preserved after the process exits, so it may be inspected during the "on_finish" or "on_exception" events. $process->kill( $signal ) Sends a signal to the process $running = $process->is_running Returns true if the Process has been started, and has not yet finished. $exited = $process->is_exited Returns true if the Process has finished running, and finished due to normal exit(2). $status = $process->exitstatus If the process exited due to normal exit(2), returns the value that was passed to exit(2). Otherwise, returns "undef". $exception = $process->exception If the process exited due to an exception, returns the exception that was thrown. Otherwise, returns "undef". $errno = $process->errno If the process exited due to an exception, returns the numerical value of $! at the time the exception was thrown. Otherwise, returns "undef". $errstr = $process->errstr If the process exited due to an exception, returns the string value of $! at the time the exception was thrown. Otherwise, returns "undef". $stream = $process->fd( $fd ) Returns the IO::Async::Stream or IO::Async::Socket associated with the given FD number. This must have been set up by a "configure" argument prior to adding the "Process" object to the "Loop". The returned object have its read or write handle set to the other end of a pipe or socket connected to that FD number in the child process. Typically, this will be used to call the "write" method on, to write more data into the child, or to set an "on_read" handler to read data out of the child. The "on_closed" event for these streams must not be changed, or it will break the close detection used by the "Process" object and the "on_finish" event will not be invoked. $stream = $process->stdin $stream = $process->stdout $stream = $process->stderr $stream = $process->stdio Shortcuts for calling "fd" with 0, 1, 2 or "io" respectively, to obtain the IO::Async::Stream representing the standard input, output, error, or combined input/output streams of the child process. EXAMPLES
Capturing the STDOUT stream of a process By configuring the "stdout" filehandle of the process using the "into" key, data written by the process can be captured. my $stdout; my $process = IO::Async::Process->new( command => [ "writing-program", "arguments" ], stdout => { into => $stdout }, on_finish => sub { print "The process has finished, and wrote: "; print $stdout; } ); $loop->add( $process ); Note that until "on_finish" is invoked, no guarantees are made about how much of the data actually written by the process is yet in the $stdout scalar. See also the "run_child" method of IO::Async::Loop. To handle data more interactively as it arrives, the "on_read" key can instead be used, to provide a callback function to invoke whenever more data is available from the process. my $process = IO::Async::Process->new( command => [ "writing-program", "arguments" ], stdout => { on_read => sub { my ( $stream, $buffref ) = @_; while( $$buffref =~ s/^(.*) // ) { print "The process wrote a line: $1 "; } return 0; }, }, on_finish => sub { print "The process has finished "; } ); $loop->add( $process ); If the code to handle data read from the process isn't available yet when the object is constructed, it can be supplied later by using the "configure" method on the "stdout" filestream at some point before it gets added to the Loop. In this case, "stdin" should be configured using "pipe_read" in the "via" key. my $process = IO::Async::Process->new( command => [ "writing-program", "arguments" ], stdout => { via => "pipe_read" }, on_finish => sub { print "The process has finished "; } ); $process->stdout->configure( on_read => sub { my ( $stream, $buffref ) = @_; while( $$buffref =~ s/^(.*) // ) { print "The process wrote a line: $1 "; } return 0; }, ); $loop->add( $process ); Sending data to STDIN of a process By configuring the "stdin" filehandle of the process using the "from" key, data can be written into the "STDIN" stream of the process. my $process = IO::Async::Process->new( command => [ "reading-program", "arguments" ], stdin => { from => "Here is the data to send " }, on_finish => sub { print "The process has finished "; } ); $loop->add( $process ); The data in this scalar will be written until it is all consumed, then the handle will be closed. This may be useful if the program waits for EOF on "STDIN" before it exits. To have the ability to write more data into the process once it has started. the "write" method on the "stdin" stream can be used, when it is configured using the "pipe_write" value for "via": my $process = IO::Async::Process->new( command => [ "reading-program", "arguments" ], stdin => { via => "pipe_write" }, on_finish => sub { print "The process has finished "; } ); $loop->add( $process ); $process->stdin->write( "Here is some more data " ); AUTHOR
Paul Evans <leonerd@leonerd.org.uk> perl v5.14.2 2012-10-24 IO::Async::Process(3pm)
All times are GMT -4. The time now is 03:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy