Adam Chlipala <[EMAIL PROTECTED]> wrote: > Well, when I expressed skepticism that we would have the new servers > ready to go by January, there was much optimistic nay-saying, but now > here we are in February. ;-) I don't really have a good handle on > where we are and what are the big obstacles remaining. Could the > volunteer admins please report on their ends of this?
AFS and Kerberos should be installed and working. There are some known issues with both the 1.4.2 and 1.4.3rc1 release, but until there are newer versions released, I can't do much to fix this. If there is anything I am suposed to do, please let me know. I'll be around on IRC for most of the weekend (modulo when I am asleep.) This may have been discussed before, but is anyone strongly against just waiting for etch (the next Debian stable release) to be out before migrating users? This should provide newer packages for nearly everything and may save in the long run, as trying to dist-upgrade with users on the system won't be pretty and I don't think we want to keep running sarge for too much longer after etch is out. > Personally, I'm blocked on information on how the new dbtool should > create databases, which is a requirement for porting the web portal. I believe I talked with docelic on IRC about creating a seperate volume for each user's db. I'd suggest setting the initial quota to 50MB (thats about 50000 K, which is what the AFS commands use.) There was also aa suggestion to create and add a system:backup group with rl ACLs to every volume, in case some sort of file-based backup system is to be used in the future. Additionally, I'd suggest granting the user at least rl access to this volume. They should be able to check the quota on the volume and it is usally easier to simply cd into it and run fs lq than to remember to use the vos listvol or vos examine command. <<CDC _______________________________________________ HCoop-SysAdmin mailing list [email protected] http://hcoop.net/cgi-bin/mailman/listinfo/hcoop-sysadmin
