> -Original Message-
> From: linux-cluster-boun...@redhat.com
[mailto:linux-cluster-boun...@redhat.com]
> On Behalf Of Joseph L. Casale
> Sent: Tuesday, March 30, 2010 5:29 PM
> To: 'Linux-cluster@redhat.com'
> Subject: [Linux-cluster] Cron Jobs
>
>
On Tue, 30 Mar 2010 21:28:46 +, "Joseph L. Casale"
wrote:
> 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 co
vices on the node after reboot.
> # In fact the node will have all the crontabs from the moment it
> # crashed augmented by changes caused by any sevices restarted
> # on it after its reboot.
> #
> # What is really needed is another script - run on boot from
> #
at.com] On Behalf Of Joseph L. Casale
Sent: Wednesday, 31 March 2010 09:42
To: 'linux clustering'
Subject: Re: [Linux-cluster] Cron Jobs
>1.
>What about replacing the directory containing the cron job descriptions in
>/var with a symbolic link to a directory on the sahred filesystem
On Wed, Mar 31, 2010 at 12:42 AM, Joseph L. Casale
wrote:
>>1.
>>What about replacing the directory containing the cron job descriptions in
>>/var with a symbolic link to a directory on the sahred filesystem.
>
You could use a shared filesystem mounted on /etc/cron.d to keep cron
scripts, and a c
>1.
>What about replacing the directory containing the cron job descriptions in
>/var with a symbolic link to a directory on the sahred filesystem.
yeah, my first inkling was to symlink /etc/cron.daily but that breaks so much
existing functionality.
>2.
>You application service start/stop scrip
remote nodes that may be
down.
Regards,
Chris Jankowski
-Original Message-
From: linux-cluster-boun...@redhat.com
[mailto:linux-cluster-boun...@redhat.com] On Behalf Of Joseph L. Casale
Sent: Wednesday, 31 March 2010 08:29
To: 'Linux-cluster@redhat.com'
Subject: [Linux-clu
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
