Does anybody has a small hint and/or advice?
To state the obvious, not yet. Otherwise you would have gotten answers by now.
Windows is not Unix. MacOS X, on the other Hand, inherits more than just the "X" from Unix.
Windows has no signals, there are no SIGINT, SIGPIPE or SIGCHLD on Windows. Perl has a thin emulation layer, but it is far from being a perfect Unix emulation. See also Re: Handling killing the perl process, Re: Signals in Strawberry Perl: Name or number?, perlport, perlwin32.
Alexander
--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
| [reply] |
Sorry for being rude. I dared ask again because I've initially posted between Christmas and New Year.
Thanks for the links. I've read and investigated quite a lot before posting here and, to be honest, I don't fully understand everything. That's the reason why I'm asking a question.
Having this child process running is obviously not satisfactory, but I still haven't found any information on how to handle such a situation... What would a software consultant from BigCorporation do? Close eyes and call it a day?
| [reply] |