Perhaps not a bug or maybe requires a feature request.* I'm attempting to host my /var/cache/yum directory on a NFS to share with several other machines.* I've tired doing with by simply changing the location in yum.conf and also by creating a symbolic link to the directory with no succes, yum just stops here with no error:


[root@localhost ~]# yum -y update
Loaded plugins: fastestmirror, refresh-packagekit
Determining fastest mirrors
** livna: rpm.livna.org
** fedora: mirror.anl.gov

** updates-newkey: mirror.steadfast.net
** updates-newkey-source: mirror.steadfast.net
** updates: mirror.steadfast.net

livna********************************************* ************** | 2.1 kB**** 00:00****
fedora******************************************** ************** | 2.4 kB**** 00:00****
updates-newkey******************************************** ****** | 2.3 kB**** 00:00****

updates-newkey-source******************************************* | 2.1 kB**** 00:00****
updates**

It will sit here pretty much forever without output, at least for the ~15 I waited, but did create the following directory structure:


[root@localhost ~]# ls -R /main/uploads/yum
/main/uploads/yum:
fedora* livna* timedhosts.txt* updates* updates-newkey* updates-newkey-source

/main/uploads/yum/fedora:
cachecookie* mirrorlist.txt* packages* primary.sqlite* repomd.xml


/main/uploads/yum/fedora/packages:

/main/uploads/yum/livna:
cachecookie* packages* primary.sqlite* repomd.xml

/main/uploads/yum/livna/packages:

/main/uploads/yum/updates:
cachecookie* mirrorlist.txt* packages* primary.sqlite* repomd.xml


/main/uploads/yum/updates/packages:

/main/uploads/yum/updates-newkey:
cachecookie* mirrorlist.txt* packages* primary.sqlite* repomd.xml

/main/uploads/yum/updates-newkey/packages:

/main/uploads/yum/updates-newkey-source:

cachecookie* mirrorlist.txt* packages* primary.sqlite* repomd.xml

/main/uploads/yum/updates-newkey-source/packages:
[root@localhost ~]#
Is this intentional or possibility a bug?

I realize creating a yum repo is fairly easy but I was hoping to only cache the packages that my machines use, not the entire repo.


Any help or suggestions?

Thanks
Andy


--
projecthuh.com
All of my bits are free, are yours? *Fedoraproject.org


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Thu, 2008-09-25 at 19:10 -0400, Dr. Diesel wrote:
> Perhaps not a bug or maybe requires a feature request. I'm attempting
> to host my /var/cache/yum directory on a NFS to share with several
> other machines. I've tired doing with by simply changing the location
> in yum.conf and also by creating a symbolic link to the directory with
> no succes, yum just stops here with no error:

What verison?
What does strace say yum is doing?
The sqlite documentation generally recommends against using NFS to
store the DB, although yum doesn't rely on multiple processes updating
the DB at once ... even so you might want to just have the packages
dirs. on NFS but leave the top level local.

We're hoping that something like yum-avahi will allow you to share data
over the local network for Fedora 11, which is the "good" way to solve
this problem IMO.


--
James Antill <james.antill@redhat.com>
Red Hat
--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Thu, 2008-09-25 at 23:35 -0400, James Antill wrote:
> On Thu, 2008-09-25 at 19:10 -0400, Dr. Diesel wrote:
> > Perhaps not a bug or maybe requires a feature request. I'm attempting
> > to host my /var/cache/yum directory on a NFS to share with several
> > other machines. I've tired doing with by simply changing the location
> > in yum.conf and also by creating a symbolic link to the directory with
> > no succes, yum just stops here with no error:
>
> What verison?
> What does strace say yum is doing?
> The sqlite documentation generally recommends against using NFS to
> store the DB, although yum doesn't rely on multiple processes updating
> the DB at once ... even so you might want to just have the packages
> dirs. on NFS but leave the top level local.
>
> We're hoping that something like yum-avahi will allow you to share data
> over the local network for Fedora 11, which is the "good" way to solve
> this problem IMO.
>

intelligent mirror is another good way.

Relying on nfs + sqlite and worrying about the race conditions
w/multiple yum instances on multiple machines possibly writing to this
location is just going to end badly.

-sv


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

>

> *We're hoping that something like yum-avahi will allow you to share data

> over the local network for Fedora 11, which is the "good" way to solve

> this problem IMO.

>



intelligent mirror is another good way.



Relying on nfs + sqlite and worrying about the race conditions

w/multiple yum instances on multiple machines possibly writing to this

location is just going to end badly.



-sv


Mirroring the package directories is easy enough.* I will attempt the strace suggestion and get back to you all.* Current versions are all F9 to date.

Any project information on yum-avahi and what it might evolve into?


Thanks
Andy

*

--

fedora-devel-list mailing list

fedora-devel-list@redhat.com

https://www.redhat.com/mailman/listinfo/fedora-devel-list



--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, 2008-09-26 at 05:29 -0500, Dr. Diesel wrote:



> Any project information on yum-avahi and what it might evolve into?

The "current" yum-avahi is at:

http://users.ecs.soton.ac.uk/rds204/yum-avahi/

...AIUI it "works", the problem is that it basically stores extra
foo.repo files on the "avahi network" and so any local attacker can
override the client machines gpg checking settings etc.
So it needs to move to just add the extra local URL at the front of the
mirrors list, and probably be cleanedup/spedup a bit. Then there is the
design of what it does now:

It is designed to present a full mirror to the clients, which isn't
that useful. What we'd want is more like "box X already download
primary.sqlite and perl, so when you do 'yum update' on box Y get those
packages from it".

The server part of it also needs some work, so it's integrated into
yum-updatesd or something and generally is cleaner/safer. As now you
have to run a specific server just for the avahi bits.

--
James Antill <james@fedoraproject.org>
Fedora

--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

2008/9/25 James Antill <james.antill@redhat.com>




*What verison?

*What does strace say yum is doing?


Ran strace on the yum PID, left it since this morning, not a single thread of activity!




--
projecthuh.com
All of my bits are free, are yours? Fedoraproject.org



--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list

On Fri, Sep 26, 2008 at 1:05 AM, seth vidal <skvidal@fedoraproject.org> wrote:





intelligent mirror is another good way.



Relying on nfs + sqlite and worrying about the race conditions

w/multiple yum instances on multiple machines possibly writing to this

location is just going to end badly.



-sv


All, linking only the packages directory has done the trick!* Many thanks to all..

Andy


--
projecthuh.com

All of my bits are free, are yours? *Fedoraproject.org


--
fedora-devel-list mailing list
fedora-devel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-devel-list