neysx 05/11/07 11:54:16 Modified: xml/htdocs/doc/en rsync.xml Log: #111691 Improved markup
Revision Changes Path 1.42 +11 -11 xml/htdocs/doc/en/rsync.xml file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/rsync.xml?rev=1.42&content-type=text/x-cvsweb-markup&cvsroot=gentoo plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/rsync.xml?rev=1.42&content-type=text/plain&cvsroot=gentoo diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/rsync.xml.diff?r1=1.41&r2=1.42&cvsroot=gentoo Index: rsync.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/rsync.xml,v retrieving revision 1.41 retrieving revision 1.42 diff -u -r1.41 -r1.42 --- rsync.xml 7 Nov 2005 11:47:06 -0000 1.41 +++ rsync.xml 7 Nov 2005 11:54:16 -0000 1.42 @@ -1,5 +1,5 @@ <?xml version='1.0' encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/rsync.xml,v 1.41 2005/11/07 11:47:06 neysx Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/rsync.xml,v 1.42 2005/11/07 11:54:16 neysx Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/rsync.xml"> @@ -18,8 +18,8 @@ <license/> -<version>1.11</version> -<date>2005-04-24</date> +<version>1.12</version> +<date>2005-11-07</date> <chapter> <title>Hardware Request</title> @@ -283,12 +283,12 @@ <body> <p> -A: netselect was designed to do this for you. If you haven't already run +A: <c>netselect</c> was designed to do this for you. If you haven't already run <c>emerge netselect</c> then do it. Then run: <c>netselect rsync.gentoo.org</c>. After a minute or so netselect will print an IP address. Take this address and use it as the only parameter for rsync with two colons appended to it. eg: <c>rsync 1.2.3.4::</c>. You should be able to find out which mirror that is -from the banner message. Update your /etc/make.conf accordingly. +from the banner message. Update your <path>/etc/make.conf</path> accordingly. </p> </body> @@ -342,7 +342,7 @@ Right now, mirroring our Portage tree requires around 250Mb, so it isn't space intensive; having at least 500Mb free should allow for growing room. Setting up a Portage tree mirror is simple -- first, ensure that your mirror has rsync -installed. Then, set up your rsyncd.conf file to look something like this: +installed. Then, set up your <path>rsyncd.conf</path> file to look something like this: </p> <pre caption="rsyncd.conf"> @@ -431,7 +431,7 @@ </pre> <p> -Your rsyncd.motd should contain your IP address and other relevant information +Your <path>rsyncd.motd</path> should contain your IP address and other relevant information about your mirror, such as information about the host providing the Portage mirror and an administrative contact. After you have been approved as an official rsync mirror your host will be aliased with a name of the form: @@ -460,7 +460,7 @@ following <uri link="/proj/en/infrastructure/mirrors/rsyncd.conf_pl.txt">perl script</uri> which will scan through your rsync log files, pick out IP addresses that have already connected more than <c>N</c> times that day and -dynamically create a rsyncd.conf file, including the offending IP addresses in +dynamically create a <path>rsyncd.conf</path> file, including the offending IP addresses in the 'hosts deny' directive. The following line controls what <c>N</c> equals: </p> @@ -470,9 +470,9 @@ <p> If you use this script, please remember to rotate your rsync log files daily -and modify the script to match the location of your rsyncd.conf file. This -script is tested on Gentoo Linux, but should work suitably on other arches that -support both rsync and perl. +and modify the script to match the location of your <path>rsyncd.conf</path> +file. This script is tested on Gentoo Linux, but should work suitably on other +arches that support both rsync and perl. </p> </body> -- [email protected] mailing list
