Thank you to everyone who responded back in the mailing list and to those who offered advice offline. I appreciate all of you.
I am using cygwin to run rsync and it works beautiully. As many have pointed out, since I am using IIS instead of apache the symlinks and hard links won't work. I expected this and am not too concerned. If this causes problems for users who may access me as a mirror I may port the web hosting portion on to a Linux box. The only reason I don't just run a CentOS server for all of this is that I cannot get funding to buy hardware specifically for this purpose. I am hosting the files on a massive DFS root which is rooted on a M$ Server 2003 box. There is no changing that, and I don't really need to anyway.
My server is (and has been) up and running for a couple of days now with no problems. I will be limiting the scope of what I am mirroring to all i386 version 3.0 and up. I have "Scheduled Tasks" working perfectly. Now I just need time to get all the goods over here.
Once I am confident that the mirror is working (and noone objects too harshly to publishing me with symlinks and hardlinks not working) I will post my server to the newsgroup.
-- Ty R. Mote
-----Original Message----- From: centos-mirror-bounces@centos.org [mailto:centos-mirror-bounces@centos.org] On Behalf Of Mote, Ty R. Sent: Thursday, September 14, 2006 9:42 AM To: centos-mirror@centos.org Subject: [CentOS-mirror] Rsync on Windows & Mirroring Best Practices
Greetings,
I am new to the idea of mirroring, but I want to support CentOS by sharing some of my bandwidth. I have read over the CentOS Mirroring HowTo and set everything up as it states. However, the instructions suggest that the reader contacts the mailing list for additional instructions for using "lock files", etc.
I have Rsync working on my Windows Server 2003 box in daemon mode. Everything appear to be functional. I would assume that I can now schedule updates using "Scheduled Tasks" in place of CRON. Is this accurate?
Lastly, I would like to mirror only the i386 & i386-64bit data (including DVDs, and SRPMs). Would anyone have advice to lend for doing that?
Thank you for your assistance!
-- Ty R. Mote Assistant Director of Technology Krum Independent School District http://www.krumisd.net O: 940/482-6000x283 C: 806/290-1313 F: 940/482-9951 ty.mote@krumisd.net
_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
Mote, Ty R. wrote:
Thank you to everyone who responded back in the mailing list and to those who offered advice offline. I appreciate all of you.
I am using cygwin to run rsync and it works beautiully. As many have pointed out, since I am using IIS instead of apache the symlinks and hard links won't work.
hard links is ok, its just going to use more space on your side - since you get multiple copies of each file.
but the symlinks is worrying - your mirror will effectively be non usable, unless the $releasever/ matching symlinks work and are moved around in sync with the centos msync network.
I am open to suggestions from people on how we might be able to work around this, nothing obvious comes to my mind. except that the entire latest version tree be also copied under the $releasever/ tree. effectively doubling the entire mirror size.
Karanbir Singh wrote:
but the symlinks is worrying - your mirror will effectively be non usable, unless the $releasever/ matching symlinks work and are moved around in sync with the centos msync network.
I am open to suggestions from people on how we might be able to work around this, nothing obvious comes to my mind. except that the entire latest version tree be also copied under the $releasever/ tree. effectively doubling the entire mirror size.
Does IIS have something like apache's Alias directive? If so, filesystem symlinking could be translated to webserver aliasing, same thing done in a different way.
Z
There isn't anything native. You can do virtual directories within IIS but not programmatically (again, natively) so it would be a hassle.
I'll just plan on putting up a centos box (using some spare parts from my girlie robot) and host the mirror that way. This only means it will be a few weeks before I come online... no big deal.
-- Ty R. Mote Assistant Director of Technology Krum Independent School District http://www.krumisd.net 940/482-6000x283 ty.mote@krumisd.net
________________________________
From: centos-mirror-bounces@centos.org on behalf of Zenon Panoussis Sent: Sat 2006-09-16 01:06 To: Mailing list for CentOS mirrors. Subject: Re: [CentOS-mirror] Rsync on Windows & Mirroring Best Practices
Karanbir Singh wrote:
but the symlinks is worrying - your mirror will effectively be non usable, unless the $releasever/ matching symlinks work and are moved around in sync with the centos msync network.
I am open to suggestions from people on how we might be able to work around this, nothing obvious comes to my mind. except that the entire latest version tree be also copied under the $releasever/ tree. effectively doubling the entire mirror size.
Does IIS have something like apache's Alias directive? If so, filesystem symlinking could be translated to webserver aliasing, same thing done in a different way.
Z
_______________________________________________ CentOS-mirror mailing list CentOS-mirror@centos.org http://lists.centos.org/mailman/listinfo/centos-mirror
-
Karanbir Singh -
Mote, Ty R. -
Zenon Panoussis