From owner-freebsd-isp Sat Jan 10 22:40:32 1998 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA23947 for isp-outgoing; Sat, 10 Jan 1998 22:40:32 -0800 (PST) (envelope-from owner-freebsd-isp) Received: from mx.calweb.com (mx.calweb.com [208.131.56.81]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA23873 for ; Sat, 10 Jan 1998 22:40:22 -0800 (PST) (envelope-from rdugaue@calweb.com) Received: by mx.calweb.com (8.8.6/8.8.6) with SMTP id WAA08765; Sat, 10 Jan 1998 22:38:49 -0800 (PST) X-SMTP: helo web1.calweb.com from rdugaue@calweb.com server rdugaue@web1.calweb.com ip 208.131.56.51 Date: Sat, 10 Jan 1998 22:38:49 -0800 (PST) From: Robert Du Gaue To: Alan Batie cc: Norman C Rice , David Hawkins , freebsd-isp@freebsd.org Subject: Re: How to lock out a nonpaying user? In-Reply-To: <19980110103848.00312@agora.rdrop.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 > All these complicated solutions when there's one already built into the > password file: the expiration date. I set up user's accounts so they > expire at a certain time, and when they send more money, I adjust the I believe this only works for a shell user. When the user PPPs in using Radius authentication from some terminal server like a Portmaster I don't believe Radius uses the exp date.