| Summary: | nfs reload fails to load information from ldap netgroups | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Nuno Sucena Almeida <slug> |
| Component: | [OLD] Server | Assignee: | Network Filesystems <net-fs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | 2005.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Nuno Sucena Almeida
2005-05-18 09:16:49 UTC
so what you're saying is ... you run `/etc/init.d/nfs start` when you run `showmount -e`, it will show /home as exported you run `/etc/init.d/nfs reload` when you run `showmount -e`, /home no longer shows up you run `/etc/init.d/nfs restart` `showmount -e` once again shows /home as exported correct ? i start the nfs daemon (booting). i add some hosts to the ldap netgroup database. i do a nfs reload, and it doesn't pick up the new ones, i need to do a nfs restart. as a matter of fact, yesterday i had another error. some of the machines in the netgroup are allowed to mount and some others aren't, even with a restart. just to make sure that the ldap stuff was working, i've coded a simple c software that lists the machines, given a netgroup name: http://aeminium.org/slug/software/netgroup/ (if you can't get there, i can email the code to you) which confirms that the ldap / nss_switch.conf are correct, giving the expected results. well, almost. for some reason if i'm using ldap, the function 'setnetgrent' returns always 1 (any netgroup name exist). but returns 0 if i only have "files" in the nss_switch.conf (with the correspoding entries in /etc/netgroup ) and the netgroup doesn't exist. in any case, i can see the correct entries being displayed for the netgroup which should be enough for the nfs daemons. thats because the reload option just re-runs exportfs, it doesnt do anything else what command needs to be run to do what you expect ? i need to stop the nfs ( /etc/init.d/nfs stop ) and restart it ( /etc/init.d/nfs start) or the usual restart to get the new machines to be recongnized. but as i said, it's even more weird since some of the hosts in the vpn are allowed and some others aren't, although the netgroup is being correctly exported by ldap, which leads me to conclude that there's something wrong querying the ldap database. searching through the net i found some hints (very old, from 2001/2) saying that the nfs netgroup thing would only work with NIS exported maps. even with a complete reboot i get the same results. the question was, what needs to be added to the init.d script for nfs reload to work ? otherwise i'm just inclined to remove the reload() option from the init script get back to us with what actually needs to be done |
