Could not figure out a way to have a NIS slave have an independent map.
The closest solution looks to be an entry in auto.home as
* server1,server2,server4:/export/home/&
and blocking NFS on each of the building gateways and or having each
building NFS head export only to the subnet it is on.
However, the restriction is for all the file systems on the NFS heads to be
laid out similarly ( /export/home/< >)
Regards,
--Walter
On Thu, Jul 14, 2011 at 2:12 PM, Walter Faleiro <curtorkar at gmail.com> wrote:
> All,
> Is it possible for NIS slaves to source a map that is different from the
> NIS server.
>> Please consider this scenario
> We have four batches of students and their labs are located in four
> different buildings
> The students are part of the same course but separated in years.
>> common passwd file
> custom auto.home file served by the nis slave in each building.
>> This will help the storage present in each building to provide the nfs home
> folder of the student having his/her desktop in the same building.
>> The other option is to have a local auto.home file on each user
> workstation, but that means we need to make sure all the auto.home files get
> updated when there is a change.
>> So in our setup we want to have the unique uid provided by the NIS master
> via passwd map, but allow each nis slave to provide custom auto.home and
> other maps eg auto.tools
>> Thanks,
> --Walter
>
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!