thanks to all who replied,
{original}
i added more ptys (16 to be exact) to an alpha server 2100 running DU3.2g
now there seems to be a problem of,
"bash: fork: operation would block"
{summary}
I eventually noticed in /var/adm/messages that when this problem was
happening the task table was filling up, "noreen vmunix: task table is full"
(thanks to Whitney Latta for this)
Find maxusers in the output of sysconfig(8), by typing:
sysconfig -q proc | grep maxusers
This command returns the line:
maxusers = 32
The variable can be changed in a couple of ways:
1) Use the dxkerneltuner(8) utility and modify "maxusers" in the "proc"
subsystem section. Changes require reboot to take effect.
OR,
2) Edit the file /sys/conf/<HOSTNAME> and modify the value there.
Then, rebuild the kernel (doconfig -c <HOSTNAME>), and reboot.
i decided to edit the /sys/conf/<HOSTNAME> file and then rebuild the kernel.
this gave me another
<error message>
noreen.apion-ti.com> doconfig -c NOREEN
*** KERNEL CONFIGURATION AND BUILD PROCEDURE ***
Saving /sys/conf/NOREEN as /sys/conf/NOREEN.bck
Do you want to edit the configuration file? (y/n) [n]: n
*** PERFORMING KERNEL BUILD ***
min. free vnode limit too small; 150 assumed
maximum vnode limit too small; 10000 assumed
*** WARNING ***
An error has occurred during system configuration. A partial listing
of the error log file (./errs) follows:
env - COMP_HOST_ROOT=/ COMP_TARGET_ROOT=/
/bin/cc -std0 -EL -I -I. -I.. -I../include -DIDENT=NOREEN -DDEC2100_A500 -DS
WAPTYPE=1 -DUERF -DOSF -DCOMPAT_43 -DMACH -DUFS -DFFM_FS -DKERNEL -D_KERNEL
-D_BSD -no_excpt -c ../arch/alpha/genassym.c
env - COMP_HOST_ROOT=/ COMP_TARGET_ROOT=/ /bin/cc -std0 -EL -non_shared -o
genassym genassym.o
./genassym > assym.s
Make: Don't know how to make data/lsm_data.c. Stop.
Press <RETURN> to continue:
Do you want to edit the configuration file? (y/n) [n]:
*** NOTE ***
A new kernel for this machine could not be successfully created.
Restoring original configuration file - /sys/conf/NOREEN
<end of error message>
again thanks to whittney,
You have 2 issues to address here:
1) Can't rebuild the kernel using the doconfig command.
The doconfig(8) utility automates the kernel build process, and runs a
series of makes and one of them is complaining about an option that is
designated in the config file (/sys/conf/<HOSTNAME>), but it has no
object support loaded on the system. Therefore, the kernel will not
build and the make fails because it cannot find the routines.
Check the /sys/conf/<HOSTNAME> file for "lsm" options like:
"pseudo-device lsm".
If present, you can edit the file and remove the lsm entries. NOTE: if
LSM (Logical Storage Manager) is supposed to be on your system, it may
be that someone deleted the subsets in the time since the kernel was
last built! In that case, you will have to identify and reload them.
Run "setld -i" and look for subsets with the name like:
OSFLSMBIN###
OSFLSMBINCOM###
2) The "task table full" message indicates you do not have enough slots
in the kernel task table to accommodate all the extra processes that are
being run, presumably because more users are active on the system now.
Bumping the "maxusers" variable in the kernel config should alleviate
that message, unless someone is running a program that has gone out of
control!!!
i took the first option and removed the lsm entries. This let me rebuild the
kernel and put it in /sys/NOREEN/vmunix. i copied it ro root and renamed the
old vmunix to vmunix.old so all thats left to be done now is to reboot the
machine. and hopefully success
darrell king
sysadmin
darrellk_at_apion-ti.com
Received on Tue Aug 11 1998 - 14:59:42 NZST