Add gromox-cleanup.sh script #111
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Do not write to a log file (/var/log/${SCRIPT_NAME}.log). Write to systemd logging instead, |
ahh right. and with the .service you can just echo you to stdout and it will show up in the journal under --unit grommunio-cleanup or however it might be called in the end. |
Ugh, this is ugly. We have And now, since gromox-2.38-17-gdde284b64 , it also knows |
Which will print out groups aswell which don't have any maildirs and therefore will give me an error on use or not? Same with the "admin" user. |
|
Hi,
danke, schon gelesen, werde ich in den Weihnachtsfeiertagen umbauen.
WH
…--------------------Ursprüngliche Nachricht--------------------
Von: crpb ***@***.***>
Gesendet: Samstag 14. Dezember 2024 1:52
An: grommunio/gromox ***@***.***>
CC: Walter Hofstädtler ***@***.***>; Mention
***@***.***>
Betreff: Re: [grommunio/gromox] Add gromox-cleanup.sh script (PR #111)
We have for-all-users echo-username
Which will print out groups aswell which don't have any maildirs and
therefore will give me an error on use or not? Same with the "admin" user.
These ugly hacks are there for a reason or we just need to have some
guidance on how to do it better as i can't seem to get it going here.
grom-test-2:~ # rpm -q gromox
gromox-2.38.17.gdde284b-lp156.20.1.x86_64
grom-test-2:~ # gromox-mbop for-all-users \( purge-datafiles \)
purge-datafiles: the operation failed
grom-test-2:~ # gromox-mbop for-all-users purge-datafiles
purge-datafiles: the operation failed
grom-test-2:~ # man gromox-mbop
grom-test-2:~ # gromox-mbop for-all-users -j 10 purge-datafiles
purge-datafiles: the operation failed
grom-test-2:~ # gromox-mbop for-all-users echo-username |wc -l
25
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: <grommunio/
***@***.***>
|
|
I'll remove my ugly hacks in favor of the recent commands somewhere around this weekend and update the PR ;) |
|
Oh and not only groups but contacts aswell what will look a bit confusing on usage 🙈 |
|
new iteration verbs added, cf. gromox-2.38-33-gb00c21f49 |
|
So basically this script is not needed anymore, closing in favor of #117. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Purpose of this PR: Keep gromox folders clean
While playing with gromox, I wrote a prometheus exporter here after which I noticed that some mailboxes were quite huge, even when the ondisk maidir was twice as small.
Discussing with @WalterHof and @crpb, they suggested to run various cleanups.
I was wondering why that wasn't "standard" for Grommunio, so here's a script that perhaps should be added by default to Grommunio's setup via a systemd timer / or even as fs-hook/thaw for VM environments.
Currently tested on two Grommunio servers running gromox 2.37.
Thanks for considering this.