system waiting for launched process AND forked processes

P

Pierre Morel

Hello,

We have written a small client-server program in c/socket. To launch the
server, we call the program which internally fork. The original process
returns immediately but the forked process stays alive and listen to
incoming socket connection.
It's all fine when running this from bash (we're on ubuntu) but when
using ruby (with either system, backtick or #x) it's blocking until both
the original process and the forked process terminate.

Is it what we should expect when calling system? If yes, how could we
work around that?

Thanks
 
R

Roger Pack

It's all fine when running this from bash (we're on ubuntu) but when
using ruby (with either system, backtick or #x) it's blocking until both
the original process and the forked process terminate.

Is it what we should expect when calling system? If yes, how could we
work around that?

Mine doesn't seem to do that.

rdp@li49-39:~$ cat spawn.rb
Process.fork {
puts 'in daemon'
puts Process.pid
sleep
}
puts 'terminating'

rdp@li49-39:~$ cat spawn2.rb
system("~/installs/ruby_trunk_installed/bin/ruby spawn.rb")
puts 'done'

rdp@li49-39:~$ ruby -v spawn2.rb
ruby 1.8.6 (2009-3-4 mbari 8B/0x8770 on patchlevel 287) [i686-linux]
terminating
done
in daemon
3199
rdp@li49-39:~$ ps -ef | grep 3199
rdp 3199 1 0 17:41 pts/0 00:00:00
/home/rdp/installs/ruby_trunk_installed/bin/ruby spawn.rb
rdp 3272 477 0 17:41 pts/0 00:00:00 grep 3199


(3199 is still alive).

Perhaps your other process.wait'ing on the first or something?

One thing that might help (in 1.9)
Process.daemon {
# something
}

or

Process.fork {
Thread.new { system("long running command")}
}

or what not.

GL.
-rp
 
R

Robert Klemme

We have written a small client-server program in c/socket. To launch the
server, we call the program which internally fork. The original process
returns immediately but the forked process stays alive and listen to
incoming socket connection.
It's all fine when running this from bash (we're on ubuntu) but when
using ruby (with either system, backtick or #x) it's blocking until both
the original process and the forked process terminate.

Is it what we should expect when calling system? If yes, how could we
work around that?

Hmmm, might be that you have an issue because your child's child is
attached to your ruby process once the starter process stops. There is
a whole range of other possible issues causing this which is hard to
sort out given the little information we have. Did you take proper
measures to demonize your child process after fork?

Kind regards

robert
 
R

Robert Klemme

Process.fork {
Thread.new { system("long running command")}
}

What do you create the thread for? Also exec is probably a better
choice in this case.

Kind regards

robert
 
P

Pierre Morel

Robert said:
Hmmm, might be that you have an issue because your child's child is
attached to your ruby process once the starter process stops. There is
a whole range of other possible issues causing this which is hard to
sort out given the little information we have. Did you take proper
measures to demonize your child process after fork?

Kind regards

robert

I didn't take any measure to daemonize the child... Now I have done it
(a call to setsid and few other things, I used the example at
http://www-theorie.physik.unizh.ch/~dpotter/howto/daemonize) and it's
working perfectly.

My mistake was assume that it would work from ruby if it was working
fine from the shell or even from another C++ program.

Thank you very much for your quick response.

Pierre
 

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

No members online now.

Forum statistics

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

Latest Threads

Top