[kwlug-disc] if {other command done} then...

Raul Suarez rarsa at yahoo.com
Thu Jul 8 11:29:53 EDT 2010


At work we use a batch control application but sometimes, when we need to go across platforms (or business partners) we rely on trigger files.

We would have a watcher job that triggers the next steps as soon as the file is received.

It is a fairly simple and fail proof method. Under Linux you can use inotify

http://www.linuxjournal.com/article/8478

Raul Suarez

Technology consultant
Software, Hardware and Practices
_________________
Twitter: rarsamx
http://rarsa.blogspot.com/ 
An eclectic collection of random thoughts


--- On Thu, 7/8/10, Insurance Squared Inc. <gcooke at insurancesquared.com> wrote:

> From: Insurance Squared Inc. <gcooke at insurancesquared.com>
> Subject: [kwlug-disc] if {other command done} then...
> To: "KWLUG discussion" <kwlug-disc at kwlug.org>
> Received: Thursday, July 8, 2010, 11:00 AM
> I push my webserver and desktops each
> night over to a backup server using rsync by running a
> script on the desktops/webserver.  I've got that set
> for 1am.
> Then at about 3 am on the backup server I run a script that
> compresses the backups and dates it.
> 
> Is there an easy way to ensure the script on the backup
> server doesn't start running until the backups are
> done?  Or would I be better forcing the compression and
> dating right from the desktop script?
> 
> g.
> 
> 
> _______________________________________________
> kwlug-disc_kwlug.org mailing list
> kwlug-disc_kwlug.org at kwlug.org
> http://astoria.ccjclearline.com/mailman/listinfo/kwlug-disc_kwlug.org
> 





More information about the kwlug-disc_kwlug.org mailing list