Ticket #1341 (new enhancement)
Consider postponing updates if / is full
| Reported by: | jdreed | Owned by: | |
|---|---|---|---|
| Priority: | low | Milestone: | The Distant Future |
| Component: | -- | Keywords: | |
| Cc: | Fixed in version: | ||
| Upstream bug: |
Description
A debathena-workstation machine's / filled up during (or right before) an update, and now the machine is not usable. Perhaps auto-update should refuse to run if there is less than 200MB free on /.
Change History
comment:1 in reply to: ↑ description Changed 11 years ago by kaduk
comment:2 Changed 11 years ago by jdreed
I think this and #117 fits in with my grand plans for debathena-console 3.0. Basically, rather than pretending to be xconsole (which will be full of spew and is not useful for the average user) and rather than sending this and #117 to syslog (which the average user does not read), we should use debathena-console for errors _we_ generate. That is, dotfile progress can go there, as well as remote root logins. We could even have system daemon running that collects errors while the user isn't logged in and shows them to them later.
Note: See
TracTickets for help on using
tickets.
Replying to jdreed:
We should try to not break the machine, but on the other hand if the machine is not taking updates someone needs to be notified.
I don't think we have a reliable contact address for workstation machines, and the users who log in may not be maintainers. Continuing to take updates so the machine breaks will reliably get noticed, at least.