On Mon, Jul 26, 2010 at 3:46 PM, Ashish SHUKLA <wahjava...@gmail.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > Sagar Belure writes: > > On Mon, Jul 26, 2010 at 2:37 PM, Ashish SHUKLA <wahjava...@gmail.com> > wrote: > > >> -----BEGIN PGP SIGNED MESSAGE----- > >> Hash: SHA512 > >> > >> Sagar Belure writes: > >> > On Mon, Jul 26, 2010 at 11:15 AM, Sagar Belure < > sagar.bel...@gmail.com > >> >wrote: > >> > >> >> On Fri, Jul 23, 2010 at 7:42 PM, Ashish SHUKLA <wahjava...@gmail.com > >> >wrote: > >> >> > >> >>> -----BEGIN PGP SIGNED MESSAGE----- > >> >>> Hash: SHA512 > >> >>> > >> >>> Vivek Kapoor writes: > >> >>> > On 07/23/2010 06:32 PM, Sagar Belure <sagar.bel...@gmail.com> > wrote: > >> >>> >> Please, bear with me, if I'm not able to properly present my > >> >>> requirement. > >> >>> >> > >> >>> >> There are some 32 and 64 bit ubuntu systems in same network. > >> >>> >> I want only one system(like, one 32 and one 64 bit systems) to be > >> >>> updated > >> >>> >> and upgraded on daily basis. > >> >>> >> And, rest of the systems, to fetch those updated packages before > >> they > >> >>> go > >> >>> >> online and check for new packages. > >> >>> > >> >>> > From what I have understood, you don't want every machine to > download > >> >>> > from the Ubuntu repositories, but only one machine should do the > >> >>> > task. It'll handle 32bit and 64bit without any issues. Use one of > the > >> >>> > following > >> >>> > >> >>> > apt-proxy, apt-cacher, apt-cacher-ng, approx > >> >>> > >> >>> > I started with apt-cacher and faced update issues in long term > use, > >> so > >> >>> > I moved to approx and was happy with it, but newer version > presented > >> a > >> >>> > bit difficulty in the sense that it didn't run its own daemon. So > I > >> >>> > moved onto apt-cacher-ng which has been working well for quite > some > >> >>> > time now. > >> >>> > >> >>> I also used apt-cacher in past and it worked but recent versions had > >> some > >> >>> issues, so I kept the old version pinned on my Debian box. > >> >>> > >> >>> I also tried pkg-cacher[1] because I needed to cache for 'yum' > >> >>> (fedora/centos) > >> >>> also and it worked great since it can cache both 'yum' and 'apt'. > >> >>> > >> >>> References: > >> >>> [1] http://gforge.opensource-sw.net/gf/project/pkg_cacher/frs/ > >> >>> > >> >>> HTH > >> >>> > >> >> > >> >> Thank you all for your responses. > >> >> I got options to look into and your views and experience is really > >> >> valuable. > >> >> > >> > >> > 'apt-cacher-ng' seems to fulfill my requirements. > >> > BTW, is it ,by any chance, possible to set up 'repository-cache' > server > >> > combined for 32 as well as 64 bit systems. > >> > apt-cacher-ng uses /var/cache/apt/archives as repository, and is > >> obviously > >> > different for 32 and 64 bit systems. > >> > >> The file names of the downloaded packages have architecture mentioned in > >> them, > >> so you don't have to worry about 32-bit packages getting overwritten by > >> 64-bit > >> ones. And I used a single repository with apt-cacher and pkg-cacher. > >> > > > Ok. By that, you mean, once I run 'sudo apt-get update ; sudo apt-get > > upgrade' on repository-cache server(Ubuntu 10.04 amd64 desktop), provided > it > > has apt-cache-ng installed, will be able to fetch 32 bit debs too? > > I'm not sure about 'apt-cache-ng', never used it. > > > Or wait > > > How am I supposed to update repository-cache server? > > I used 'apt-cacher' and 'pkg-cacher' both of which act only when they > receive > an HTTP request from one of the clients. They're usually installed as a CGI > binary, or as a standalone web-server. And when they receive a HTTP request > for a file, they perform a cache look-up, and if the file is in cache, they > serve it from cache, otherwise they initiate downloading from the source. > The > first time one of your client updates itself, a 'cache miss' will happen > and > the packages will be downloaded. And for subsequent updates, the packages > are > served from the cache. > Ok. That was very clear and neat. Thank you. AFAICS, installation with 'apt-cacher-ng' on the systems seems the same way, looking at the configuration page by browsing http://localhost:3124/acng-report.html And yes, Vivek seems right, that apt-cacher-ng uses cache located at /var/cache/apt-cacher-ng/_import. Now, I'm hoping importing already downloaded packages from /var/cache/apt/will be all fine. -- Thanks, Sagar Belure Security Analyst Secfence Technologies www.secfence.com _______________________________________________ Ilugd mailing list Ilugd@lists.linux-delhi.org http://frodo.hserus.net/mailman/listinfo/ilugd
