Re: [Patch v2 2/2] let user specify action after systemd start dracut-emergency

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 05/31/2013 05:45 PM, Harald Hoyer wrote:

> emergency.service is the last resort emergency.
> 
> [harald@lenovo rules (master)]$ fgrep OnFail /lib/systemd/system/*.target
> /lib/systemd/system/initrd-fs.target:OnFailure=emergency.target
> /lib/systemd/system/initrd-fs.target:OnFailureIsolate=yes
> /lib/systemd/system/initrd-root-fs.target:OnFailure=emergency.target
> /lib/systemd/system/initrd-root-fs.target:OnFailureIsolate=yes
> /lib/systemd/system/initrd.target:OnFailure=emergency.target
> /lib/systemd/system/initrd.target:OnFailureIsolate=yes
> 
> Maybe we should refrain from isolating to the emergency.target, which starts
> emergency.service.
> 
> I'll ask on the systemd-devel list.


I tried set these OnFailureIsolate=no, seems services not started any
more and systemd hang there.

--
To unsubscribe from this list: send the line "unsubscribe initramfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux SCSI]

  Powered by Linux