10-28-2004
Web site mirroring
I have a unix server running RedHat Linux 9.0. I want to mirror my site on a different server with the same configuration so if the main server goes down, the other server will take over. How is this best accomplished?
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I have a m/c loaded with redhat linux, static IP address and this m/c intern connected to the internet thro leaseline. Now i need to setup a company website has www.abc.xyz.com. What necessary configuration i need to do so that others can view our website.
Thanks
Bache Gowda (5 Replies)
Discussion started by: bache_gowda
5 Replies
2. UNIX for Dummies Questions & Answers
Hiya All,
How can I test my PERL Scripts whilst making my web site?
I'm hoping there is some software out there that emulates a Web Server - without all the hassle of my building/setting up a Web Server from Stratch (Never done anything like that before - my next big project! 8) )
... (7 Replies)
Discussion started by: marty 600
7 Replies
3. AIX
hello
I would like to create an internal web site, but how do i make it with Aix ?
I must to install apache and send my http pages in the declared repertory ?
There are some configuration files to modify ??
thank you (2 Replies)
Discussion started by: pascalbout
2 Replies
4. UNIX for Dummies Questions & Answers
I deleted my subdomains using cPanel. But when i Got to subdomain.site.com it still pulls up my main site .
what can I do ?
thanks (2 Replies)
Discussion started by: upirate
2 Replies
5. AIX
hi guys,
ok this script, i am trying to browse a http site and store the output in a text file ...
when i run the script , i get a http compatibility error.
does any1 have a good solution to contact a http server and save the html in a text file.. i know the result comes with html tags. ... (4 Replies)
Discussion started by: kirantalla
4 Replies
6. Shell Programming and Scripting
I have always wanted to create my own site, I've only had one class about the basics in creating web pages but know i would like to get into more and more detailed info about doing so anyone with alot of experience please help me out.:b: (0 Replies)
Discussion started by: kprescod4158
0 Replies
7. Web Development
Hi All,
I am currently managing a web site. I find that during the peak time period,ie,between 1300hrs to 2100hrs everyday,the response slows down whenever i access the applications hosted by the server.However when i try to access the static content in the web server,it loads quickly.
The... (2 Replies)
Discussion started by: Hari_Ganesh
2 Replies
8. Red Hat
Hi Guys,
Is there any way that we can know whether a website is fullly loaded with Linux command line ?? is there any command in Linux that can achieve that ??
Also,naturally I would also like to get the response code of the particular website/URL that i am testing for ??
Any help would be... (3 Replies)
Discussion started by: Pradeep_1990
3 Replies
rpc.lockd(8) System Manager's Manual rpc.lockd(8)
NAME
rpc.lockd, lockd - Network lock daemon
SYNOPSIS
/usr/sbin/rpc.lockd [-b hostname] [-c] [-d debug] [-g graceperiod] [-h hashsize] [-s] [-t timeout]
OPTIONS
The default behavior will create and bind a socket for each protocol per interface on the system. When the -b switch is specified, one
socket per protocol will be created and bind to the passed IP address. Available only on TruCluster Server systems. This option starts the
clusterwide lock daemon, which helps provide highly available NFS service. Do not use -c directly. Highly available NFS service is config-
ured by default and typically does not require intervention. If you do need to start the clusterwide lock daemon, use the CAA command,
caa_start cluster_lockd.
For more information, see the TruCluster Server Administration manual. Internal Use Only. Use this option only under the direction
of technical support personnel. Causes the rpc.lockd daemon to use the variable graceperiod (in seconds) as the grace period dura-
tion instead of the default value of 15 seconds. Internal Use Only. Causes the rpc.lockd daemon to use the variable timeout (in
seconds) as the interval instead of the default value of 5 seconds to retransmit a lock request to the remote server.
DESCRIPTION
The rpc.lockd daemon processes lock requests that are either sent locally by the kernel or remotely by another lock daemon. The NFS locking
service makes this advisory locking support possible by using the fcntl system call and the lockf subroutine. The rpc.lockd daemon forwards
lock requests for remote data to the server site's lock daemon. The rpc.lockd daemon then requests the status monitor daemon, rpc.statd,
for monitor service. The reply to the lock request is not sent to the kernel until the status daemon and the server site's lock daemon have
replied.
If either the status monitor or server site's lock daemon is unavailable, the reply to a lock request for remote data is delayed until all
daemons become available.
When a server recovers, it waits for a grace period for all client site lock daemons to submit reclaim requests. Client site lock daemons
are notified by rpc.statd of the server recovery and promptly resubmit previously granted lock requests. If a client site's lock daemon
fails to secure previously granted locks at the server site, it sends the signal SIGLOST to all the processes that were previously holding
locks and cannot reclaim them.
SEE ALSO
Commands: rpc.statd(8)
Functions: fcntl(2), signal(2), lockf(3)
rpc.lockd(8)