Date: Mon, 30 Apr 2007 19:24:29 +0200 From: Michael Nottebrock <lofi@freebsd.org> To: kde@freebsd.org Cc: gnome@freebsd.org, David Southwell <david@vizion2000.net> Subject: Re: [kde-freebsd] var/log/messages umass da0 >6 how to stop? Message-ID: <200704301924.33576.lofi@freebsd.org> In-Reply-To: <200704301001.08628.david@vizion2000.net> References: <200704300301.22102.david@vizion2000.net> <200704301832.12814.lofi@freebsd.org> <200704301001.08628.david@vizion2000.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart2113207.olKnu7f2gX Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Monday, 30. April 2007, David Southwell wrote: > On Monday 30 April 2007 09:32:07 Michael Nottebrock wrote: > > On Monday, 30. April 2007, David Southwell wrote: > > > [ Device probing message spam ] > > > [...] > > > > > > Can anyone help further? > > > > The short explanation: Those messages are generated by the kernel and > > triggered by the continuous polling of hald for media. The correct fix > > would be making the kernel less verbose - I don't know if anyone is > > working on that at the moment. > > > > There is very little you can do about it as it is - you can make sure to > > configure newsyslog so that /var/log/messages and its backup copies don= 't > > overflow your /var filesystem by editing /etc/newsyslog.conf and you can > > configure syslogd to write messages you care about to separate logs so > > they don't get lost too quickly in the kernel spam. > > > > Cheers, > > Thank you Michael. > > I gather, from what you say, that there are no configuration options for > hald to prevent this happening. I think there is, probably by generating some additional policy XML files, = but=20 I'll pass on that question (how to prevent hal from polling specific=20 devices/classes of devices/all devices) to the HAL maintainers at gnome@=20 (cc'd). Preventing hald from polling the devices would more or less defeat its purp= ose=20 though - it exists and runs to detect media insertions/changes and pass the= m=20 on the desktop applications (via DBUS) so they can react to it - like=20 displaying an icon your desktop. Perhaps there is a way to lengthen the sca= n=20 interval, perhaps even specific to certain devices or certain device classe= s? Like I said, the real fault in my opinion is with the kernel, which is simp= ly=20 way too verbose and lacks means of making it less so. Complaining about tha= t=20 on current@freebsd.org might help, but only in the medium term (it takes a= =20 while for changes to happen and trickle down into FreeBSD releases). Cheers, =2D-=20 ,_, | Michael Nottebrock | lofi@freebsd.org (/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org \u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org --nextPart2113207.olKnu7f2gX Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (FreeBSD) iD8DBQBGNiZOXhc68WspdLARAl+bAJ9p5mlFGLIG7HehrDjPsJ4BYx/O1QCeLJ5K 8cOVnLUbjGX0flAvn7wXQ3c= =/YyY -----END PGP SIGNATURE----- --nextPart2113207.olKnu7f2gX--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200704301924.33576.lofi>