From owner-freebsd-hackers Sun Aug 1 3:46:37 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from arnold.neland.dk (mail.neland.dk [194.255.12.232]) by hub.freebsd.org (Postfix) with ESMTP id 6468E14D8C for ; Sun, 1 Aug 1999 03:46:31 -0700 (PDT) (envelope-from leifn@neland.dk) Received: from localhost (localhost [127.0.0.1]) by arnold.neland.dk (8.9.3/8.9.3) with ESMTP id MAA68087; Sun, 1 Aug 1999 12:45:46 +0200 (CEST) (envelope-from leifn@neland.dk) Date: Sun, 1 Aug 1999 12:45:46 +0200 (CEST) From: Leif Neland To: Mike Hoskins Cc: Alex Zepeda , Alex Povolotsky , hackers@FreeBSD.ORG Subject: Re: Solution for mail pseudo-users? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Then again, SQL seems to be the current buzz... Having SQL-based access > is cool/manageable (a friend generates the MySQL db from his Radius users > file). > And we do it the other way: Generate the users file from mysql. I rather prefer it like that; then I can still auth users, if mysql goes down. Also, it saved my a$$ once; mysql lacking commit and rollback. I was disturbed into firing off an update command before having typed the where-clause. I then locked the password of every user, instead of only the users belonging to a single client... Luckily, I dump the database every hour, and rcs it, so I can recreate the database at any hourly version the last few months. Leif > As usual, there's more than one way to skin a cat. > Yeah.. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message