On Fri, Sep 05, 2008 at 09:42:44AM +0200, Morten Brekkevold wrote:

...

# The e-mail address of the NAV system administrator. All cron error # messages will be sent to this address. ADMIN_MAIL=systjc@ecs.soton.ac.uk

I suggest you add another option

CRON_MAIL=....

so you can still have an admin contact on the NAV system/web view, but direct cron stuff easily to nowhere. Or maybe a variable for just the Cricket cron outputs if NAV cron output is useful :)

The ADMIN_MAIL setting has no relation to what is displayed as a contact anywhere on the NAV web; that's just regular HTML configured by the administrators in the webfront config/template files.

The point of ADMIN_MAIL is to have something to fall back to if all other methods of getting attention fail.

Ah my bad, I assumed the contact info that by default is bottom right of the NAV home was take from there. But it isn't :)

One thing you can do is edit /etc/nav/cron.d/cricket and redirect everything from the collect-subtrees cricket command to /dev/null and then run "nav restart cricket" to reinstall the cron snippet into navcron's crontab.

If you do that, you can still find cricket's messages in its log files. It's default loglevel is more verbose than just error messages, so you'd either have to grep the logs for errors or adjust the loglevel in cricket-conf.pl.

Nice tip, thanks.