DHASKIN%CLARKU.BITNET@mitvma.mit.edu (02/18/89)
Thnaks to those who responded; DEC/Atlanta actually called just as the first e-mail responses were arriving. The solution was trivial. It's a shame it took them almost 2 days to respond. In the /usr/sys/config/SYSTEMNAME file which describes the configuration of the Ultrix kernel to be built, the maxusers parameter does *not* correspond to one's licensed number of users. DEC does not recommend a specific number, but as Ross Parker (parker@waters.mpr.ca) said: > We run a Microvax 3600 with a 2-user license here with MAXUSERS set to 32. > 32 is about the minimum for a timesharing system or a system that does > any real work (we have 10 vaxes here... all are set to at least 32). The solution was obviously to change the parameter and rebuild the kernel. After rebooting we had no problem. As Ross explained: > FYI, gnodes are an in-core abstraction of the inode. They are used to > reference files in both normally mounted file systems and NFS mounted > file systems. 4.3 BSD has the same idea, but they're called 'vnodes'. I am still dismayed with DEC/Atlanta, and if this had been more critical I would have taken Dick Green's (green@unxa.DEC.com) advice: > I work for DEC and suggest that when you are dealing with any support > center and are displeased YELL and SCREAM and ask to talk to a manager. Luckily it was not a production machine. If it had that could've idled people for 2 days. Of course, if it *was* a production machine I wouldn't have rebuilt the kernel in the middle of the week. :-). Onwards and upwards... Denis
guy@auspex.UUCP (Guy Harris) (02/19/89)
>As Ross explained: > >> FYI, gnodes are an in-core abstraction of the inode. They are used to >> reference files in both normally mounted file systems and NFS mounted >> file systems. 4.3 BSD has the same idea, but they're called 'vnodes'. His explanation is correct, except that he claims that 4.3BSD has vnodes. It doesn't. SunOS has vnodes, as do systems that have picked up the vnode code from Sun's ONC/NFS source releases. Vnodes aren't limited to "normally mounted file systems" (by which I presume you mean UNIX-style file systems on local disks) and NFS mounted file systems, and I think gnodes aren't, either. They're both intended as general mechanisms to support various types of OS objects that behave like file systems and like files/directories on file systems; they can support multiple kinds of local file systems (V7/S5, 4.2BSD, MS-DOS, Files-11, etc.), multiple kinds of remote file systems (NFS, AT&T's RFS, etc.), and multiple kinds of weird file systems ("/proc", which gives you a view of the system process table and the systems processes; etc.).