diff options
| author | Colin Walters <walters@verbum.org> | 2021-09-30 14:09:22 -0400 |
|---|---|---|
| committer | Colin Walters <walters@verbum.org> | 2021-09-30 14:09:22 -0400 |
| commit | 1ed290c7d93e24fd3986dd3c355b0d323dcdcd99 (patch) | |
| tree | 8ae11bbcb5f3347dd7c9986e08e94d09497c75ad | |
| parent | 4b61768e3dc7d2f4453fb44f1f640ccb092b59d1 (diff) | |
| download | ostree-1ed290c7d93e24fd3986dd3c355b0d323dcdcd99.tar.gz | |
fsck: Print a success message
There's a general Unix philosophy that "silence is golden".
However, when one is explicitly invoking an error check it's nice
to see explicit success.
We already print various statistics, so ending with a happy
note has no extra cost.
| -rw-r--r-- | src/ostree/ot-builtin-fsck.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/ostree/ot-builtin-fsck.c b/src/ostree/ot-builtin-fsck.c index dea03af4..f7a72601 100644 --- a/src/ostree/ot-builtin-fsck.c +++ b/src/ostree/ot-builtin-fsck.c @@ -459,5 +459,8 @@ ostree_builtin_fsck (int argc, char **argv, OstreeCommandInvocation *invocation, if (n_fsck_partial > 0) return glnx_throw (error, "%u partial commits from fsck-detected corruption", n_partial); + g_print ("object fsck of %d commits completed successfully - no errors found.\n", + (guint)g_hash_table_size (commits)); + return TRUE; } |