Hi Gang:
I called journalctl and got two lines that sparked a question:
Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 17 15:17:36 localhost.localdomain bluetoothd[502]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Should I be creating a bluetooth directory and perhaps touching the files: input.conf and serial.conf? I went ahead and created the directory, but I have yet to create the files.
Thanks
Richard
On Sun, 2013-10-27 at 09:23 -0700, Richard Vickery wrote:
Hi Gang:
I called journalctl and got two lines that sparked a question:
Parsing /etc/bluetooth/input.conf failed: No such file or directory
Oct 17 15:17:36 localhost.localdomain bluetoothd[502]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Should I be creating a bluetooth directory and perhaps touching the files: input.conf and serial.conf?
In general, no. It's pretty common for code to do something if a file exists, but just go ahead 'as usual' if it doesn't; this kind of message doesn't necessarily mean anything is wrong. I would only start doing that kind of thing if there was obviously something wrong with Bluetooth functionality, and research indicated that these files being 'missing' might have something to do with it.