Well, I successfully managed to get the one line command I wrote to successfully delete all security camera entries older than 100 days.  The directory had grown to about 300GB, encompassing 14 months, so it was time to weed things out a bit.

The command I wrote into an executable file in my personal path was:  find $1 -mtime +100 -exec rm -R {} \;

I saved it in my path and called it prune.  The syntax it was to expect was:  prune <directory to prune with trailing />  I was then to remove all files and directories older than 100 days.

However, it didn’t work.  I scratched my head for awhile, discovered it worked if I manually typed in the find string.  Sometimes I can be such a dumb ass.  I didn’t realize that there already was a prune command in /usr/bin/ for some kind of graphing functions.  So, I renamed MY prune command to shear, and everything works as expected.

Oh, the 300GB of security camera video was reduced to 60GB.  My next step will be to put it in a cron, so that it’s automatic….  Too  bad that I’ll never get that 45 minutes back, LOL.

For those of you familiar with my Linux server, y’all know that I run many custom BASH, Perl, and Python scripts.  We are going to discuss today my iptables firewall script, or actually the fact that I took the time to repair it.   Since upgrading the server to Fedora 20 in September 2014, my firewall script would start fine, but would choke on restarting, reloading, or running it over itself.  The end result would be that the server would sever all ports with the outside, effectively taking it down, needing a reboot to get it back online.  This was a real PITA, since I couldn’t really make any changes to the firewall without reboot.  I thought it was an end result of the OS changing from SysV init scripts to a systemd system.  How wrong I was….  The cause was simply a typo that I made while adding a feature, and a ‘done’ without a ‘while’ and a ‘fi’ without an ‘if’ stopped the script from accepting the restart and reload argument.  Most of the iptables rulesets were created before this typo, so it gave the ‘appearance’ that it was working properly.  Debugging a script of this size is a fairly daunting task, as the main firewall script is a healthy 50 pages, and its configuration file (one of a half dozen helper files) is about 7 pages long.  Since I’ve had a few questions about this firewall, I’ll share it with everybody…..

Download links are only viewable to logged in users.  All the other helper files, as well as these are all available upon request.  If you are a logged in user, and downloading these files, remove the .txt extension from the config and main files….

This is the screen information if the VERBOSE variable is set to 1 (Select the pop-out gadget to see this properly formatted)

Loading...

Taking too long?

Reload document

| Open in new tab

This is the configuration file that allows for easy firewall config.     (Select the pop-out gadget to see this properly formatted)

Loading...

Taking too long?

Reload document

| Open in new tab

This is the MAIN iptables firewall script that should be run at start.  (Select the pop-out gadget to see this properly formatted)

Loading...

Taking too long?

Reload document

| Open in new tab

All in all, it was a fairly productive week off.  I have a few other minor syntax errors to chase down, but the firewall is operating within normal parameters…..