basically, the daemon hangs right at the start of the request. My very first
use IO::File; open LOG, ">>log.out" or die "opening log.out: $!\n"; LOG->autoflush(1); printf LOG "PROC $$: %d %s run starts %s\n", time, __FILE__, scalar(localtime);
for the second request (remember, it is sent while the first program is running) does NOT APPEAR UNTIL THE FIRST REQUEST HAS FINISHED!!!!
This means that activation of the very function, 'go' does not start until monster has finished running...does this make sense to anyone?
it seems like the fork is not done completely or something, so though the 'return' happens easily after the first time, 'go' is still waiting for the fork to finish....
any ideas?
thanks
Sam
In reply to Re: Re: It works, and then it doesn't...connecting to a daemon over the net
by seaver
in thread It works, and then it doesn't...connecting to a daemon over the net
by seaver
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |