From owner-freebsd-questions Tue Oct 28 22:11:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA22859 for questions-outgoing; Tue, 28 Oct 1997 22:11:02 -0800 (PST) (envelope-from owner-freebsd-questions) Received: from mail.san.rr.com (mail-atm.san.rr.com [204.210.0.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA22854 for ; Tue, 28 Oct 1997 22:11:00 -0800 (PST) (envelope-from studded@san.rr.com) Received: (from studded@localhost) by mail.san.rr.com (8.8.7/8.8.7) id WAA08612; Tue, 28 Oct 1997 22:08:57 -0800 (PST) Message-Id: <199710290608.WAA08612@mail.san.rr.com> From: "Studded" To: "Peter Philipp" , "spork" Cc: "freebsd-questions@FreeBSD.ORG" Date: Tue, 28 Oct 97 22:08:53 -0800 Reply-To: "Studded" Priority: Normal X-Mailer: PMMail 1.95a For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: limits and 2.2-97102x SNAP Sender: owner-freebsd-questions@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I had a similar situation involving a 2.2.5 Beta from a few days before -Release. Of course I'm sure you ran cap_mkdb /etc/login.conf ?? :) My particular problem turned out to be sshd. Prior to the 'make world' upgrade to 2.2.5-Beta , I had a 2.2-Stable from around 9/1. I had sshd installed and working, but when I installed the 2.2.5 beta, an ssh login refused to acknowledge the settings in login.conf, although su to root used root's settings. I needed to upgrade ssh, bash and a few other things anyway, which I did by compiling from the ports. After that, the limits in login.conf were recognized. I confirmed that it was sshd which was the crucial element just tonight after an upgrade to the 10/27 snap. After once again upgrading via make world, I compiled a new kernel and restarted. Once again, ssh logins didn't recognize the limits in login.conf. I tried deleting the /etc/login.conf.db and recreating it, but that didn't work. Once I re-recompiled ssh from the ports, the limits in login.conf were once again recognized for an ssh login. In my mind, this is a serious liability. I can understand needing to recompile ports and packages for major changes, but moving from 2.2.5-beta to a 2.2-snap probably shouldn't? In any case, I was planning to post this anyway now that I have the concrete info, so thanks for giving me an excuse, and I hope this helps someone. Doug On Tue, 28 Oct 1997 01:20:04 -0500 (EST), spork wrote: >One day I would like to compile a FAQ that details process limits and kind >of delineates the differences between the kernel options and the login >classes. I don't yet have all the info, but I need to get up to speed >RSN... > >Anyone else have any interesting input for this? It seems to be a pretty >confusing issue these days. > >Charles > >On Mon, 27 Oct 1997, Peter Philipp wrote: > >> I'm in a situation where I need to increase OPEN_MAX to 1024 or higher. I >> did compile the kernel which is 2.2-STABLE (2.2-97102x SNAP) with >> options "OPEN_MAX=1024" >> but now I'm at a loss with the limits as imposed by the kernel. AM I >> missing something with the init startup? Is it true I increase the >> hardlimit on users with the default class from /etc/login.conf? I have >> something along the lines of, >> >> :openfiles=1024:\ >> >> I hope this is right..is there anything I'm missing? >> >> Peter *** Proud operator, designer and maintainer of the world's largest *** Internet Relay Chat server. 4,168 clients and still growing. :-) *** Try spider.dal.net on ports 6662-4 (Powered by FreeBSD) *** Part of the DALnet IRC network ***