On Sun, 11 Feb 2007 10:04:51 -0500 [EMAIL PROTECTED] wrote: > Adam Chlipala wrote: > > We don't know how to grant users permissions to drop tables from MySQL > > databases without letting them drop whole databases. We can't allow the > > latter because MySQL keeps permissions around, even after the databases > > they refer to are dropped. Going through dbtool, a user can only create > > databases in his AFS space. If he can drop that database and has the > > permissions to re-create it, it will be created in the default location, > > the partition housing /var/lib/mysql, and thus not subject to the user's > > database quota, allowing him to overrun /var. Anyone have a solution to > > suggest? > > > > > Is there any way that we could set restrictive permissions in all or > part of /var/lib/mysql such that a CREATE command issued through the > default mysql tool would fail?
I don't think so :( There are other files in that dir and all... _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
