Of course you will not be able to kill te stuck httpx and you need to
avoid killing your cmd.exe session.
The kernel is going to try to kill these process off on it's own. You are
getting helping it out.
>0105 0.105M 0.012M 27 3 PROCDUMP
PROCDUMP should not be running.
>but if it's apache with his unkillable child all these improvements will
>not help for sure, since afaik in some way it lock something in the file
>system that prevent the normal reboot with setboot /b
My experience is that unkillable processes do not prevent reboots. The
kernel will attempt to kill all the existing processes, but it is fully
aware that the kill might fail and this will not prevent the reboot.
My gut feel is that this is more of a hardware issue. A
>i also don't know if there something more powerful to the setboot /b that
>is able to reboot the system also in those situations
Don't you think that after all the years you have used OS/2, if such a
thing existed, you would already know about it?
BTW, which version of setboot are you using? There's the AiRBoot version,
the IBM version and the dfsee version. They all invoke the same IOCTL to
do the reboot.
Tillbaks till lista