Hi Rebecca, On Sat, Feb 09, 2013, Rebecca Menessec wrote: > I was looking for a way to disable BlueZ logging (Ubuntu machine), and > came across this, in the bluetoothd manpage: > > 'bluetoothd itself does not accept many command-line options, as most of > its configuration is done in the /etc/bluetooth/main.conf file, which > has its own man page.' > > That doesn't appear to be true. I can't find any trace in any distro, or > in the source. I've found a bug filed here and there against the lack of > manpage, but no manpage. This is indeed a bug. I just pushed a patch to remove this reference from the bluetoothd man page. main.conf might deserve its own man page (even though the upstream sample is self-documenting) but as long one doesn't exist it's at least better not to have a bogus reference to it. It's also worth noting that we're really trying to promote systems without any /etc/bluetooth directory at all since the bluetoothd defaults should be usable by as many as possible. > There's definitely logging going on by default: > > localhost ~ [0]# lsof -n 2> /dev/null | grep blue | grep log > rsyslogd 804 syslog 2w REG 0,21 > 2027 8482 /var/log/bluetoothd.log > rs:main 804 813 syslog 2w REG 0,21 > 2027 8482 /var/log/bluetoothd.log > rsyslogd 804 814 syslog 2w REG 0,21 > 2027 8482 /var/log/bluetoothd.log > rsyslogd 804 815 syslog 2w REG 0,21 > 2027 8482 /var/log/bluetoothd.log > > Unfortunately, there's no hint anywhere what's causing bluetoothd to > log, or how to stop it. There is no way to stop bluetoothd from logging errors. You can enable/disable debug logs with the -d switch but that's it. Johan -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
