Dejal Home

Simon icon Simon
Flexible server monitoring

Introducing Simon 5!

Simon version 5 is now available. It is a massive update, introducing a much-requested feature: syncing the Simon data between multiple Macs, plus a Simon Status service, a Link Checker filter, improved Find filter, iMessage and Speak Error notifiers, a new app icon, and much more.

Important: please note that Simon 5 requires a minimum of macOS 10.12 (Sierra), and is a paid upgrade from Simon 4. Purchasers since September 1, 2020 automatically get a version 5 license (that also works in previous versions).

Read the Simon What's New page for details.

test for file permission change?

Wed, 2009-03-25 14:45 — alternapop

Is there a way to tell if a specified files permissions have changed on a remote server?

for example, if the permissions for:
/usr/bin/sudo

change from:
-r-s--x--x root:wheel

to anything else... then alert me.

i see the default option for "file is writable" but am not sure how to accomplish what i need.

thanks

‹ notifier behavior Simon preventing computer shutdown ›
Wed, 2009-03-25 16:15 — David Sinclair
David Sinclair's picture

Re: test for file permission change?

You could check for that by creating a Script-based service that simply contains the following line:

ls -la /usr/bin/sudo

In fact, I've just created this new service for you, called File Attributes; you can download it from the Simon Extras page.

Once that service is added, you can simply create a new test and select it, and enter the /usr/bin/sudo path. Use Smart Change Detection to alert you if that changes: ensure the Smart Change Detection checkbox is enabled, and add a Change notifier.

Thu, 2009-03-26 09:33 — alternapop

thanks!!!

!!!

Thu, 2009-03-26 11:28 — alternapop

usage...

How would this be used to check for a file change on another computer? I am evaluating Simon for purchase and am not terribly experienced with it yet.

For test like HTTP, there is a field for the computer IP. For this service test, I don't see this field as an option.

Thanks!

Thu, 2009-03-26 12:50 — David Sinclair
David Sinclair's picture

Re: usage...

Oh, sorry... I got carried away with the checking attributes part, and overlooked the remote part.

For that, you'd need to SSH into the machine first, then use the command.

I'm not sure that it's possible to include the password as input for ssh in the script, though. So another option would be to duplicate the existing SSH service and add a line to the session to issue the ls -la /usr/bin/sudo command.