RE: [cobalt-users] raq2, letter to Cobalt

["Lyle Scheer" <lyle@xxxxxxxxxx>]

> > The most simple way I can think of to do this is to disable
> activemonitor.
> > Log in as admin, "su -" and enter the admin password to
> become root, and
> > then type "mv /usr/local/sbin/monitor
> /usr/local/sbin/monitor.saved".
> >
> > It might complain a bit that it can't run activemonitor, but it will
> > complain only to you.
>
> Yes, but won't this stop the (excellent) monitoring service?
> Who will inform
> me about errors then? Will the statistics for the site's disk
> usage still
> work?

Well... yes.  This was the fastest way I could think of...  I did a little
code reading on the perl script /usr/local/sbin/monitor.  It looks like if
you modify all instances of the command "Cobalt::Repair::repair_notify" to
only include the variable ($svr) (ie.
"Cobalt::Repair::repair_notify($svr)"), then it *looks* like it might only
send notices to the admin user.  Since I have basically no real knowledge of
the code and am just guessing, your mileage may vary.  Want to experiment??
Just copy the script to a saved location and make the edit... fill a user to
near quota, run /usr/local/sbin/monitor or wait for a 15 minute interval,
see what happens.  Anyone want to run this experiment?

- Lyle