running X
windows under various window managers (AfterStep 0.18.1, Sawfish 0.24
and Enlightenment 0.16.4 ).
(*KRUD = Kevens Redhat Uber Distribution # 6.2 - 2430)
# Problem 1 -- VM: killing processes
>From a *cold boot* I immediately log into the root shell. I run "top"
and it sh
Thanks Kirk and Chris,
Indeed, my problems started when I mistyped a tar command. I just
rebooted the system. (That's so Windows!) Everything's back to normal
now. But still, it's quite a pain not to be able to kill such a
process. Any prospects of a fix in future kernels? Thanks,
Hidong
Do the "killed" processes show up on 'ps' as zombies (with a Z)? If so then
they may be there because their parent process is still (erroneously)
waiting for them to complete. Try using adding the -f option to ps. This
will show the parent-child relationships of your processes. If this is the
Hate to say this, but mabey you should reboot. It sounds like there is some
issue with your tape drive. Were you doing a backup when this started? Mabey
something with your backup software.
Kirk
>At 07:30 PM 3/28/00 -0800, you wrote:
>Yes. The processes still show up. The really bad thing abou
Yes. The processes still show up. The really bad thing about this
problem is that I can't access my tape drive /dev/st0 now.
Hidong
"[EMAIL PROTECTED]" wrote:
>
> Have you tried
> killall tar
>
> Kirk
>
> >At 04:15 PM 3/28/00 -0800, you wrote:
> >Hi,
> >
> >I'm trying to kill some tar pr
Have you tried
killall tar
Kirk
>At 04:15 PM 3/28/00 -0800, you wrote:
>Hi,
>
>I'm trying to kill some tar processes, but I can't. They show up like
>this with ps aux:
>
>
>
>root 12166 0.0 0.1 1224 432 ?D15:54 0:00 tar Xcvf
>backup.e
>root 12174 0.0 0.1 1224 432 ?
Hi,
I'm trying to kill some tar processes, but I can't. They show up like
this with ps aux:
root 12166 0.0 0.1 1224 432 ?D15:54 0:00 tar Xcvf
backup.e
root 12174 0.0 0.1 1224 432 ?D15:57 0:00 tar -X
backup.exc
root 12209 0.0 0.1 1224 432 ?
I've seen this done in perl cgi scripts to prevent them from taking too
long - put the following in your script, right after the #!/usr/bin/perl
alarm(6);
If the program is still running after 6 seconds it will send an SIGALRM
signal to itself and die. You might want to define a handler, and cat
I'm wondering if it's possible to kill processes automatically (as a
cron-job?).
I've managed to setup Linux and Apache and now I tried to kill the machine
by executing several processes to find out, how the machine reacts. I wrote
a little perl script (cgi) that calls itself. My provider has the
