From: Pacho Ramos <pacho@gentoo.org>
To: BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: About udev rule removal
Date: Fri, 06 Jul 2012 20:36:59 +0200 [thread overview]
Message-ID: <1341599820.4531.0.camel@belkin4> (raw)
In-Reply-To: <CAMOw1v6hMcHqWAhHHyJAsQhjo=nrp62bYm9+TCeOehV_ktoKbw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1235 bytes --]
El mar, 03-07-2012 a las 10:21 -0300, Lucas De Marchi escribió:
> On Sat, Jun 30, 2012 at 3:15 PM, Pacho Ramos <pacho@gentoo.org> wrote:
> > El vie, 29-06-2012 a las 22:23 +0200, Pacho Ramos escribió:
> >> I would like to know what distributions not relying on systemd are
> >> supposed to get bluetoothd autostarted now that udev rule was dropped:
> >> http://git.kernel.org/?p=bluetooth/bluez.git;a=commit;h=2ea98a6a043710ad4958355b62c682b4767f292e
> >>
> >> Looks like we go back from udev rule to manually starting bluetoothd all
> >> the time, even if bluetooth device is not connected? Why are we going
> >> back to old behavior?
> >>
> >> Thanks for the info
> >
> > Should we revert that change downstream if we are not going to rely on
> > systemd and until udev is changed to break that setup (forcing us to go
> > to old "always running" behavior)?
>
> Udev rules are not supposed to spawn daemons. It never was. And now if
> you do that udev will kill your daemon after a certain timeout. You'd
> need to a) maintain that rule by yourself and b) patch udev to not do
> that.
>
>
> Lucas De Marchi
>
Will go with the old way of starting it with an init.d script then.
Thanks for the info.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2012-07-06 18:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-29 20:23 About udev rule removal Pacho Ramos
2012-06-30 18:15 ` Pacho Ramos
2012-07-03 13:21 ` Lucas De Marchi
2012-07-06 18:36 ` Pacho Ramos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1341599820.4531.0.camel@belkin4 \
--to=pacho@gentoo.org \
--cc=linux-bluetooth@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox