The problem with turning processing over to the user script when a SIGHUP is received is that the script can not determine if there is a controlling terminal or not. If the terminal is gone and the user attempts any kind of terminal I/O then the script will hang forever for all practical purposes.
Also, by letting the user script process the SIGHUP you are really not using the signal system the way it is intended to operate on *nix. Oh, and there is one REALLY BIG POINT. The SIGHUP signal is NOT platform independent. It is NOT supported on Windows and therefore the behavior of the script would be different than on a *nix platform. This is an absolute reason not to support SIGHUP processing. David Ashley ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_d2d_nov _______________________________________________ Oorexx-devel mailing list Oorexx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/oorexx-devel
