|
| How to kill a runaway perl script |
 |
Tue, 15 Aug 2006 12:07:03 GMT |
HI,
Is there any way to kill a runaway perl srcipt on netware?
If I try to unload perl I get a Command LIne Interface cannot be unloaded
at this time error.
|
| Post Reply
|
| Re: How to kill a runaway perl script |
 |
Tue, 15 Aug 2006 23:30:59 GMT |
Hi Brian,
Brian Mantler <brianmantler@nowhere.com> wrote in
news:Xns9820529281566brianmantlernowherec@130.57.1.81:
> HI,
>
> Is there any way to kill a runaway perl srcipt on netware?
>
> If I try to unload perl I get a Command LIne Interface cannot be unloaded
> at this time error.
thats most likely because your script has loaded addditional NLMs; if you
first unload these it might work;
I've had often luck with this:
# unlperl.ncf
unload socket
unload pmysql
unload dbi
unload base64
unload fcntl
unload io
unload cwd
unload glob
unload posix
unload perl
HTH, Guenter,
|
| Post Reply
|
| Re: How to kill a runaway perl script |
 |
Wed, 16 Aug 2006 08:17:24 GMT |
Brian Mantler wrote:
> HI,
> Is there any way to kill a runaway perl srcipt on netware?
> If I try to unload perl I get a Command LIne Interface cannot be unloaded
> at this time error.
> Thanks.
Brian,
I put Perl scripts that doesn't need to share OS address space ressources
into their own address space using:
load address space=<myspace> perl <myscript.pl>
To (brutally) kill it, unload the address space:
unload address space=<myspace>
This tip may come in a bit late for you - but it may help in the future.
|
| Post Reply
|
|
|
|
|
|
|
|
|
|