Linux heartbeat resources question

[blast]

Hi all,

i have a scenario where i have 2 front ends that receive traffic (http server) and should run some scripts in crontab, some of the scripts should just being running by 1 server at a time (active one) and others should run on both.

Regarding the http like is load-sharing i think i cant use heartbeat, right? heartbeat is just for active-stanby or can we use to a active-active as watchdog? i have a cisco css to load sharing the http, and i can make a watchdog script to the apache.

Regarding the cron crontrol i was thinking to make a script that replaces the crontab file to whatever is the correct one. When the heartbeat start what parameter is sent to the script that are resources? a start if active node and nothing if is the standby?allways start?how should i config the haresources to do it? what is the best way?

i have other situation that is making a nfs server in solaris 10, i have 2 servers with shared disks ( sun array), can i use heartbeat to this too? it is possible to make it in such way that if i had i failover in nfs server the clients doesn't need to reconnect?

Its a long post...sorry!
thanks!!

[mzainal]

Hi,

Do you search in Google? Perhaps you got some answer before post here. Or you may try and post here.


Regrads,
Banie

[blast]

yes i did some search...didn't find any straightforward way to do it.


crontab:
i found rcron that it seems to do more or less what i want we can configure like this:

# a local only job
12 11 * * * myjob1
# a rcron handled job
14 11 * * * rcron myjob2

rcron will check a file for passive/active word i run the script if active is found, but we still have to do the heartbeat and updated the status file. a "problem" here is that the cron runs lots of times without need (in passive node). Anyone used this rcron? other way is making a script that changes the crontab file, but i dont know if its a good way of doing it..


NFS server: i found that is possible but that probably i will have some errors installing the sources...
i dont have acess to the servers, i m mouting a testbed (VM) to try to install the heartbeat into solaris. in google almost all config examples are for apache or nfs but with drdb not with a shared disks, neverless i found something like this (haresources):

server1 192.168.1.1 Filesystem::/dev/sda1::/mnt::ext3 nfslock nfs

server1 - primary server
192.168.1.1 - ha ip
Filesystem - resource type
/dev/sda1 - device
/mnt - mount point
ext3 - FS type
nfslock nfs - to start NFS server

Is this correct? if so how the heartbeat knows how to mount/umount the FS? will this permit a transparent failover to the clients?


Thanks!