Well, this is a question from Miroslav Suchý on my PR with a solution.
https://github.com/rpm-software-management/mock/pull/293
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
On Tuesday, July 30, 2019 4:59:13 PM CEST Jan Buchmaier wrote:
> Do we want to catch/process SIGABRT as well?
I see no obvious use case for catching SIGABRT by mock.
Why are you asking about SIGABRT specifically?
Kamil
___
devel mailing list --
Do we want to catch/process SIGABRT as well?
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
On Tuesday, June 4, 2019 9:33:33 AM CEST Miroslav Suchý wrote:
> Dne 03. 06. 19 v 13:00 Kamil Dudka napsal(a):
>
> >> Now I'm working on signal SIGTERM handling and I would like to kill all
> >> processes related to the main mock process.
> >>
> >> What do you think is it a good
> >>
> >> idea
Dne 03. 06. 19 v 13:00 Kamil Dudka napsal(a):
>> Now I'm working on signal SIGTERM handling and I would like to kill all
>> processes related to the main mock process.
>> What do you think is it a good
>> idea to kill all processes, or do we want to kill the main process only?
>> And what about
On Monday, June 3, 2019 12:18:02 PM CEST Jan Buchmaier wrote:
> Now I'm working on signal SIGTERM handling and I would like to kill all
> processes related to the main mock process.
> What do you think is it a good
> idea to kill all processes, or do we want to kill the main process only?
> And
Now I'm working on signal SIGTERM handling and I would like to kill all
processes related to the main mock process.
What do you think is it a good idea to kill all processes, or do we want to
kill the main process only?
And what about SIGINT so-called KeyInterrupt in python? Same reaction?
