Re: [Bluez-devel] Permission flags (chmod) for /dev/rfcomm*

Re: [Bluez-devel] Permission flags (chmod) for /dev/rfcomm*

[Marcel Holtmann]

Hi Thomas,

> We have a bunch of small robots that we can access via bluetooth. For  
> each robot, we added an entry in the /etc/bluetooth/rfcomm.conf file.  
> These entries look as follows:
> 	rfcommXX {
> 		bind yes;
> 		device HARDWARE_ADDRESS;
> 		channel 1;
> 	}
> 
> When we start the bluetooth service, the following line is executed  
> (as root)
> 	rfcomm bind all
> which creates a /dev/rfcommXX for each robot. There are two issues  
> with these files:
> 
> 1) All devices are created with chmod 600 (crw-------). This is a  
> problem for us because we want several users to be able to access  
> them. Is there a way of configuring the chmod mask in the rfcomm.conf  
> file?
> (Note that launching a "chmod 666 /dev/rfcomm*" after "rfcomm bind  
> all" is not a good solution since the devices are created with some  
> delay.)
> 
> 2) These devices belong to the locally logged in user, not root. Why?  
> Is there a way to configure that (user and group ownership)?

both are udev related questions and in both cases the udev configuration
is the answer.

Regards

Marcel




-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

[Bluez-devel] Permission flags (chmod) for /dev/rfcomm*

[Thomas Lochmatter]

We have a bunch of small robots that we can access via bluetooth. For  
each robot, we added an entry in the /etc/bluetooth/rfcomm.conf file.  
These entries look as follows:
	rfcommXX {
		bind yes;
		device HARDWARE_ADDRESS;
		channel 1;
	}

When we start the bluetooth service, the following line is executed  
(as root)
	rfcomm bind all
which creates a /dev/rfcommXX for each robot. There are two issues  
with these files:

1) All devices are created with chmod 600 (crw-------). This is a  
problem for us because we want several users to be able to access  
them. Is there a way of configuring the chmod mask in the rfcomm.conf  
file?
(Note that launching a "chmod 666 /dev/rfcomm*" after "rfcomm bind  
all" is not a good solution since the devices are created with some  
delay.)

2) These devices belong to the locally logged in user, not root. Why?  
Is there a way to configure that (user and group ownership)?

Thanks,
Thomas



-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel