I've observed that mon leaves timeout management implementation to monitor scripts, what happens is that if the monitor script is badly writen and doesn't handle timeouts properly it will cause mon to stand waiting for response, a example of such a script is ping.monitor, which don't handle ping timeout (-w time paramenter), and in some cases get stuck at the pign forever.
Is this behaviour by design.? _______________________________________________ mon mailing list [EMAIL PROTECTED] http://linux.kernel.org/mailman/listinfo/mon
