On Thu, 16 Jan 2014 18:14:48 -0700
Chris Murphy wrote:
>
> systemd debug is rather verbose. First remove 'rhgb quiet' from the
> linux line,
Never liked a graphical both have been removed for many releases.
//* Daft, I like looking at the text going up. */
found in the grub menu. Highlight t
On Jan 16, 2014, at 3:50 PM, Frank Murphy wrote:
> On Thu, 16 Jan 2014 15:47:54 -0500
> Matthew Miller wrote:
>
>> Sorry, coming to this late, but did you try booting with
>>
>> systemd.log_level=debug
>>
>
> No,
>
> Would that have helped at the time read what was on the screen?
syste
On Thu, 16 Jan 2014 15:47:54 -0500
Matthew Miller wrote:
> Sorry, coming to this late, but did you try booting with
>
> systemd.log_level=debug
>
No,
Would that have helped at the time read what was on the screen?
___
Regards,
Frank
www.frankly3d.com
--
users mailing list
users@lists.f
On Thu, Jan 16, 2014 at 05:23:12PM +, Frank Murphy wrote:
> At the time after this test it just hung there,
> with the [faileds] just out of screen-shot.
> the bottom most entry on the screen was
> cannot find rescue.target
Sorry, coming to this late, but did you try booting with
systemd.log
On Thu, 16 Jan 2014 11:11:15 -0600
Michael Cronenworth wrote:
> Frank Murphy wrote:
> > Is there any way to have the screen to automatically pause
> > if "[FAILED] foo-bar.service" appears on the screen.
>
> Not unless you knew the failing service and added a unit file to
> "OnFailure=" in the
Frank Murphy wrote:
Is there any way to have the screen to automatically pause
if "[FAILED] foo-bar.service" appears on the screen.
Not unless you knew the failing service and added a unit file to "OnFailure=" in
the failing service's unit file.
Can you not find the failed service with "sys
Is there any way to have the screen to automatically pause
if "[FAILED] foo-bar.service" appears on the screen.
similar to the kernel-line pause_on_oops=N
I'm asking cause I got a number of fails during a test,
and my kb batteries decided to die at that exact time.
# with no spares around.
_
