fork, trap and exec. Pickaxe typo?

N

Nate Murray

Hey All, I got this code straight from the PickAxe:

trap("CLD") {
pid = Process.wait
puts "Child pid #{pid}: terminated"
exit
}


exec("echo 'hello world'") if fork == nil

But it doesnt word!
The CLD trap'ped call never executes.


Another question... If I perform the exec 4 times the trap call back
should be called four times, right?

So this code:

trap("CLD") {
pid = Process.wait
puts "Child pid #{pid}: terminated"
exit
}

1.upto(4) do
exec("echo \"hello $HOSTNAME #{Process.pid}\n\" ; sleep 5") if
fork.nil?
end

Should call trap("CLD") four times, right?

Thanks for your help in advance.
 
N

Nate Murray

Another question, trap("CLD") should be called even with a non-zero
exit status, correct?

FYI, I am running under MacOSX 10.4

$ ruby --version
ruby 1.8.4 (2005-12-24) [i686-darwin8.6.1]
 
H

Hugh Sasse

Hey All, I got this code straight from the PickAxe:

But it doesnt word!
The CLD trap'ped call never executes.


Another question... If I perform the exec 4 times the trap call back
should be called four times, right?

So this code:

trap("CLD") {
pid = Process.wait
puts "Child pid #{pid}: terminated" # exit
}

1.upto(4) do
exec("echo \"hello $HOSTNAME #{Process.pid}\n\" ; sleep 5") if
fork.nil?
end

sleep 25
Should call trap("CLD") four times, right?

Thanks for your help in advance.

that should do the job. You didn't wait around for things to happen.
Hugh
 
N

Nate Murray

Yeah, but how do I wait for an unknown amount of time? It would seem
that this would do it:

trap("CLD") {
pid = Process.wait
puts "Child pid #{pid}: terminated"
}

1.upto(4) do
fork do
exec("sleep 3 && echo \"hello $HOSTNAME #{Process.pid}\n\"")
end
end

Process.waitall

But trap isnt always called on all the children.

Example output:

hello nate.cpo 4136

Child pid 4136: terminated
hello nate.cpo 4139

Child pid 4139: terminated
hello nate.cpo 4137

hello nate.cpo 4138

Child pid 4138: terminated

Notice that 4137 never called the trap callback even though
Process.waitall was called.
 
H

Hugh Sasse

Yeah, but how do I wait for an unknown amount of time? It would seem
that this would do it:

trap("CLD") {
pid = Process.wait
puts "Child pid #{pid}: terminated"
}

1.upto(4) do
fork do
exec("sleep 3 && echo \"hello $HOSTNAME #{Process.pid}\n\"")
end
end

Process.waitall

puts Process.waitall

=begin ri_output
------------------------------------------------------- Process::waitall
Process.waitall => [ [pid1,status1], ...]
------------------------------------------------------------------------
Waits for all children, returning an array of _pid_/_status_ pairs
(where _status_ is a +Process::Status+ object).
[...]
=end

# So while I'm not sure what's happening to the missing signal
# you should be able to see that all the processes have finished.
But trap isnt always called on all the children.
Example output:
[...]
Notice that 4137 never called the trap callback even though
Process.waitall was called.
Hugh
 
N

Nate Murray

This is so strange. I feel that I am really missing something here.

Here is my updated code, but the output is odd:

require 'pp'

trap("CLD") {
pid = Process.wait
puts "Child pid #{pid}: terminated"
}

1.upto(4) do
fork do
exec("sleep 3 && echo \"hello $HOSTNAME #{Process.pid}\n\"")
end
end

pp Process.waitall

== output:

hello nate.cpo 4655

Child pid 4655: terminated
hello nate.cpo 4660

hello nate.cpo 4657

hello nate.cpo 4659

Child pid 4660: terminated
[[4659, #<Process::Status: pid=4659,exited(0)>],
[4657, #<Process::Status: pid=4657,exited(0)>]]


The processes that are trapped call the callback and never end up in
Process.waitall. And those in Process.waitall never send the SIGCLD.

I think I need to do more research on this...

Hugh said:
Yeah, but how do I wait for an unknown amount of time? It would seem
that this would do it:

trap("CLD") {
pid = Process.wait
puts "Child pid #{pid}: terminated"
}

1.upto(4) do
fork do
exec("sleep 3 && echo \"hello $HOSTNAME #{Process.pid}\n\"")
end
end

Process.waitall

puts Process.waitall

=begin ri_output
------------------------------------------------------- Process::waitall
Process.waitall => [ [pid1,status1], ...]
------------------------------------------------------------------------
Waits for all children, returning an array of _pid_/_status_ pairs
(where _status_ is a +Process::Status+ object).
[...]
=end

# So while I'm not sure what's happening to the missing signal
# you should be able to see that all the processes have finished.
But trap isnt always called on all the children.
Example output:
[...]
Notice that 4137 never called the trap callback even though
Process.waitall was called.
Hugh
 
M

Morton Goldberg

This is so strange. I feel that I am really missing something here.

Here is my updated code, but the output is odd:

require 'pp'

trap("CLD") {
pid = Process.wait

I think this causes a conflict with Process.waitall below. I don't
understand why you're doing this and a waitall. One thing seems
clear: any child process whose exit is caught here won't be caught by
the waitall below.
puts "Child pid #{pid}: terminated"
}

1.upto(4) do
fork do
exec("sleep 3 && echo \"hello $HOSTNAME #{Process.pid}\n\"")
end
end

pp Process.waitall

The following code and output may give you some ideas about what is
happening.

<code>
DEBUG = []

trap("CLD") {
pid = Process.wait
DEBUG << "Child pid #{pid} terminated"
}

begin
4.times do
if fork.nil?
exec(%{echo "hello from child #{Process.pid}"})
else
sleep 1
end
end
ensure
DEBUG.each { |s| puts s }
end
</code>

<results>
RubyMate r5712 running Ruby v1.8.2 (/usr/bin/ruby)
hello from child 1743
hello from child 1744
hello from child 1745
hello from child 1746
Child pid 1743 terminated
Child pid 1744 terminated
Child pid 1745 terminated
Child pid 1746 terminated
</results>

Regards, Morton
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

Forum statistics

Threads
473,744
Messages
2,569,482
Members
44,901
Latest member
Noble71S45

Latest Threads

Top