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
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