Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: zsh (4.2.0-10)

X-seq: zsh-workers 19932
From: Clint Adams <schizo@xxxxxxxxxx>
To: "Christian T. Steigies" <cts@xxxxxxxxxx>
Subject: Re: zsh (4.2.0-10)
Date: Thu, 13 May 2004 10:12:37 -0400
Cc: zsh-workers@xxxxxxxxxx, sbuild@xxxxxxxxxxxxxxxxxxx, troup@xxxxxxxxxx, Q@xxxxxxx
In-reply-to: <20040513140213.GA26274@xxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <20040513074011.GA31678@skeeve> <20040513132408.GA32597@xxxxxxxxxxx> <20040513133541.GA24070@xxxxxxxxxxxxxxxx> <20040513140213.GA26274@xxxxxxxxxxxxxxxx>

> According the manpage, I sent a kill -s SIGCONT. Did that, this is what
> happened:

Technically it should be "kill -s CONT".

> ../../Test/B04read.ztst: starting.
> make[2]: *** [check] Terminated
> make[1]: *** [check] Terminated
> Build killed with signal 15 after 150 minutes of inactivity
> Build killed with signal 9 after 5 minutes of inactivity
> ******************************************************************************

Probably sbuild sent the SIGTERM long before you sent the SIGCONT, and
the build didn't react until you did.

Previously, this had only been seen using sbuild on ultrasparc, and
recently Kurt Roeckx reported a problem using sbuild on amd64.  I assume
you're using sbuild on m68k.  Yes?

Messages sorted by: Reverse Date, Date, Thread, Author