Hello:
I'm upgrading mon from an old version of mon to .99.2 on tru64. We are
using perl 5.6.0.
Everything is fine, except that for some reason I _cannot_ get mon to read
alerts in alert.d directory. Then it begins to even refuse to see the
mail.alerts which are untouched.
Did something in
--On Tuesday, September 24, 2002 8:55 AM -0400 Andy Diller
[EMAIL PROTECTED] wrote:
Why is mon refusing to acknowledge these alerts which is plainly there in
the alert.d directory?
My first guess would be a permissions problem. Either the alerts aren't
executable, or they aren't readable
Ok, they needed the execute bit set. Sigh..
thanks!
--On Tuesday, September 24, 2002 9:56 AM -0400 David Nolan
[EMAIL PROTECTED] wrote:
My first guess would be a permissions problem. Either the alerts aren't
executable, or they aren't readable by the user your mon server is
running
Check the permissions on the full path to the alert.d directory
i.e.
ls -ld /usr/
ls -ld /usr/local/
ls -ld /usr/local/lib/
ls -ld /usr/local/lib/mon/
ls -ld /usr/local/lib/mon/alert.d/
ls -l /usr/local/lib/mon/alert.d/mail.alert
And make sure that the user that runs mon has rights to read and
William Bartholomew writes:
Having very little experience with Perl, what is the best way to start
mon as a non-root user under rc.local (if this is indeed possible).
In rc.local, something like:
su MONUSER -c /usr/local/mon/mon OPTIONS ARGUMENTS
MONUSER obviously needs access to the mon directory and all
subdirectories, does it need any special permissions to the perl or perl
library directories or will the defaults suffice?
Regards,
William Bartholomew
Internet Developer
Orli-TECH Pty Ltd
Your Innovative e-Business Partner
Web:
William Bartholomew writes:
MONUSER obviously needs access to the mon directory and all
subdirectories, does it need any special permissions to the perl or perl
library directories or will the defaults suffice?
The defaults are sufficient. I run mon this way (as a regular
user) - it needs
On Tue, 24 Sep 2002 13:25:46 -0700 (PDT), Jim Trocki [EMAIL PROTECTED] said:
yeah, well -w carps on this:
my %h;
die if ($h{stuff} ne );
It's true that you have to adjust your code to avoid triggering warnings.
I find the adjustment worth it, but opinions differ.
If you already
