On Sun, 30.03.14 19:23, Andrey Borzenkov ([email protected]) wrote: > linux-qbc6:~ # systemctl show systemd-udevd.service -p FragmentPath > FragmentPath=/usr/lib/systemd/system/systemd-udevd.service > linux-qbc6:~ # cp /usr/lib/systemd/system/systemd-udevd.service > /etc/systemd/system > linux-qbc6:~ # systemctl daemon-reload > linux-qbc6:~ # cp /usr/lib/systemd/system/systemd-udevd.service > /etc/systemd/system > linux-qbc6:~ # systemctl show systemd-udevd.service -p FragmentPath > FragmentPath=/usr/lib/systemd/system/systemd-udevd.service > linux-qbc6:~ # exit > > >From non-exhaustive testing it appears to be the only unit showing this > property. Enabling systemd debug does not add any useful information > (no output about unit discovery). Any way to debug it? > > The version is systemd-208-19.1.x86_64 from openSUSE.
Hmm, that's weird. Is /etc on some weird mount point or so? It might be interesting to run "strace -o log -e open -p 1" and then trigger a reload, and then look at the generate log file "log". It should show you where systemd is looking for the udev service file, and might contain a hint, why it skips the file in /etc? Lennart -- Lennart Poettering, Red Hat _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
