Picking up from another thread, I've become intrigued by the following code

Code:

find . -type d -perm -o=w

What's interesting about this command is, if placed in a shell and run as a cron job, it could be 'silent' until something bad happened to your account. I'm wondering whether other commands could be placed together which are 'silent' (i.e. no output) when conditions are normal, but create output, therefore email when things are abnormal. The use of cron would be perfect for this since they could be run once a day and report only when there is an obvious problem. Any thoughts for other commands?

I've looked at this wiki, and it's really cool. But I was specifically thinking of commands that are 'silent' when normally run; therefore no email from a cron job. While these are great scripts and shells, they send output which is likely to be ignored if it comes every day. I was really trying to have an email that is the 'oh crap!' factor; it should not arrive.

I personally like a daily report. I've actually been thinking about taking bobocat's scripts and parts of yours to make a daily report that includes things I might want to look into further. So far tho I haven't done alot other that conceptualize. The trick is in fact to suppress details that are normal, so that when the report arrives it includes only things that need to be looked into/checked further.

(03-17-2012 08:11 AM)LakeRat Wrote: I personally like a daily report. I've actually been thinking about taking bobocat's scripts and parts of yours to make a daily report that includes things I might want to look into further. So far tho I haven't done alot other that conceptualize. The trick is in fact to suppress details that are normal, so that when the report arrives it includes only things that need to be looked into/checked further.

i simplified it for the wiki. i use a series of colours to tag low, med, and high threat changes. most of my report comes greyed out, with just they key potential problems in red. the only way to get to that stage is run a full report and start adding files to the low threat list. it gets better over time.

you can configure git to do the same with the .gitignore file, but it's either ignore or not, whereas I want to monitor. Usually I just open, look for red, and delete....

Yup tried google and dreamhost wiki, but I not really trying to create a code repository am I? This is where git instructions become sort of overwhelming. If I just want to stick my account into a git repository, then it's really not a project. From the dreamhost wiki, there are quick instructions for creating a local project:

I assume this creates a local empty project. From my repository experience (or lack of it) I'm not confident that I want to wade into what would happen is I did this on /home/myuser/. Is this what your suggesting? Then use .gitignore to ignore files you expect to change?