Hello
On Wed, Oct 5, 2011 at 4:10 PM, Albert Strasheim wrote:
> Hello all
> I have the following udev rule in a machine with a bunch of disks:
> SUBSYSTEM=="block", KERNEL=="sd*", TAG+="systemd", ACTION=="add",
> RUN+="/bin/systemctl restart blockinit@%k.service"
To answer myself: systemctl has
On Thu, Oct 6, 2011 at 11:29, Albert Strasheim wrote:
> On Wed, Oct 5, 2011 at 4:10 PM, Albert Strasheim wrote:
>> Hello all
>> I have the following udev rule in a machine with a bunch of disks:
>> SUBSYSTEM=="block", KERNEL=="sd*", TAG+="systemd", ACTION=="add",
>> RUN+="/bin/systemctl restart b
Hello
On Thu, Oct 6, 2011 at 1:05 PM, Kay Sievers wrote:
> On Thu, Oct 6, 2011 at 11:29, Albert Strasheim wrote:
>> On Wed, Oct 5, 2011 at 4:10 PM, Albert Strasheim wrote:
>>> Hello all
>>> I have the following udev rule in a machine with a bunch of disks:
>>> SUBSYSTEM=="block", KERNEL=="sd*",
We can reproducably get an F15 system in a state that it fails to
complete a reboot.
Becuase all the logging, network and getty's has been stopped all
we can see is the kernel messages on the console.
What we need to know is why systemd is not completing the reboot.
What advice do you have on ho
On Thursday 06 October 2011 15:56:43 Barry Scott wrote:
> We can reproducably get an F15 system in a state that it fails to
> complete a reboot.
>
> Becuase all the logging, network and getty's has been stopped all
> we can see is the kernel messages on the console.
>
> What we need to know is wh
Sorry, inadvertently left off the ML.
Original Message
Subject: Re: [systemd-devel] Seeking Advice on debugging failure to reboot
Date: Thu, 06 Oct 2011 15:01:30 -0400
From: Clyde E. Kunkel
To: Barry Scott
On 10/06/2011 01:26 PM, Barry Scott wrote:
On Thursday 06 October 201
