[kde-freebsd] var/log/messages umass da0 >6 how to stop?

[Joe Marcus Clarke]

On Mon, 2007-04-30 at 19:24 +0200, Michael Nottebrock wrote:
> 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 
> I'll pass on that question (how to prevent hal from polling specific 
> devices/classes of devices/all devices) to the HAL maintainers at gnome@ 
> (cc'd).

Polling can be disabled on a per device basis.  It has been discussed on
freebsd-gnome in the past.

> 
> Preventing hald from polling the devices would more or less defeat its purpose 
> though - it exists and runs to detect media insertions/changes and pass them 
> on the desktop applications (via DBUS) so they can react to it - like 
> displaying an icon your desktop. Perhaps there is a way to lengthen the scan 
> interval, perhaps even specific to certain devices or certain device classes?
> 
> Like I said, the real fault in my opinion is with the kernel, which is simply 
> way too verbose and lacks means of making it less so. Complaining about that 
> on current at freebsd.org might help, but only in the medium term (it takes a 
> while for changes to happen and trickle down into FreeBSD releases).

This is where the real solution lies.  If polling is disabled for this
device, then it will be treated like a floppy disk in that you will need
vfs.usermount=1, an entry in /etc/fstab, and a user-owned mount point in
order to mount media.  If the kernel were less verbose about missing
media cases, then there would be no reason for users to complain.
current@ would be a good list on which to raise this issue.

Joe

-- 
PGP Key : http://www.marcuscom.com/pgp.asc
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 187 bytes
Desc: This is a digitally signed message part
Url : http://mail.kde.org/pipermail/kde-freebsd/attachments/20070430/7ec24b0e/attachment.pgp