Tested on v229.
On Fri, Jun 10, 2016 at 3:37 PM, Shimin Guo wrote:
> Summary: If bar depends on foo via Requires and After, a failed restart on
> foo leaves bar permanently in the failed state, even if a later autorestart
> successfully brings up foo, even if bar is configured to always restart.
Summary: If bar depends on foo via Requires and After, a failed restart on
foo leaves bar permanently in the failed state, even if a later autorestart
successfully brings up foo, even if bar is configured to always restart. Is
this how systemd restart and dependency is supposed to work?
To repro:
10 juin 2016 18:26 "Lennart Poettering" a écrit:
> On Fri, 10.06.16 13:48, Florent Peterschmitt ([email protected]) wrote:
>
>> I have no udev rules at all in this initramfs, and as I said in
>> another mail, i'll try with genkernel-next that embeds udev (there is
>> a specific option for t
On Fri, 10.06.16 13:48, Florent Peterschmitt ([email protected]) wrote:
> I have no udev rules at all in this initramfs, and as I said in
> another mail, i'll try with genkernel-next that embeds udev (there is
> a specific option for that) and do stuff with SYSTEMD_READY.
I am not sure DM i
10 juin 2016 15:31 "Lennart Poettering" a écrit:
> On Thu, 09.06.16 20:30, Florent Peterschmitt ([email protected]) wrote:
>
>> # udevadm info /dev/mapper/root
>> P: /devices/virtual/block/dm-0
>> N: dm-0
>> E: DEVNAME=/dev/dm-0
>> E: DEVPATH=/devices/virtual/block/dm-0
>> E: DEVTYPE=disk
>
On Thu, 09.06.16 20:30, Florent Peterschmitt ([email protected]) wrote:
> # udevadm info /dev/mapper/root
> P: /devices/virtual/block/dm-0
> N: dm-0
> E: DEVNAME=/dev/dm-0
> E: DEVPATH=/devices/virtual/block/dm-0
> E: DEVTYPE=disk
> E: DM_UDEV_DISABLE_DISK_RULES_FLAG=1
> E: DM_UDEV_DISABLE_O
On Thu, 09.06.16 21:42, Sebastian Ott ([email protected]) wrote:
>
> Since the introduction of the whitelist in 60-persistent-storage.rules
> block device symlinks are no longer created for scm block devices.
>
> Add scm to the whitelist.
We generally prefer PR submissions via github th
On Thu, 09.06.16 17:11, Egor M. ([email protected]) wrote:
> Hello.
>
> How to enable IPv6 forwarding in systemd-nspawn containers? I have a container
> with network-bridge (--network-bridge=br0). Despite of
> net.ipv6.conf.all.forwarding value and corresponding interface values, IP
10.06.2016 11:01, Florent Peterschmitt пишет:
> 10 juin 2016 08:06 "Andrei Borzenkov" a écrit:
>> 09.06.2016 23:30, Florent Peterschmitt пишет:
>>
>>> The log with systemd.log_level=debug at boot is located here:
>>> http://data.peterschmitt.fr/systemd.log
>>
>> Unfortunately this log while being
10 juin 2016 08:06 "Andrei Borzenkov" a écrit:
> 09.06.2016 23:30, Florent Peterschmitt пишет:
>
>> The log with systemd.log_level=debug at boot is located here:
>> http://data.peterschmitt.fr/systemd.log
>
> Unfortunately this log while being verbose does not add any useful
> information.
>
>>
10 matches
Mail list logo
