From owner-freebsd-questions  Tue Nov 10 13:29:25 1998
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id NAA18097
          for freebsd-questions-outgoing; Tue, 10 Nov 1998 13:29:25 -0800 (PST)
          (envelope-from owner-freebsd-questions@FreeBSD.ORG)
Received: from axl.training.iafrica.com (axl.training.iafrica.com [196.31.1.175])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA18075
          for <questions@freebsd.org>; Tue, 10 Nov 1998 13:29:13 -0800 (PST)
          (envelope-from sheldonh@axl.training.iafrica.com)
Received: from sheldonh (helo=axl.training.iafrica.com)
	by axl.training.iafrica.com with local-esmtp (Exim 2.05 #1)
	id 0zdLL5-0005hs-00
	for questions@freebsd.org; Tue, 10 Nov 1998 23:28:39 +0200
From: Sheldon Hearn <axl@iafrica.com>
To: questions@FreeBSD.ORG
Subject: REQ: login.conf sessionlimit primer
Date: Tue, 10 Nov 1998 23:28:38 +0200
Message-ID: <21939.910733318@axl.training.iafrica.com>
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG


Hi folks,

I've been trying to use login.conf to restrict users in the default
class to 3 concurrent logins (using ssh and console login as tests).
I've played with the sessionlimit, accounted and ttys.accounted
capabilities, used cap_mkdb (even though the comments in login.conf
indicate that a login.conf.db is not mandatory) and can't achieve the
results I'm looking for.

I would greatly appreciate some advice on what to do from start to
finish, assuming that console login / ssh can actually be restricted.

Thanks,
Sheldon.

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message