From owner-freebsd-isp Mon Jan 12 10:02:11 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA05397 for isp-outgoing; Mon, 12 Jan 1998 10:02:11 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from mercury.jorsm.com (mercury.jorsm.com [207.112.128.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA05386 for ; Mon, 12 Jan 1998 10:02:04 -0800 (PST) (envelope-from jeff@mercury.jorsm.com) Received: from localhost (jeff@localhost) by mercury.jorsm.com (8.8.7/8.8.7) with SMTP id MAA24161; Mon, 12 Jan 1998 12:01:52 -0600 (CST) Date: Mon, 12 Jan 1998 12:01:51 -0600 (CST) From: Jeff Lynch To: Norman C Rice cc: David Hawkins , freebsd-isp@FreeBSD.ORG Subject: Re: How to lock out a nonpaying user? In-Reply-To: <19980110123645.13588@emu.sourcee.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, 10 Jan 1998, Norman C Rice wrote: > Sounds very interesting.... I know that RedHat Linux has a similar > feature accessible from their control-panel. Would you consider > publishing your script to simplify this task for other providers? > -- > Regards, > Norman C. Rice, Jr. I don't mind sharing this. Some parts are crude and it doesn't currently provide and file-locking mechanism but up to now there hasn't been a high likelihood of simultaneous use due to the structure of our operation. Another shortcoming is it doesn't manage the radius users file, which is also of little concern due to 99% of our logins use the DEFAULT entry. Rather than post to the list, email me separately. ========================================================================= Jeffrey A. Lynch, President JORSM Internet email: jeff@jorsm.com Northwest Indiana's Full-Service Provider Voice: (219)322-2180 927 Sheffield Avenue, Dyer, IN 46311 Autoresponse: info@jorsm.com http://www.jorsm.com