Clément Lassieur skribis:
> Ludovic Courtès writes:
>
>> The commit above makes sure all child processes are reaped. Could you
>> check whether that solves the problem you’re seeing with ‘guix publish’?
>
> Indeed it's fixed. Thank you very much :-)
Excellent, thanks for checking!
Ludo’.
Ludovic Courtès writes:
> The commit above makes sure all child processes are reaped. Could you
> check whether that solves the problem you’re seeing with ‘guix publish’?
Indeed it's fixed. Thank you very much :-)
ng0 skribis:
> I just found this upstream issue: https://github.com/tmux/tmux/issues/311
> which has been fixed in tmux 2.5. I think we should take this bug to upstream,
> even if it's just to get more insight if it is a tmux bug.
Oh that probably explains why tmux leaves a zombie process, thoug
Clément Lassieur skribis:
> Ludovic Courtès writes:
>
>> Hi,
>>
>> Leo Famulari skribis:
>>
>>> On Sun, May 14, 2017 at 11:36:17PM +0200, Ludovic Courtès wrote:
What does /var/log/shepherd.log show around the time where you hit
“halt”?
I get something like this:
Ludovic Courtès transcribed 1.7K bytes:
> Hi,
>
> Leo Famulari skribis:
>
> > On Sun, May 14, 2017 at 11:36:17PM +0200, Ludovic Courtès wrote:
> >> What does /var/log/shepherd.log show around the time where you hit
> >> “halt”?
> >>
> >> I get something like this:
> >>
> >> --8<---
Ludovic Courtès writes:
> Hi,
>
> Leo Famulari skribis:
>
>> On Sun, May 14, 2017 at 11:36:17PM +0200, Ludovic Courtès wrote:
>>> What does /var/log/shepherd.log show around the time where you hit
>>> “halt”?
>>>
>>> I get something like this:
>>>
>>> --8<---cut here---
Hi,
Leo Famulari skribis:
> On Sun, May 14, 2017 at 11:36:17PM +0200, Ludovic Courtès wrote:
>> What does /var/log/shepherd.log show around the time where you hit
>> “halt”?
>>
>> I get something like this:
>>
>> --8<---cut here---start->8---
>> 18:06:26 Ser
Leo Famulari skribis:
> On Wed, May 17, 2017 at 09:39:45AM +0200, Ludovic Courtès wrote:
>> This is on the bare metal and /etc/shepherd/do-not-kill does not exist,
>> right?
>
> Yes, on a Thinkpad x200s (x86_64) with a recent kernel. Nothing is
> protected by a 'do-not-kill' file.
>
>> We could a
On Wed, May 17, 2017 at 09:39:45AM +0200, Ludovic Courtès wrote:
> This is on the bare metal and /etc/shepherd/do-not-kill does not exist,
> right?
Yes, on a Thinkpad x200s (x86_64) with a recent kernel. Nothing is
protected by a 'do-not-kill' file.
> We could always add a round of SIGKILL in the
Leo Famulari skribis:
> On Sun, May 14, 2017 at 11:36:17PM +0200, Ludovic Courtès wrote:
>> What does /var/log/shepherd.log show around the time where you hit
>> “halt”?
>>
>> I get something like this:
>>
>> --8<---cut here---start->8---
>> 18:06:26 Service
On Sun, May 14, 2017 at 11:36:17PM +0200, Ludovic Courtès wrote:
> What does /var/log/shepherd.log show around the time where you hit
> “halt”?
>
> I get something like this:
>
> --8<---cut here---start->8---
> 18:06:26 Service mcron has been stopped.
> 18:06:2
Leo Famulari skribis:
> When tmux is running, GuixSD fails to reboot. No more details yet, but
> confirmation from at least 3 users:
What does /var/log/shepherd.log show around the time where you hit
“halt”?
I get something like this:
--8<---cut here---start
When tmux is running, GuixSD fails to reboot. No more details yet, but
confirmation from at least 3 users:
[19:24:57] My system can't shut itself down. Once it says
everything is shut down, I have to power off with the power button.
[19:25:05] CharlieBrown: I've had that issue before
[19:25:12]
13 matches
Mail list logo
