Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 10 Jan 1998 13:55:35 -0500
From:      Norman C Rice <nrice@emu.sourcee.com>
To:        Alan Batie <batie@agora.rdrop.com>
Cc:        Norman C Rice <nrice@emu.sourcee.com>, David Hawkins <dhawk@river.org>, freebsd-isp@freebsd.org
Subject:   Re: How to lock out a nonpaying user?
Message-ID:  <19980110135535.19480@emu.sourcee.com>
In-Reply-To: <19980110103848.00312@agora.rdrop.com>; from Alan Batie on Sat, Jan 10, 1998 at 10:38:48AM -0800
References:  <199801101411.GAA17813@ohio.river.org> <19980110102326.26066@emu.sourcee.com> <19980110103848.00312@agora.rdrop.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Jan 10, 1998 at 10:38:48AM -0800, Alan Batie wrote:
> On Sat, Jan 10, 1998 at 10:23:26AM -0500, Norman C Rice wrote:
> > I use `vipw' to place an asterisk (*) in the first character of their
> > password field.
> >
> > You could use vipw to change their login program to /usr/bin/false or
> > /nonexistent.
> 
> 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
> expiration accordingly.  That way the system automatically handles it,
> and all I have to is the odd "oh please the check's in the mail and I
> really need my email" extensions at the beginning of the month.  I keep
> the paid-for expiration date in a separate file with scripts to munge
> things in batches for payment processing.
> 
> -- 
> Alan Batie                   ______      It's not my fault!  It's some guy
> batie@agora.rdrop.com        \    /      named "General Protection"!
> +1 503 452-0960               \  /       --Ratbert
> PGP FP: DE 3C 29 17 C0 49      \/        7A 27 40 A5 3C 37 4A DA 52 B9
> 
> It is my policy to avoid purchase of any products from companies which
> use unrequested email advertisements or telephone solicitation.

Perhaps they are complicated. Perhaps the automation of selectively 
updating the expiration date field for all users every month isn't 
trivial either. Perhaps it's not trivial to enter the "paid-for
expiration date" for all users. Who knows?

Everyone is contributing some very good ideas. Hopefully, David finds
a suggestion that works for him.
-- 
Regards,
Norman C. Rice, Jr.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980110135535.19480>