Hi, Sorry for the late reply,
On Fri, Sep 19, 2008 at 05:58:47PM -0500, Karl Berry wrote: > This is trivial when one knows Apache, > > Sure. I didn't really mean to suggest documenting how to write a > redirect directive or whatever. > > What isn't trivial is figuring out the recommended way to discover (let > alone modify) the Apache config on savannah, given the plethora of > vservers. There are a lot of httpd.conf's on the server. > > Searching for apache on the wiki turns up nothing useful. Am I missing it? Well that is part of what I assume the sysadmin can figure out. Which gives: - read infra/vservers.txt - vserver-stat CTX PROC VSZ RSS userTIME sysTIME UPTIME NAME 101 45 777.9M 274.4M 7d10h20 3d13h19 35d22h41 internal 102 4 10.8M 2.8M 13h35m55 1h34m52 35d01h27 accounts 103 29 2.7G 265M 8d19h01 1d14h30 35d22h41 frontend 104 119 1.2G 232.2M 31d08h38 8d13h25 35d22h41 vcs-noshell 105 91 892M 127.7M 15h02m16 3h02m09 35d22h41 sftp 106 3 7.2M 2.3M 45m30s71 17m55s64 35d22h41 builder - "ok, this is most probably 'sftp', as it's a SFTP-based access" - vserver sftp enter - ls /etc/apache2/sites-available/ # standard Debian layout arch audio-video bzr default download - "ok, this can only be 'download'" - emacs /etc/apache2/sites-available/download So this is self-documented and avoids a documentation maintenance burden. > and this isn't safe to be done if one doesn't. > > Well, it could have been done with an http-equiv refresh file instead of > in the Apache config. (Not that I'm arguing it should have been.) Though http-equiv will only work for the directory index. -- Sylvain
