A few ideas. 1. What about replacing the directory containing the cron job descriptions in /var with a symbolic link to a directory on the sahred filesystem. 2. You application service start/stop script may modify the cron job description files. This is more complex, as it has to deal with remote nodes that may be down. Regards, Chris Jankowski -----Original Message----- From: linux-cluster-bounces@xxxxxxxxxx [mailto:linux-cluster-bounces@xxxxxxxxxx] On Behalf Of Joseph L. Casale Sent: Wednesday, 31 March 2010 08:29 To: 'Linux-cluster@xxxxxxxxxx' Subject: Cron Jobs Anyone know how I might accomplish keeping cron jobs on the active node? I realize I can create the job on all nodes such that it quietly checks for status, if it's the active node, it runs but it's much easier to maintain my config on the moving fs as I do with httpd/MySQL etc so there exists only one copy. Thanks for any ideas! jlc -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
