Subject: RE: kill stopped jobs
From: Leif Sawyer (lsawyer@gci.com)
Date: Tue Sep 09 2003 - 10:23:49 AKDT
Tim Jordan writes:
> I've been using Ctrl+Z in bash incorrectly. I now understand
> that this STOPs a job.
>
> [root@Tim-on-Linux etc]# jobs
> [1] Stopped userdrake (wd: /mnt)
> [2]- Stopped userdrake (wd: /mnt)
> [3]+ Stopped man kill
>
> [root@Tim-on-Linux etc]# ps -ae | grep userdrake
> 31828 pts/2 00:00:00 userdrake.real
> 31842 pts/2 00:00:00 userdrake.real
>
> Now- how do I kill these jobs?
> I've tried kill 31828 .......no luck...
Tim, What this does (for shells that support job control) is
temporarily pauses the process.
From here on, i'll only talk about bash:
List the paused processes by typing 'jobs'
1 31828 pts/2 00:00:00 userdrake.real
2 31842 pts/2 00:00:00 userdrake.real
Bring a paused job into the foreground
$ fg %1
Put a paused job into the background
$ bg %2
Kill a paused job:
$ kill -9 %2
-- Binary/unsupported file stripped by Listar --
-- Type: application/x-pkcs7-signature
-- File: smime.p7s
---------
To unsubscribe, send email to <aklug-request@aklug.org>
with 'unsubscribe' in the message body.
This archive was generated by hypermail 2a23 : Tue Sep 09 2003 - 10:24:51 AKDT