View Single Post
Reflektorfalke's Avatar
Posts: 597 | Thanked: 490 times | Joined on Dec 2009 @ Germany
#27
Originally Posted by mirakels View Post
To analyse failures I think it is very vsaluable to also get syslog output. Thsi can show what obexd is doing. It shows things you won't see in the hcidump log.

To use syslog:

apt-get install sysklogd

and add the --debug optuon to your obexd command invocation.

sysklogd will create a file /var/log/syslog

After your test copy this file to some other location (do not delete the original)
and edit out the relevant part. so you can post it alongside the hcidump log.
Hi Mirakels!

Thankx a lot for your support!
Would it be possible to give us a more detailed guideline how to enable the --debug option, one that even Linux-noobs will understand
I think it would be nice to have this in the summary in the first post...