Please reply to the list, rather than just me. There's a much better chance
someone else might be able to help. If this is a bug in mon we would like
as many people to see it as possible so that it can get fixed more quickly.
If you could give us your config file and fake program you're using that
might give us more to go on. The only thing I can possibly think of is some
conflict between STDOUT and STDERR from the parent and child processes
causing weirdness, see 'perldoc -q background' for details:
STDIN, STDOUT, and STDERR are shared
Both the main process and the backgrounded one
(the "child" process) share the same STDIN,
STDOUT and STDERR filehandles. If both try to
access them at once, strange things can
happen.
I tried setting up a simple alert that invoked another shell script with
0.99.2, and it didn't hang mon when it ran.
locktest.alert:
#!/usr/bin/perl
system("/home/andrewr/bin/test.sh&");
exit 0;
/home/andrewr/bin/test.sh:
#!/bin/sh
echo "This is a really simple script which does something"
ls /
sleep 90
At 04:04 PM 10/30/01 -0500, you wrote:
>Andrew, thanks for answering. The fake program is a gratuitous arp program.
>Fake itself is not hanging is mon the one that hangs. fake starts and it
>stays up and works but mon is waiting for the alert to finish (or at least
>it looks that way). Just last week, I did the implementation of mon using
>the 0.38.16 version and everything worked. This week I was going to do a
>DEMO (tomorrow) and I (because I am masochist) decided to convert
>everything to the new version. I guess I will not demo this portion. As
>soon as the alert happens and I submit the background command, if you try
>to issue a monshow it hangs and so the mon.cgi. Everyone is waiting for the
>alert to finish. Thanks for any help you can provide. Carlos :-)
>
>PS - I am running mon in Linux for S/390.
