Best bet is probably to insert a call to the script at the end of your rc.local file, probably with a & at the end of the command line, and then have the script start with a "wait 300" to give you the five minute wait you're looking for.
On Mon, 27 Jan 2003, Robert Adkins wrote: > Hello All, > > I have a script that I need to run at startup that will wait for a > significant amount of time and then execute on the servers. > > Basically, I need both servers to run this script at boot and mount up > drives on the other server, in cases of power outages. What I am thinking > about doing is putting a line into the rc.sysinit file at the end of the > file that will run the script and put it into the background. > > The script would then wait about 5 minutes, which is a little longer > then it takes for the servers to reboot, then it will attempt to mount > the NFS share on the other server. After that, it will attempt to list > the contents, if it receives '0' then it will rerun, waiting another 5 > minutes or so (perhaps adding up a counter and logging the attempts each > time, with a date stamp) until it fails at least 3 or 4 times. After that > point, the script will E-mail the admin and exit. > > Basically, what I am asking is whether or not this is a good place to > put the launching of this script? > > Regards, > Robert Adkins II > IT Manager/Buyer > Impel Industries, Inc. > Ph. 586-254-5800 > Fx. 586-254-5804 > > > > -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org:2000 -- redhat-list mailing list unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe https://listman.redhat.com/mailman/listinfo/redhat-list
