Le lundi 24 septembre 2012 à 11:07 +0200, Andrea Turrini a écrit :
2012/9/24 Frederic Crozat <fcrozat@suse.com>:
By default, systemd-binfmt.service isn't started unless you have a config file in either /usr/lib/binfmt.d or /usr/local/lib/binfmt.d or /etc/binfmt.d or /run/binfmt.d. My guess is you have wine installed.
Just as information, I just checked since I have wine installed and autofs4 is loaded. The interesting fact is that /usr/lib/binfmt.d and /etc/binfmt.d are empty while /usr/local/lib/binfmt.d and /run/binfmt.d do not exist. If I run "systemctl status systemd-binfmt.service", I obtain
systemd-binfmt.service - Set Up Additional Binary Formats Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static) Active: inactive (dead) start condition failed at Mon, 24 Sep 2012 07:10:59 +0200; 3h 42min ago CGroup: name=systemd:/system/systemd-binfmt.service
and /lib/systemd/system/systemd-binfmt.service comes from systemd-44-10.1.1.x86_64, according to "rpm -qf" output.
Just a side question: the service is loaded but dead since the start condition failed. Where can I find a more complete info about the failure? If I grep /var/log/messages or systemd-journal for binfmt, I do not find any occurrence of binfmt...
How about looking at the service file itself ? :) I don't know if the exact failing conditions will be logged in future version of systemd. Regarding binfmt, I've checked deeper and there is also an automount setup as proc-sys-fs-binfmt_misc.automount -- Frederic Crozat <fcrozat@suse.com> SUSE -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org