There are a number of possiblities here
in reply to Perl processes that never die
Since we can have no possible way of knowing what your script does, we cannot analyze it. I don't even know if the Netscape server runs the script persistently or not, so it's unlikely that you'll find a solution here. An ugly hack would be to throw in a alarm(x); at the top of your script where x is the maximum amount of time this entire script can take. That's bad- you probably don't want that. Instead, pull apart your code, especially looking at any loops for any bugs.
- the server is doing something wrong or has been improperly configured
- you have an infinite loop in your program that you don't know about
- Netscape's handling of perl scripts is EVILLY flawed (?)
Related to the client pushing the STOP button? I dunno. Why don't you try it and find out?
AgentM Systems nor Nasca Enterprises nor
Bone::Easy nor Macperl is responsible for the
comments made by
AgentM. Remember, you can build any logical system with NOR.