On Fri, Sep 19, 2003 at 02:34:37PM -0400, Rolf Campbell wrote:
>Christopher Faylor wrote:
>>This problem sounded familiar so I did a little archive diving. It was
>>reported before and I investigated it before. I remember thinking that
>>this would be hard to fix owing to a race condition with si
Christopher Faylor wrote:
On Fri, Aug 15, 2003 at 09:10:12PM -0400, Rolf Campbell wrote:
Christopher Faylor wrote:
On Mon, Sep 08, 2003 at 04:44:58PM -0400, Rolf Campbell wrote:
I started a large build, then hit ^Z. Then "fg", and this is what
happened:
A large build shouldn't even recognize
On Fri, Aug 15, 2003 at 09:10:12PM -0400, Rolf Campbell wrote:
>Christopher Faylor wrote:
>>On Mon, Sep 08, 2003 at 04:44:58PM -0400, Rolf Campbell wrote:
>>>I started a large build, then hit ^Z. Then "fg", and this is what
>>>happened:
>>A large build shouldn't even recognize the ^Z if you are r
Christopher Faylor wrote:
On Mon, Sep 08, 2003 at 04:44:58PM -0400, Rolf Campbell wrote:
I started a large build, then hit ^Z. Then "fg", and this is what happened:
A large build shouldn't even recognize the ^Z if you are running this from
the console. Your TERM=xterm below. Are you running this
On Mon, Sep 08, 2003 at 04:44:58PM -0400, Rolf Campbell wrote:
>I started a large build, then hit ^Z. Then "fg", and this is what happened:
A large build shouldn't even recognize the ^Z if you are running this from
the console. Your TERM=xterm below. Are you running this under X?
cgf
--
Unsub
I started a large build, then hit ^Z. Then "fg", and this is what happened:
begin
make[2]: Leaving directory `/c/base2/node/comp/DiagNodeScheduler'
make[2]: Entering directory `/c/base2/node/comp/equipConf'
[1]+ Stopped nice -20 make -rsw -C pload/SCC target
/
6 matches
Mail list logo
