I know, it's a lot simpler to put it right quietly with a cron, or even
part of the update process, and I have considered this, but as always, it's
political.
The client wants it this way.
With their previous installation of Xymon, I had it working, so I know it's
possible.
However, it was all lost in a catastrophic system failure (with no backups).
I rebuilt Xymon on a new server for them, but and I can't a hell remember
how I configured the directory monitoring.
Regards
Vernon
On 2 December 2014 at 22:26, Steve Coile <user-a2e2f9aff0d1@xymon.invalid>
wrote:
What's the point of monitoring for it? To let you know you need to
correct them? If that, why not just put a cron job in place that sets them
properly?
--
*Steve Coile*Senior Network and Systems Engineer, McClatchy Interactive
<http://www.mcclatchyinteractive.com/>;
Office: XXX-XXX-XXXX | Mobile: XXX-XXX-XXXX | Fax: XXX-XXX-XXXX
On Tue, Dec 2, 2014 at 2:28 AM, Vernon Everett <user-b3f8dacb72c8@xymon.invalid>
wrote:
Hi guys
I have a *directory *on a client system, and it needs to have permission
of 777
From time to time, automated software updates sets it to 770.
I am looking for a way to check this, and alert when permissions are not
as they should be.
Any advice appreciated.
Regards
Vernon
--
"Accept the challenges so that you can feel the exhilaration of victory"
- General George Patton
--
"Accept the challenges so that you can feel the exhilaration of victory"
- General George Patton