[systemd-bugs] [Bug 54560] systemd does not follow symlinks that point outside of /etc/systemd/system or /usr/lib/systemd/system

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=54560

--- Comment #1 from Dimitri <mitya at mageia.org> ---
Same here with Mageia 3 (Cauldron), systemd 195.

Having an ability to follow symlinks that point outside unit dir may be very
helpful sometimes. I'm now packaging Zabbix 2.0 for inclusion into Mageia
release. Zabbix's database backend can't be selected in runtime, so you have to
compile 3 versions (MySQL, PostgreSQL and SQLite3) and choose between them.
I've decided to use alternatives mechanism to switch between server executables
and corresponding systemd units (units are different because of dependencies on
different database services). In Fedora, all the unit files are put into
/usr/lib/systemd/system directory, thus exposing 4 services (main symlink and 3
actual units). I've decided not to pollute the directory and to put unit files,
say, in /usr/share/zabbix/systemd. But systemd is not able to load such a unit
because it tries to open unit file with O_NOFOLLOW.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20130407/a2f49bdf/attachment.html>