Thanks for all replay.
What i need exactly is How to make the Cron centralized and NOT how to make it not running on backup node.
Without having a centralized cron I need to edit the cron file in all nodes.This is the difficulty which I am facing.
Any suggession will be valuable.
On Tue, 09 May 2006 Nick Burrett wrote :
>saju john wrote:
>>Is there any way to make a centalized cron while using Redhat HA cluster with Sahred storage. I mean to put the crontab entry for a particular user on shared storage, so that when the cluster shifts, on the other node cron should read from the cron file in shared storage.
>If you want some form of high availability cron, you could try to leverage the Condor application to suit your needs. If you link your cron applications against the Condor libraries, then you get process check pointing and all sorts of other wonderful stuff.
>>This setup has the advantage that we don't need to manullay update the cron entry in both nodes.
>>b) Soft link the cron directory in /var/spool to /path/to/shared/storage/cron. This is working till the cluster shift. The cron is getting dead when the cluster shifts as it lose the /var/spool/cron link's destination driectory which will be mapped to the other node
>You need to add in a heartbeat trigger. The cron daemon runs on one server only. When that server goes offline, then start the cron daemon on the backup server. This is a terrible solution though.