To: alpha-osf-managers
Many thanks to :
Dr. Thomas P. Blinn, UNIX Software Group, Digital Equipment Corporation
Who pointed me in the right direction. The cause of the problem was a
system rename I did a few months ago.
The doconfig was putting it's files into /usr/sys/DISASTER but then using
/sys/DISASTER (a symbolic link) to build the kernel. Well the problem was
that the symbolic link was pointing to the the old system name directory.
I deleted the link and rebuilt the kernel again and all is fine.
Thanks,
Mark Greenhalgh
IDX Systems Corporation
02/12/98 07:20:09 AM
mark_greenhalgh_at_idx.com
Tom's reply:
>In the directory /sys/DISASTER, look at the files param.c and confdep.h;
the
>confdep.h is generated by the doconfig process (when it runs config), and
it
>gets included in the compilation of param.c; the "maxusers" value you put
in
>your configuration file SHOULD wind up as a "#define MAXUSERS nnn" in the
.h
>file.
>
>If it's really there, then try cleaning out the /sys/DISASTER directory
and
>then doing a doconfig -c DISASTER to rebuild everything from scratch. If
>that doesn't do it, it's a real mystery to me.>
>
>Tom
Original posting:
> To: alpha-osf-managers
> Hi all,
>
> I'm attempting to increase tha value of maxusers in my kernal and
the
> change just isn't taking. Any ideas why ?
>
> Config file
>
> # Special options (see configuring the kernel chapter
> # in the Guide to System Administration)
> #
> dfldsiz 134217728
> maxdsiz 1073741824
> dflssiz 2097152
> maxssiz 33554432
> cpu "DEC4100"
> maxusers 64
> config vmunix swap generic
> --- etc --- (other changes that I have made)
>
> After building the kernal....
>
> kdbx -k /sys/DISASTER/vmunix
> dbx version 3.11.10
> Type 'help' for help.
>
> (kdbx) p maxusers
> 32
> (kdbx) q
> dbx (pid 1498) died. Exiting...
Received on Thu Feb 12 1998 - 14:52:35 NZDT