Custom Query (196 matches)

We don't presently have a Nagios test that will alert us if there's a failure of the backend network switch, or the backend interface on an individual server. All the probes for sql.mit.edu will still pass because they run over the public network.

We should use some plugin to run a 'select 1;' or something similarly trivial on each scripts server.

“You can request a non-MIT hostname, but you'll have to register the hostname yourself and configure it's DNS with a CNAME record for "scripts-vhosts.mit.edu." or an A record for scripts-vhosts.mit.edu's IP address, 18.181.0.46.”

This isn’t useful to the typical user; the choice between CNAME and A is just confusing. Also, there are too many caveats associated with CNAMEs (canonicalization will kill most of your incoming mail, and you can’t use them at the top of a zone). We should just tell all users to use A records.

If for some reason we want to document that CNAMEs are supported even though they’re strictly inferior, we can put that information in an FAQ somewhere, but it shouldn’t be on the Pony form.

If you try to log into phpMyAdmin with the wrong password, later attempts with the correct password will fail unless you delete your cookie, which is quite cryptic. No idea why.