++added:
Currently here are the subsystems we use:: # vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 101 42 773.5M 267.7M 7d12h24 3d14h16 36d10h29 internal 102 4 10.8M 2.8M 13h46m09 1h36m02 35d13h15 accounts 103 32 3.1G 293.8M 8d21h07 1d14h54 36d10h29 frontend 104 122 1.3G 280M 31d10h54 8d15h36 36d10h29 vcs-noshell 105 91 836.6M 94.1M 15h11m59 3h04m16 36d10h29 sftp 106 3 7.2M 2.3M 45m33s75 18m00s80 36d10h29 builder * frontend: Savane frontend, the web interface at sv.gnu.org and sv.nongnu.org * accounts: replicates the database to system (Unix) accounts; /etc/passwd and /etc/group are regularly copied (overwrite) to vcs-noshell and sftp * vcs-noshell: public services that are accessed through a restricted shell: CVS, Git, SVN, Hg, with their respective web browsing apps * sftp: public services that are accessed through a restricted shell and allow users to write files anywhere they want (using SFTP/SCP/rsync): download, bzr, GNU Arch, and an Apache instance to access them * internal: runs internal services, like the MySQL database, the Exim MTA (with From: and sender rewrite), a Debian mirror. There's also a public Cacti instance there. * builder: used to rebuild software, Debian packages or kernels. It's separate so there's no problem with installing dependencies, testing them, etc. There's a pbuilder (cowbuilder) ready for Etch+backports rebuilds. * and of course, the host (not a vserver) where admins can log in. There's an unused by functional chroot'd DNS setup and a Apache with a "Savannah downtime" frontpage -- forwarded from https://savannah.gnu.org/maintenance/[EMAIL PROTECTED]://savannah.gnu.org/maintenance _______________________________________________ Savannah-cvs mailing list [email protected] http://lists.gnu.org/mailman/listinfo/savannah-cvs
