[systemd-devel] systemd195: issue with udev launched script

[Warpme]

On 11/15/12 9:05 PM, Kay Sievers wrote:
> On Thu, Nov 15, 2012 at 7:40 PM, Warpme <warpme at o2.pl> wrote:
>> Sometime ago upgraded my ArchLinux (kernel3.3.8) server to systemd195.
>> Today I discovered that my backup procedure fails. It was working OK with
>> previous systemd.
>> Forgive me if this forum is wrong place to ask such questions, but as udev
>> is now part of systemd - I decided to ask here...
>> I know that long tasks launched by udev should be detached.
>> Maybe some merciful soul help me with finding error in following approach:
>> (maybe there is better way do to launching scripts on USN attach ?)
> Udev even handlers cannot run long running processes, they get cleaned
> up after a timeout. That's what you see here.
>
> Udev events are timing critical, and they might block the entire
> bootup if they do not return in time. There is no sane way to make
> udev run such scripts, handle that properly. It is not really made to
> start such services.
>
> You can use systemd to instantiate a service on device discovery (or
> run a daemon that listens to events from udev on old init systems).
>
> Check how bluetooth, cups printers, usbmux, ... is handled:
>    TAG+="systemd",
> ENV{SYSTEMD_WANTS}="configure-printer at usb-$env{BUSNUM}-$env{DEVNUM}.service"
>    TAG+="systemd", ENV{SYSTEMD_WANTS}+="bluetooth.target"
>    TAG+="systemd", ENV{SYSTEMD_WANTS}="usbmuxd.service"
>
> Kay
>
Kay, Dave
Million thx for quick replay !
It's great that systemd solves in nice way also this aspect.
I definitely will go systemd+templates route.
Thx again

-------------- next part --------------
A non-text attachment was scrubbed...
Name: warpme.vcf
Type: text/x-vcard
Size: 89 bytes
Desc: not available
URL: <http://lists.freedesktop.org/archives/systemd-devel/attachments/20121115/8e9749df/attachment.vcf>