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

[Johannes Ernst]

> On Jul 1, 2015, at 14:59, Michael Biebl <mbiebl at gmail.com> wrote:
> 
> 2015-07-01 22:50 GMT+02:00 Johannes Ernst <johannes.ernst at gmail.com <mailto:johannes.ernst at gmail.com>>:
>> 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
> 
> Which packages ships that tmpfiles snippet? This is not coming from
> systemd itself.

https://github.com/systemd/systemd/blob/master/units/systemd-tmpfiles-setup.service.in <https://github.com/systemd/systemd/blob/master/units/systemd-tmpfiles-setup.service.in>


> 
> -- 
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?

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