2014/1/20 Colin Guthrie :
> CC'ing Zbigniew as he's working on the Fedora bug AFAIK.
>
> 'Twas brillig, and Lennart Poettering at 20/01/14 12:37 did gyre and gimble:
>> On Thu, 16.01.14 12:28, Colin Guthrie ([email protected]) wrote:
>>
>>>
>>> 'Twas brillig, and Colin Guthrie at 14/01/14 13:28
CC'ing Zbigniew as he's working on the Fedora bug AFAIK.
'Twas brillig, and Lennart Poettering at 20/01/14 12:37 did gyre and gimble:
> On Thu, 16.01.14 12:28, Colin Guthrie ([email protected]) wrote:
>
>>
>> 'Twas brillig, and Colin Guthrie at 14/01/14 13:28 did gyre and gimble:
>>> 3. Some s
On Thu, 16.01.14 12:28, Colin Guthrie ([email protected]) wrote:
>
> 'Twas brillig, and Colin Guthrie at 14/01/14 13:28 did gyre and gimble:
> > 3. Some sort of kernel trigger for me today led it to run two reexecs
> > quite quickly and triggered this problem randomly during runtime. This
> >
'Twas brillig, and Colin Guthrie at 14/01/14 13:28 did gyre and gimble:
> 3. Some sort of kernel trigger for me today led it to run two reexecs
> quite quickly and triggered this problem randomly during runtime. This
> *might* have come in via "telinit u" instead. It doesn't appear that the
> kerne
'Twas brillig, and Colin Guthrie at 14/01/14 12:57 did gyre and gimble:
> Looking again, it seems as if "systemctl daemon-reexec; systemctl
> daemon-reexec" can also trigger the problem...
OK, so from the last couple days of debugging, I can see two problems
where this problem occurs.
1. If syste
'Twas brillig, and Colin Guthrie at 14/01/14 12:10 did gyre and gimble:
> Hi,
>
> OK, so following on from my posts yesterday about "systemctl
> [en|dis]able weirdness + reload (writes /run/nologin)", I do still seem
> to be getting problems.
>
> It seems that I got bitten again by this today (th
