From: "Mikael Lindqvist" <li.mikael.spam@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] permissions to set local name
Date: Mon, 20 Nov 2006 09:31:57 +0100 [thread overview]
Message-ID: <b5dccebe0611200031v64a8d2d0xfdd92edf29a44d0@mail.gmail.com> (raw)
In-Reply-To: <1163940471.11790.2.camel@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 1575 bytes --]
Hi again,
How does hcid know what mode that is "best" for my application? I want to
make sure that it is 1 (result with rssi), is there a way I can tell hcid to
always choose that mode then?
Also, I would like to have as few external dependencies, so if possible I
would prefer to not use d-bus. Is there a way to set the local name without
d-bus and without root privileges?
-- Mikael
On 11/19/06, Marcel Holtmann <marcel@holtmann.org> wrote:
>
> Hi Mikael,
>
> > I've noticed that only the superuser may perform some hci commands,
> > such as OCF_WRITE_LOCAL_NAME and OCF_WRITE_INQUIRY_MODE. How can I
> > grant privileges for other users to perform those commands?
> >
> > The problem is that I have an application that needs to set those
> > paramaters, but I don't want to run the application as root.
>
> the inquiry mode should never be set by an application. It is up to hcid
> to pick the best inquiry mode.
>
> The local name can be set via the D-Bus interface and no root privileges
> are needed.
>
> Regards
>
> Marcel
>
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>
[-- Attachment #1.2: Type: text/html, Size: 2169 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 164 bytes --]
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2006-11-20 8:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-19 11:50 [Bluez-users] permissions to set local name Mikael Lindqvist
2006-11-19 12:47 ` Marcel Holtmann
2006-11-20 8:31 ` Mikael Lindqvist [this message]
2006-11-20 8:43 ` Marcel Holtmann
2006-11-21 9:14 ` Mikael Lindqvist
2006-11-21 9:17 ` Marcel Holtmann
2006-11-21 9:36 ` Mikael Lindqvist
2006-11-21 11:10 ` Marcel Holtmann
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=b5dccebe0611200031v64a8d2d0xfdd92edf29a44d0@mail.gmail.com \
--to=li.mikael.spam@gmail.com \
--cc=bluez-users@lists.sourceforge.net \
/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