5 Jul
1999
5 Jul
'99
3:25 p.m.
Over the past few months, for various reasons, our F630 has lost it's connection to our NIS slave. Pretty well every time this happens the filer decides not to serve either NFS or CIFS clients(usually CIFS). The only way to get the machine to serve data again is to run ypset and have it bind to a new NIS slave or(as a last resort) reboot the filer and have it automatically discover another slave. Shouldn't the filer bind itself to a new NIS slave after some timeout period without any intervention?
We're currently running DOT 5.3.1 but have seen the problem on several 5.2 versions.
Does anyone have any recommendations or are we stuck with less stable NIS client?
-Sean