Conversation
* use if $command instead of check for last command which is a safer way for exitcodes * get_maildirs(): use gromox-mbop instead * use `command -p` instead of $BIN_DIR * use full names for systemd.unit's * make clear that we count in seconds
gromox-mbox-repair-tool.sh: shell script improvements
Corrected the command for checking midb SQL database integrity.
|
Have been running this script on multiple grommunio systems to cope with incoherent data, comming from gromox itself or various power outages. Script works quite well, never lost any data, respects repair actions where grommunio needs to be shutdown. All in all I think it would be nice for admins to have a single repair script instead of having to run multiple small tools, which is nice for specialized admins. |
|
sh is awkward. The more one wants to do, the more awkward the syntax gets. Overall, that script looks like it wants to be gromox-mbop. At that point, mbop should just be made to do it. Choosing not to go with shell scripts. |
|
Fair enough, thanks for your viewpoint. The most crucial missing part today would be gromox-mbck also being able to repair sqlite3 files (gromox-mbck repairs a mailbox, but sqlite3 still finds errors in said file). The other part would be to allow iter over multiple mailboxes, hence the shell script. I'll keep my script around until integrated tools handle those scenarios. |
3 participants
Using this script since more than a year without any major trouble nor data loss.
Main functions:
Perhaps it could be useful to add it to gromox.
Feel free to change headers / licence / whatever if needed.
Respects sqlite3 checks as per #147