automounter vs mock (shared-subtrees) was Re: Mock 0.8.x available

[Orion Poplawski]

Michael E Brown wrote:
> On Tue, Nov 13, 2007 at 03:12:50PM -0800, Jeff Sheltren wrote:
>> Yep, sorry for the noise, I didn't realize I was using an older  
>> version.  After rebuilding 0.8.7 for EL5, it mostly works, but I have  
>> noticed on bug so far.  In my configs, I have a mock repo defined  
>> using file:///some/path which is an NFS mounted directory (handled by  
>> automount).  Now, if that is not currently mounted and I run mock,  
>> then yum in mock gives an error that the repodata isn't found for that  
>> repo.  At that point I can run the 'mount' command, see that automount  
>> has mounted the directory, and then if I re-run mock it will complete  
>> the setup/build successfully.
> 
> This is because mock now clone()'s itself and creates a new namespace
> before exe()-ing the mock.py code. Your automounter is not sharing the
> new namespace that mock creates. You can fix this by running:
> 
> # mount --make-rshared /
> 
> You can put it in your /etc/rc.local.
> 
> I was not able to find out the syntax to put this into /etc/fstab, which
> is where I think it goes.

The problem I'm seeing is that a mock instance runs, it accesses 
file:///data/sw1/...  which is automounted for that process, but then I 
cannot access /data/sw1 for any other process until the first mock 
quits.  mount --make-rshared / doesn't seem to help.

-- 
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  orion at cora.nwra.com
Boulder, CO 80301              http://www.cora.nwra.com