Date: Thu, 29 Mar 2007 07:53:01 -0500 From: Eric Anderson <anderson@centtech.com> To: Maksim Yevmenkin <maksim.yevmenkin@gmail.com> Cc: "freebsd-bluetooth@freebsd.org" <freebsd-bluetooth@freebsd.org> Subject: Re: bthidd filling my logs Message-ID: <460BB6AD.4060306@centtech.com> In-Reply-To: <bb4a86c70703281220w61cd9252mb7c35f7121a3b9e@mail.gmail.com> References: <46096375.1050301@centtech.com> <bb4a86c70703280939h19ff2bb0xbf7a032e54033ec5@mail.gmail.com> <460AA7CB.6050500@centtech.com> <bb4a86c70703281220w61cd9252mb7c35f7121a3b9e@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/28/07 14:20, Maksim Yevmenkin wrote: > On 3/28/07, Eric Anderson <anderson@centtech.com> wrote: >> On 03/28/07 11:39, Maksim Yevmenkin wrote: >>> On 3/27/07, Eric Anderson <anderson@centtech.com> wrote: >>>> Ok, I'm getting tired of my logs rolling because of these messages: >>>> >>>> Mar 27 13:31:05 neutrino bthidd[956]: Could not connect to >>>> 00:0c:55:12:ba:ae. Host is down (64) >>>> Mar 27 13:31:30 neutrino bthidd[956]: Opening outbound session for >>>> 00:0c:55:12:ba:ae (new_device=1, reconnect_initiate=1) >>>> >>>> Can we mute those, or show them only the first time, or something? They >>>> pop up every 30 seconds. >>> if you are not using 00:0c:55:12:ba:ae device, just remove it from >>> your bthidd.conf >> >> The thing is, I do use it. Just not all the time. I use one mouse at >> the office, and another one when traveling, at home, etc. That's what's >> nice about this - I can configure 10 if I want, and use whichever one >> is near me without carrying them all around. > > the thing is, you did not configure it :) i.e. bthidd thinks its a new > device. usually mice and keybords have reconnect initiate to 1, so > bthidd does not try to contact them Hmm - seems that at some point recently during an upgrade or crash, I think I may have lost the db or some part of it. I just powered on my mouse, and once it initiated, the messages are gone. So, you are 100% correct. >> The fact is that it is really useless to log it every 30s that it can't >> see it. Logging it once on initial connect, or for the first time after >> a previously running connection was disconnected is however useful. >> I'm not sure the right way to patch it though, I've already been looking >> at it. > > well, yes, i agree. i will look into it when i have spare time > > max Thanks again, and sorry for the noise.. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology An undefined problem has an infinite number of solutions. ------------------------------------------------------------------------
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?460BB6AD.4060306>