| Subject: | kill job vs. pid |
|---|---|
| From: | Daniel Norton <danorton@xxxxxxxxx> |
| Date: | Fri, 25 Jul 2008 07:28:03 -0700 (PDT) |
| Newsgroups: | gnu.bash.bug |
A simple question and perhaps its simplicity explains why I can't find
an answer elsewhere:
How do I tell bash to kill job 1, rather than pid 1 ?
What does "kill <<n>>" mean? What if there is no jobspec <<n>> and I
type "kill <<n>>" ?
e..g.
$ jobs
[1]+ Stopped blahblahblah
$ ps 1
PID TTY STAT TIME COMMAND
1 ? Ss 0:02 /sbin/init
Thanks.
--
Daniel
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Variable scoping, Chet Ramey |
|---|---|
| Next by Date: | How to create parameterized aliases in bashrc, Aman Jain |
| Previous by Thread: | Re: Variable scoping, Pierre Gaston |
| Next by Thread: | Re: kill job vs. pid, Paul Jarc |
| Indexes: | [Date] [Thread] [Top] [All Lists] |