It's getting CPU-choked. If you abort a job that is getting no CPU at
all it will simply not do anything. What I would do is raise the job
into the CS queue before aborting it. Or find what's choking it off and
lower that job's priority.



Richard Hoffmann wrote:
>
> Apache is running,  but you cant access any of the web pages, (we get
> the server down or not responding message from Netscape).    We are
> trying to abort the Apache job,  but it appears to be hung.      We are
> going to stop the network services at noon and try an abortjob, but I
> don't know if this will help.
>
> Any Ideas other than restarting the system?
>
> Thanks
> Richard Hoffmann