<div dir="ltr">yeah - bug in my script. Private mirrors don't get crawled (unless they're also on Internet2 and have set the i2_clients flag), so don't need an rsync module. I'll fix the nag script.<div><br>
</div><div>Thanks,<br>Matt</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Jul 16, 2013 at 8:23 AM, Brian Long (brilong) <span dir="ltr"><<a href="mailto:brilong@cisco.com" target="_blank">brilong@cisco.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Matt et al,<br>
<br>
I received emails regarding the rsync URLs even though I have my mirror marked as private. There is no way for MirrorManager infrastructure to reach my internal server via rsync or http. :)<br>
<br>
Could you alter future nag emails to look for the "private" flag and disregard the lack of rsync URLs?<br>
<br>
Also, part of the email said the following:<br>
"Host <a href="http://rtp-linux.cisco.com" target="_blank">rtp-linux.cisco.com</a> Category Fedora Linux has no up-to-date<br>
directories. Check that your Category URL points to<br>
pub/fedora/linux. * Consult the crawler logs and check your<br>
report_mirror.conf."<br>
<br>
I fixed a report_mirror.conf snafu and re-ran report_mirror.<br>
<br>
Thank you.<br>
<span class="HOEnZb"><font color="#888888"><br>
/Brian/<br>
--<br>
Brian Long | |<br>
Research Triangle Park, NC . | | | . | | | .<br>
' '<br>
C I S C O<br>
</font></span><div><div class="h5"><br>
On Jul 15, 2013, at 1:42 PM, <a href="mailto:Matt_Domsch@dell.com">Matt_Domsch@dell.com</a> wrote:<br>
<br>
> Great question! Yes! When you create a URL in the MirrorManager web admin interface, you can select the box "for other mirrors only". Such URL will then _not_ appear on the publiclist pages, and will not appear in metalinks at all. The crawler will be able to use it, but it won't be shown to anyone else.<br>
><br>
> If you need to, on your side in your rsync modules, you can restrict to <a href="http://209.132.181.0/24" target="_blank">209.132.181.0/24</a> which will allow the MirrorManager servers in Fedora Infrastructure to hit your URL, but no one else.<br>
><br>
> Thanks,<br>
> Matt<br>
><br>
><br>
> --<br>
> Matt Domsch<br>
> Distinguished Engineer, Technology Strategist<br>
> Dell | Office of the CTO<br>
><br>
><br>
> -----Original Message-----<br>
> From: <a href="mailto:mirror-list-d-bounces@redhat.com">mirror-list-d-bounces@redhat.com</a> [mailto:<a href="mailto:mirror-list-d-bounces@redhat.com">mirror-list-d-bounces@redhat.com</a>] On Behalf Of Mark McKinstry<br>
> Sent: Monday, July 15, 2013 9:57 AM<br>
> To: A private discussion group for official mirrors of <a href="http://ftp.redhat.com" target="_blank">ftp.redhat.com</a><br>
> Subject: Re: rsync targets for Fedora content please<br>
><br>
> On 07/12/2013 06:27 PM, Matt_Domsch@Dell.com wrote:<br>
>> Please consider adding an rsync module for each Category of content<br>
>> you carry, and add the URLs into MirrorManager.<br>
><br>
> Is there a way to only allow rsync access for the MirrorManager<br>
> server(s) and not be listed as a public rsync mirror?<br>
><br>
><br>
> --<br>
> Mark McKinstry<br>
> Nexcess - Beyond Hosting<br>
> 21700 Melrose Ave.<br>
> Southfield, MI 48075<br>
> Phone: +1.866.639.2377<br>
> Fax: +1.248.281.0473<br>
> <a href="http://twitter.com/nexcess" target="_blank">http://twitter.com/nexcess</a><br>
><br>
> --<br>
><br>
> --<br>
<br>
<br>
</div></div>--<br>
<br>
</blockquote></div><br></div>