From owner-freebsd-questions  Tue Sep 30 10:26:13 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id KAA08449
          for questions-outgoing; Tue, 30 Sep 1997 10:26:13 -0700 (PDT)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA08441
          for <freebsd-questions@FreeBSD.ORG>; Tue, 30 Sep 1997 10:26:06 -0700 (PDT)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id KAA23020;
          Tue, 30 Sep 1997 10:22:07 -0700 (PDT)
Date: Tue, 30 Sep 1997 10:22:07 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Sunthiti Patchararungruang <stt@pluto.cpe.ku.ac.th>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: FreeBSD Questions
In-Reply-To: <Pine.BSF.3.96.970928155103.17858A-100000@pluto.cpe.ku.ac.th>
Message-ID: <Pine.BSF.3.96.970930101947.22967E-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sun, 28 Sep 1997, Sunthiti Patchararungruang wrote:

> 	I am using FreeBSD 2.2 with Wu-ftpd2.4.2, Samba, and Apache 
> from BSD package. The ftp server often generates message "ftpd[______] :
> exiting on signal 11". I don't know the source of the problem. 

Is this 2.2.0 or 2.2.2?

This is either a misconfiguration or you have some bad memory creeping
around.

> 	Moreover, when I login at the console more than 2 sessions, I
> cannot use command "man" because it always has error "cannot fork". This
> error isn't occured when I use telnet instead. However, even the "man"
> error message occured, I can create another login session from console
> without error. Therefore, I think it does not come from the memory or
> process table full. What should I do?
> 	Another error is come from fingerd, it is "fingerd[_____] : fork:
> Resource temporarily unavailable". I also don't know what I sould do.

If you're running 2.2.2, the limits for your login are set too low in
/etc/login.conf.  Try bumping up the limits.

If you're running 2.2.0, run ps -ax and make sure something hasn't gone
hog wild.

> 
> 	CPU 486DX2-66
> 	MEM 16MB
> 	SWAP 40MB
> 
> I compiled with:
> 	option MaxUsers 40

maxusers isn't an option; it's a directive.  I assume you just changed

maxusers 	16

to

maxusers 	40


in your kernel config.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major