From owner-freebsd-current Thu Apr 20 11:28:27 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id LAA04998 for current-outgoing; Thu, 20 Apr 1995 11:28:27 -0700 Received: from gw.itfs.nsk.su (gw.itfs.nsk.su [193.124.36.33]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id LAA04967 for ; Thu, 20 Apr 1995 11:27:33 -0700 Received: (nnd@localhost) by gw.itfs.nsk.su (8.6.12/8.6.12) id BAA23062 for current@freebsd.org; Fri, 21 Apr 1995 01:26:16 +0700 Date: Fri, 21 Apr 1995 01:26:16 +0700 From: "Nickolay N. Dudorov" Message-Id: <199504201826.BAA23062@gw.itfs.nsk.su> To: current@FreeBSD.org Subject: About 1.1.5.1 quality Sender: current-owner@FreeBSD.org Precedence: bulk Here is just my experience with 1.1.5.1 and 2.1-development: one of my computers (386DX40, 8MB, 340 MB IDE) used to run 1.1.5.1 with named (primary for 4 zones and secondary for another 6), gated (2 ethernets and 1 slip, RIP ), SMTP relay for about 300 UUCP-connected customers (modems and uucp connections established by another comp). All this time I have to reboot it (unless it hungs or reboots without me) every 5 days due to constantn grows of used swap space. Now I use another computer (486SX33, 8MB, 540 MB PCI SCSI) with the same functions and with 2.1-development at April 9 CTM-500 level. Today "w" shows 10+ days up and swap space is used by 25% (from 35MB total). This number would be bigger if I not restart named several times, but I could not find any "unreturned" swap space. I know that this is only ONE example and 1.1.5.1 is realy VERY stable system (my 1.1.5.1 USENET and news-mail server usualy shows more than month up and I reboot it only to change the UPS) but if you dont use some KNOWN experimental or broken parts -current may bite 1.1.5.1 in some applications. N.Dudorov