[systemd-devel] How do I find out why a service was started? (systemd-tmpfiles-setup failed in container)

[Johannes Ernst]

> On Jul 3, 2015, at 4:01, Lennart Poettering <lennart at poettering.net> wrote:
> 
> On Wed, 01.07.15 13:50, Johannes Ernst (johannes.ernst at gmail.com <mailto:johannes.ernst at gmail.com>) wrote:
> 
>> Hey Martin,
>> 
>> thanks, but:
>> 
>>>> My container is degraded because systemd-tmpfiles-setup.service
>>>> failed. My understanding is that it should not run in the container
>>>> anyway. (Right?)
>>> 
>>> It should run in a container; its purpose is both necessary, and I
>>> don't see why a container would have any difficulty with it. It runs
>>> just fine in both system and even unprivileged user containers here.
>> 
>> Here is what fails:
>> 
>> # /usr/bin/systemd-tmpfiles --create --remove --boot --exclude-prefix=/dev
>> Failed to create file /sys/devices/system/cpu/microcode/reload: Read-only file system
> 
> We should probably handle this case in a nicer way, and downgrade
> EROFS error for cases like this.
> 
> Can you let me know which tmpfiles snippet actually adds this line,
> and what precisely it contains? i.e. look in /usr/lib/tmpfiles.d/ for
> the file that mentions "/sys/devices/system/cpu/microcode/reload", and
> figure out the package name it is shipped with, and paste the contents
> of the file here.

/usr/lib/tmpfiles.d/linux-firmware.conf is owned by linux-firmware 20150527.3161bfa-1

Content:

w /sys/devices/system/cpu/microcode/reload - - - - 1


> 
> Thanks,
> 
> Lennart
> 
> -- 
> Lennart Poettering, Red Hat

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20150706/ad97dd3b/attachment-0001.html>