On 2010-01-14, at 03:14, Al Viro wrote:
I am not going to apply that. For one thing, printk is improper
mechanism
for "observing [normal] operations". Vague references to "enterprise
users" wanting that do not constitute a valid rationale.
What's more, there is absolutely no point in taking care to have
mount(2)
spew something in log when explicitly asked to do so; caller can
bloody
well do it itself. From userland.
Sure, it is _possible_ to do this, but you miss the fact that there
are many system monitoring tools that already scrape /var/log/messages
and integrate with event managers. What you are suggesting is that
every such tool implement an extra, completely ad-hoc mechanism just
for monitoring the mount/unmount of filesystems on Linux. That
doesn't make sense.
Conversely, adding a new monitor for a message in /var/log/messages is
simply a matter of adding a scanf() format string to their existing
list of format strings - a 5-minute exercise for a junior sysadmin.
Cheers, Andreas
--
Andreas Dilger
Sr. Staff Engineer, Lustre Group
Sun Microsystems of Canada, Inc.
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
