$arr_19 ), array( 3, false, $arr_20, $arr_24 ), array( 2, false, "\" />", $arr_25 ) ) ); ?> $arr_27 ), array( 3, false, $arr_28, $arr_30 ), array( 2, false, "\" />\n\n", $arr_31 ) ) ); ?> array( 2, false, false, $arr_9 ), array( 4, $arr_10, "if", $arr_245, $arr_248 ), array( 2, false, "\n", $arr_249 ) ) ); ?> rr_466 ), array( 4, $arr_467, "if", $arr_482, $arr_484 ), array( 2, false, "\n", $arr_485 ) ) ); ?> TRIGGER HAPPY » Linux Magazine
 

Configuring event-triggered commands with Incron

TRIGGER HAPPY

Author(s):

While cron doggedly keeps to a fixed schedule, Incron monitors directories and runs commands when changes occur.

Cron is a constant companion for admins like myself. My crontab and I have both grown over the years – Crontab has gotten longer, and I’ve gotten wider. Maybe I’m sentimental, but I decided it was time to let my old friend venture out into unexplored territory with a little help from Incron. This cron extension uses an event triggered approach, rather than traditional time-based scheduling, monitoring directories, and running commands when specific changes occur.

Read full article as PDF »

Charlys_Column.pdf  (91.01 kB)
comments powered by Disqus

Visit Our Shop

Trial Subscription

Digital Subscription

Subscribe

Direct Download

Read full article as PDF »

Charlys_Column.pdf  (91.01 kB)

Tag Cloud

Bruce Byfield Gnome KDE Kernel Linux Linux Pro Magazine Open Source Projects Red Hat Ubuntu events foss free software google

News