[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Possibly a bug

From: Chet Ramey
Subject: Re: Possibly a bug
Date: Mon, 20 Apr 2015 17:13:40 -0400
User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.6.0

On 4/20/15 5:01 PM, Valentin Bajrami wrote:

> Now when running ./history | his  where his is not an existing command it
> fails and adds an entry in the job list.
> $ ./history | his
> [2]+  Stopped                 ./history | his
> bash: his: command not found...
> Running twice the output becomes:
> $ jobs -l
> [1]-  6556 Killed                  ./history
>       6557 Stopped (tty input)     | his
> [2]+  6830 Stopped (tty input)     ./history
>       6831                       | his
> I seem not to be able to clean up the jobs.
> Can anyone explain what is really happening?

It's most likely that you have a shell function defined for your
command-not-found hook (command_not_found_handle) and that function
attempts to read from the tty, or calls a program that does, causing the
process group to stop due to SIGTTIN.

``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, ITS, CWRU    address@hidden    http://cnswww.cns.cwru.edu/~chet/

reply via email to

[Prev in Thread] Current Thread [Next in Thread]