Re: [systemd-devel] SYSTEMD_WANTS and oneshot services

2011-08-24 Thread Albert Strasheim
Hello On Tue, Aug 23, 2011 at 6:09 PM, Lennart Poettering lenn...@poettering.net wrote: On Sun, 21.08.11 14:01, Albert Strasheim (full...@gmail.com) wrote: Is there a way to always get this behavior? I'd like my network interfaces to be brought up regardless of how and when their modules are

Re: [systemd-devel] SYSTEMD_WANTS and oneshot services

2011-08-24 Thread Lennart Poettering
On Wed, 24.08.11 13:26, Albert Strasheim (full...@gmail.com) wrote: When reloading the module, there is no transaction in the debug log. When I strace systemd, I can see that epoll returns and that systemd calls recvmsg twice for the netlink messages about the two network ports. systemd

Re: [systemd-devel] SYSTEMD_WANTS and oneshot services

2011-08-24 Thread Albert Strasheim
Hello On Wed, Aug 24, 2011 at 2:04 PM, Lennart Poettering lenn...@poettering.net wrote: On Wed, 24.08.11 13:26, Albert Strasheim (full...@gmail.com) wrote: When reloading the module, there is no transaction in the debug log. When I strace systemd, I can see that epoll returns and that systemd

[systemd-devel] SYSTEMD_WANTS and oneshot services

2011-08-21 Thread Albert Strasheim
Hello all After my misadventures with SYSTEMD_ALIAS, I've tried to do it with SYSTEMD_WANTS instead. My udev rule: SUBSYSTEM==net, NAME==em[1-2], TAG+=systemd, ENV{SYSTEMD_WANTS}=foo-net-$name.service And my foo-net-em1.service unit (just calls the existing network scripts for now): [Unit]