Custom Query (1145 matches)

Reported by jdreed, 14 years ago.

/usr/share/recovery-mode/options is what gets presented to the user when they choose "recovery mode" at the grub menu. Hotline notes there's no way to force an update now.

Can we dump a shell script in /usr/share/recover-mode/options that forces an update and then a "real" reboot? (a kexec reboot occasionally will end up back in recovery mode, which is not what we want)

And when we have our debathena-change-the-ip-address-of-this-cluster-machine pony, that should go in the recovery-mode menu too.

I'll note that naming them "athena-update" and "athena-network" will cause them to appear at the top of the list (it's sorted alphabetically) which is desirable.

Reported by jdreed, 14 years ago.

When we switched to a 6-hour desync schedule during busy periods, we lost the ability to push out updates quickly. I think we want this back, particularly if we break printing again.

While the existing desync intervals (6 hours "during the day", 2 hours otherwise) are fine as fallbacks, I want the auto updater to go check a URL for a suggested desync interval. If fetching the URL fails, it can fallback to the existing schedule. We undoubtedly want to take #309 into account when implementing this.

Alternatively, the only real reason we want to desync updates is to avoid the suckage of huge updates (texlive, OOo, etc). We had talked about a URL providing a whitelist of packages that should be updated immediately, so that we can fix, say, reactivate and printing-config instantaneously. The danger there is that we can also deploy broken packages instantaneously.

This description should be updated to reflect whichever method we chose for regaining some measure of control over auto-updates.

Reported by jdreed, 14 years ago.

"setup save" only works for tcsh users, and makes all kinds of assumptions about our printing infrastructure. /mit/save/bin is full of bitrotted csh scripts and old copies of "lpr2" which are actively harmful these days.

We should talk to save about desupporting "setup save" and nuking most of /mit/save/bin. If there's any functionality that's missing after the cleanup, we can talk about providing it in Debathena directly.