As i just have moved, i currently lack of internet access (mobile phone is limited to 250mb/month), i had a good look on Glennzos Guide about how to set up a local repo.
To just do installations, the script should work, but requires some lovly testers to confirm it.
Currently i'll have a play to retrieve and intigrate the updates.
Sadly, i currently have either access to internet or
Quote from: jur on January 08, 2010, 10:30:43 PMOK, there is stuff over here now.How do I point AppBrowser to the local mirror? Is it simply a case of filling in the directory? And what do I put for prototcol?You will ne...
I've read a few guides outlining how to setup a local YUM repo, but none of them explicitly stated an answer to my question; If I set up a local YUM repo, does that mean that any CentOS servers which pull from said repo will never be "ahead" of the local YUM repo?
I want to ensure a consistent package distribution across all my servers.
Good catch on the favicon, not sure if it was recently moved or I just hadnt seen the error since I quiet the output. favicon.ico is in the images subdir, here is a corrected version of the script.[code]#!/bin/sh# A script to maintain a private mirr...
Now that I have created my local yum repo I want centos to first look for package under the local repo first and if its not there then its should go and check on the internet. I tried checking the /etc/yum.conf like may be changing some priority level but it doesn't seems to be there.
I've been trying to create a private mirror based on
(the last one is easier to comprehend). But when I tried
# curl -s "https://mirrors.fedoraproject.org/metalink?repo=fedora-17&arch=i386" | grep private
it didn't show anything.
I want to install SQL server 2008 R2 and IIS on same server with a mirroring configuration with principal/mirror/witness setup. Both principal and mirror servers will have IIS and SQL server. My question is twofold:
1) Will additional ram to the principal server be enough for smooth operation? Here we can assume a payload of about 50-100 http requests per second and flat database structure.