Davor Ocelic <[EMAIL PROTECTED]> wrote: > Adam, here are working mysql instructions: > > http://wiki.hcoop.net/wiki/DaemonAdmin/MySQL > > (The first part of it, which is appropriately marked, > applies to both MySQL and Postgres).
Was it decideded not to grant system:backup rl access on all the volumes? (I thought it would be wise to setup a group that has read access to everything, even if we aren't going to use it right now, it might be useful in the future.) I'd also caution about making changes directly in root.cell all the time. While this seems like a good idea, if something goes wrong and the volume doesn't get released, all paths in the entire cell can be broken. I'd recomend having the common/databases directory be a seperate volume (containing only mount points) so that any problems that occur during a volume release only affect the databases and not potentially everything, including user home directories. Might be a good idea to grant the actual user "rl" access to this volume so that they can cd into it and check the quota easier. Might also make sense to have a "databases" group that contains both mysql and postgres users so that there isn't a need to grant "l" access to both on databases/USERNAME. Those instructions look fine. <<CDC _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
