On Tue, 10 Sep 2013 15:36:26 +0200,
Kay Sievers wrote:
Udev still does all what did before systemd. It was never really able
to run or start long-running tasks. Udev can only reliably handle
synchronously started and very short-living programs, and that was
always the case.
Ahh, you are corr
On Tue, Sep 10, 2013 at 3:14 PM, MUNEDA Takahiro
wrote:
>> Udev still does all what did before systemd. It was never really able
>> to run or start long-running tasks. Udev can only reliably handle
>> synchronously started and very short-living programs, and that was
>> always the case.
>
>
> Ahh
On Tue, 10 Sep 2013 02:25:19 +0200,
Lennart Poettering wrote:
On Mon, 09.09.13 17:23, MUNEDA Takahiro (muneda.takah...@jp.fujitsu.com) wrote:
Ok, I found out another problem.
Even if I have a following udev rules and 'remove' event happens, no
systemd service will be called.
ACTION=="add|
On Mon, 9 Sep 2013 23:45:01 +0200,
Kay Sievers wrote:
On Mon, Sep 9, 2013 at 11:23 PM, MUNEDA Takahiro
wrote:
Ok, I found out another problem.
Even if I have a following udev rules and 'remove' event happens, no
systemd service will be called.
ACTION=="add|remove", TAG+="systemd", ENV{SY
On Mon, 09.09.13 17:23, MUNEDA Takahiro (muneda.takah...@jp.fujitsu.com) wrote:
> Ok, I found out another problem.
> Even if I have a following udev rules and 'remove' event happens, no
> systemd service will be called.
>
> ACTION=="add|remove", TAG+="systemd", ENV{SYSTEMD_WANTS}="muneda@.serv
On Fri, 06 Sep 2013 22:41:05 -0400,
MUNEDA Takahiro wrote:
> When an unit is called via udev rules like below, only first 'online'
> works correctly. Even if 'offline' event has happen, device and its
> relative data still exists inside systemd, then following online
> events will be ignored sin
On Mon, Sep 9, 2013 at 11:23 PM, MUNEDA Takahiro
wrote:
> Ok, I found out another problem.
> Even if I have a following udev rules and 'remove' event happens, no
> systemd service will be called.
>
> ACTION=="add|remove", TAG+="systemd", ENV{SYSTEMD_WANTS}="muneda@.service"
>
> My final goal is
When an unit is called via udev rules like below, only first 'online'
works correctly. Even if 'offline' event has happen, device and its
relative data still exists inside systemd, then following online
events will be ignored since systemd thinks it's already done. The
device and its relatives sh
