Date: Wed, 4 Dec 2002 16:06:36 +0300 (MSK) From: Varshavchick Alexander <alex@metrocom.ru> To: <freebsd-questions@FreeBSD.ORG> Cc: <freebsd-hackers@FreeBSD.ORG> Subject: maxusers and random system freezes Message-ID: <Pine.GSO.4.33.0212041552070.3419-100000@apache.metrocom.ru>
next in thread | raw e-mail | index | archive | help
Hi people, Can it be so that kernel maxusers=768 value being more than 512 leads to spontaneous system freezes which can take up to several hours when the system is just sleeping (only replying to ping) and doing nothing else, not allowing to telnet or anything. The system is 4.5-STABLE with much RAM (4 Gb) and the box has a heavy enough traffic so a bunch of other kernel options have been increased: options SHMMAXPGS=262144 #max amount of shared mem. pages options SHMMNI=256 #max number of shared memory ident if. options SHMSEG=256 #max shared mem.segs per process options MSGSEG=32767 #max num. of mes.segments in system options MSGSSZ=32 #size of msg-seg. MUST be power of 2 options MSGMNB=65535 #max char. per message queue options MSGTQL=2046 #max amount of msgs in system options SEMMNU=256 #number of semaphore UNDO structures options SEMMNS=1024 #number of semaphores in system options SEMMNI=520 #number of semaphore indentifiers options SEMUME=100 #number of UNDO keys options SEMMSL=256 # max number of semaphores per id options SEMOPM=256 # max number of operations per semop call Or what else can be causing such system crashes? Any help is greatly appreciated! Regards ---- Alexander Varshavchick, Metrocom Joint Stock Company Phone: (812)118-3322, 118-3115(fax) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.33.0212041552070.3419-100000>