From owner-freebsd-current Sun Nov 8 11:44:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12685 for freebsd-current-outgoing; Sun, 8 Nov 1998 11:44:27 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dingo.cdrom.com (castles209.castles.com [208.214.165.209]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA12658 for ; Sun, 8 Nov 1998 11:44:24 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id LAA03204; Sun, 8 Nov 1998 11:43:16 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199811081943.LAA03204@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Brian W. Buchanan" cc: current@FreeBSD.ORG Subject: Re: meaning of "file: table is full" kernel log messages? In-reply-to: Your message of "Sat, 07 Nov 1998 13:20:50 PST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 08 Nov 1998 11:43:15 -0800 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > My daily security check email noted some kernel log entries that I didn't > recognize: > > smarter kernel log messages: > > file: table is full > You probably want to rebuild your kernel with maxusers set much higher (what's it currently set to - 10?) > Checking dmesg, I noted that the next message indicated that a process > segfaulted, but as there's no date stamps, I don't know if it happened > immediately afterward. That'll be in the messages file as well. > I'm running -CURRENT with the kernel built Oct 13 (I'd be more current, > but the new bootloader causes my machine to lock up... any fix for this > yet?) No idea; what's the problem? -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message