On Aug 18, 9:09pm, Peter Stephenson wrote:
}
} + } else if (sig == SIGCONT) {
} + Job jn;
} + Process pn;
} + if (findproc(pid, &jn, &pn, 0)) {
} + if (WIFSTOPPED(pn->status))
} + pn->status = SP_RUNNING;
} +
On Aug 20, 12:14am, Jilles Tjoelker wrote:
}
} > [continuing a stopped background job using kill is not reflected in the
} > output of jobs]
}
} I think hooking into the kill builtin is the wrong way to fix this.
} Instead, use the facilities provided by modern systems which can notify
} you if a
> [continuing a stopped background job using kill is not reflected in the
> output of jobs]
I think hooking into the kill builtin is the wrong way to fix this.
Instead, use the facilities provided by modern systems which can notify
you if a child process continues. These are si_code CLD_CONTINUED
On Wed, 18 Aug 2010 18:29:59 +
Clint Adams wrote:
> On Wed, Aug 18, 2010 at 02:51:48PM +1200, Victor Villa wrote:
> > After running a process in the background (by putting "&" at the end
> > of the command line) the output of "jobs" correctly shows the
> > process as "running". If I send the p
On Wed, Aug 18, 2010 at 02:51:48PM +1200, Victor Villa wrote:
> After running a process in the background (by putting "&" at the end of the
> command line) the output of "jobs" correctly shows
> the process as "running". If I send the process a STOP signal with "kill
> -STOP", the process stops
Package: zsh
Version: 4.3.10-14
Severity: normal
After running a process in the background (by putting "&" at the end of the
command line) the output of "jobs" correctly shows
the process as "running". If I send the process a STOP signal with "kill
-STOP", the process stops and "jobs" shows t
6 matches
Mail list logo
