03-30-2009
Keep in mind that clustering does not mean high availability. CLustering is sharing resources with multiple machines. What you need to look into is syncing and failover mechanisms so that 2 web servers at different locations are mirrored copies so that if one goes down, dns is routed to the other server.
I am kind of down this route myself and learning as I go. Be nice to utilize an HA consultant as trial and error can be costly.
3 More Discussions You Might Find Interesting
1. Solaris
HI Experts,
Could some one help me in configuring high availability zone on Sun Cluster
Reg: Sudhan (3 Replies)
Discussion started by: sudhan143
3 Replies
2. Red Hat
How can we implement a service in HA, which in not available in HA.
like sldap or customize application.
Requirement Details.
NODE1 service slapd is running.(Require)
NODE2 service slapd is running.(Require)
on both the node replication is happening.
Now here requirement is need... (2 Replies)
Discussion started by: Priy
2 Replies
3. Red Hat
What's the best way clusters for Storage at some point? (The way that data is the same in all parts)
To set up a Web server cluster is the logical way?!
Cluster database and Storage and then by keepalived + HA cluster will be communicated?
Or, there a better solution? (For about 4 points)
Thank... (0 Replies)
Discussion started by: mnnn
0 Replies
LEARN ABOUT DEBIAN
make_sockdfr
MAKE_SOCKDFR(8) System Manager's Manual MAKE_SOCKDFR(8)
NAME
make_sockdfr - Generates frozen route file for SOCKS server
SYNOPSIS
make_sockdfr [infile [outfile] ]
DESCRIPTION
make_sockdfr reads in a plain-text route file for the SOCKS server and produces a frozen route file as the output.
Both arguments are optional. The default for infile is /etc/sockd.route; the default for outfile is /etc/sockd.fr. You may specify infile
while omitting outfile, but you cannot specify outfile without also speficying infile.
The contents of the frozen route file is essentially the memory image of the parsed input file. Using the frozen route file can reduce the
start-up delay of the SOCKS server program since it no longer has to parse the file contents.
When the SOCKS server starts, it always looks for the frozen route file /etc/sockd.fr first. If that file is not found, it then tries to
use the plain-text route file /etc/sockd.route. If you use frozen route file, you must remember to run make_sockdfr every time after you
modify the plain-text file or the SOCKS server will continue to use the frozen version of a previous route file.
To find out the contents of a frozen route file, use dump_sockdfr.
FILES
/etc/sockd.fr, /etc/sockd.route
SEE ALSO
dump_sockdfr(8), sockd.fr(5), sockd.route(5)
AUTHOR
Ying-Da Lee, yingda@esd.sgi.com or yingda@best.com
May 6, 1996 MAKE_SOCKDFR(8)