[lnkForumImage]
TotalShareware - Download Free Software
Confronta i prezzi di migliaia di prodotti.
Asp Forum
 Home | Login | Register | Search 


 

Forums >

comp.lang.ruby

Thread + fork warning

Ariff Abdullah

10/8/2003 3:01:00 AM

# ruby -e 'a = Thread.new { fork {} }; a.join'
-e:1: warning: fork terminates thread at -e:1
# ruby -v
ruby 1.8.0 (2003-10-05) [i386-freebsd4]

is this intentional?

--

Ariff Abdullah
MyBSD
http://www.My... (IPv4)
http://staff.My... (IPv6/IPv4)
http://tomoyo.My... (IPv6/IPv4)
4 Answers

Bedo Sandor

10/15/2003 10:26:00 AM

0

On Wed, Oct 08, 2003 at 12:00:50PM +0900, Ariff Abdullah wrote:
> # ruby -e 'a = Thread.new { fork {} }; a.join'
> -e:1: warning: fork terminates thread at -e:1
> # ruby -v
> ruby 1.8.0 (2003-10-05) [i386-freebsd4]
>
> is this intentional?


Hello!

I don't know, but I have the same warning, if I make a
fork{} in the main thread, and there is one or more
other running thread.

% vi thread.rb
1.: #!/usr/bin/ruby -w
2.:
3.: def forkAndWaitInThread
4.: Kernel.fork {
5.: Kernel.exec("sleep 5")
6.: }
7.: Thread.new {
8.: Process.wait
9.: }
10.: end
11.:
12.: 2.times { forkAndWaitInThread }
13.:
14.: Thread.list.each { |t| t.join unless t == Thread.current }
15.:

% chmod +x thread.rb ; ./thread.rb
./thread.rb:4: warning: fork terminates thread at ./thread.rb:8

Seems to work as I expected, but warnings make me misgiving.
Could somebody explain me the reasons? Am I doing wrong
if I leave out of consideration this warning? What is
the correct/usual method to execute processes in background?

% ruby -v
ruby 1.8.0 (2003-10-05) [i386-linux]
...from Debian/sid package

--
bSanyI

matz

10/15/2003 2:17:00 PM

0

Hi,

In message "Re: Thread + fork warning"
on 03/10/15, Bedo Sandor <bsanyi@sunserv.kfki.hu> writes:

|% chmod +x thread.rb ; ./thread.rb
|./thread.rb:4: warning: fork terminates thread at ./thread.rb:8
|
|Seems to work as I expected, but warnings make me misgiving.
|Could somebody explain me the reasons? Am I doing wrong
|if I leave out of consideration this warning? What is
|the correct/usual method to execute processes in background?

When you fork, all other threads are terminated in the child process.
The simplest solution is not mixing fork and threads, for example, use
system instead of fork+exec.

matz.

Bedo Sandor

10/17/2003 7:47:00 AM

0

On Wed, Oct 15, 2003 at 11:16:43PM +0900, Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Re: Thread + fork warning"
> on 03/10/15, Bedo Sandor <bsanyi@sunserv.kfki.hu> writes:
>
> |% chmod +x thread.rb ; ./thread.rb
> |./thread.rb:4: warning: fork terminates thread at ./thread.rb:8
> |
>
> When you fork, all other threads are terminated in the child process.

But only in the child process!? This is exactly what I
want! In my program the main process forks&execs other
processes, and in the main process creates a thread to
wait/waitpid the forked process, and log the time and
the pid when done. I don't need thread in the Ruby
interpreter in the child processes, they only execs an
external command. I think the correct behavior would
be in a threaded Ruby program that fork does not harm
threads in the main process, but starts an other
interpreter without threads running only with the
commands in the block passed to the Kernel.fork.


> The simplest solution is not mixing fork and threads, for example, use
> system instead of fork+exec.

I have two problems with system():

- I can't log the termination of the spawned
process.

- Don't know if this is a correct way to start
background processes: (I need background processes,
so I have to continue the main Ruby program!)

def startInBg(unixCommand)
system(unixCommand.to_s + "&")
end
...
startInBg 'zcat /var/log/messages*.gz | logClassifier'

It works, and there's no warnin, but what
do You think about +"&" ?

--
bSanyI

matz

10/17/2003 3:25:00 PM

0

Hi,

In message "Re: Thread + fork warning"
on 03/10/17, Bedo Sandor <bsanyi@sunserv.kfki.hu> writes:

|- I can't log the termination of the spawned
| process.

How do you want to watch process? If you want to store logs into a
file, you can use shell redirect such as ">" etc.

If you want to get logs as stream output, you can use popen3 library.

|- Don't know if this is a correct way to start
| background processes: (I need background processes,
| so I have to continue the main Ruby program!)
|
| def startInBg(unixCommand)
| system(unixCommand.to_s + "&")
| end
| ...
| startInBg 'zcat /var/log/messages*.gz | logClassifier'
|
| It works, and there's no warnin, but what
| do You think about +"&" ?

+"&" should work OK; you are working on Unix.

matz.