"Jeffrey Silverman" <jeffreyjhu.edu> wrote in
[...]SUID has nothing to do with enforcing ownership of files, it is used to>
> I tried this, which *almost* worked, (with example user "x"):
> * move data files to directory in user x's home directory
> * chown all data fils to x:mysql
> * simlink to the data directory from the MySQL default data directory
> I say this almost works because it does, in fact, enforce quotas for
> those files owned by x. However, new tables create new .frm, .MYD, and
> .MYI files which are owned by mysql:mysql! Thus the quota is not
> enforced on any newly created database tables.
> I also tried setting the SUID bit to force the ownership of files in
> that directory but that does not work either. After some research, I
> found that it may work on *BSD systems, but I am using Linux.
> Setting SGID worked -- it forced group ownership on new files -- but I
> can't see how that will help me enforce *user* quotas.
run a program as superuser no matter who you are.
GUID has nothing to do with enforcing group ownership of files, it is
used to run a program as superuser no matter who you are if you are in
the same group as the program is chown'ed
You could run multiple mysql daemons foreach user with -u user, listening> Things that are *not* options (so please don't suggest them):
> * using another operating system
> * I had another one but i forgot it, darnnit. :)
on a different port and having a seperate data directory.