From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Silent maintenance
Date: Sat, 14 Aug 2010 21:41:44 +0000 [thread overview]
Message-ID: <AANLkTimLHand0g965TJmk=Y4Q+0uTFovZZRZXf9Fx4UB@mail.gmail.com> (raw)
In-Reply-To: <20100814210556.GB2372@burratino>
On Sat, Aug 14, 2010 at 21:05, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Enrico Weigelt wrote:
>
>> are there some flags to make the maintenance commands like
>> git-repack and git-gc silent, so they only output errors ?
>
> Does --quiet work? If not, patches would be welcome.
I intentionally neglected to mention that. That inevitably leads to
cases where something fails, but you didn't record the output.
Instead (copy/paste from a recent post of mine to an unrelated mailing
list, funny how these things come up at the same time), do:
Just install this: http://search.cpan.org/dist/App-Cronjob/
Then put something like this in your crontab:
@daily cronjob -E -j josm-build -E /path/to/build.sh
cronjob(1) will consume all the output, and either print it all or
nothing, depending on the exit code of the program it's running.
If you're running a POSIX shell script you can add this to the top of
the script:
# Exit on errors
trap 'fail' ERR
fail () {
code=$?
echo "Failed with exit code $code"
exit 1
}
Then you don't have to check the exit code of everything individually.
I use this for all my cronjobs, see
e.g. http://github.com/avar/openstreetmap-mirror for an example, it's
what I use to get E-Mails when the JOSM GitHub mirror fails, but
*only* when it fails.
next prev parent reply other threads:[~2010-08-14 21:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-14 13:11 Silent maintenance Enrico Weigelt
2010-08-14 13:26 ` Ævar Arnfjörð Bjarmason
2010-08-14 16:33 ` Valeo de Vries
2010-08-14 16:41 ` Ævar Arnfjörð Bjarmason
2010-08-14 21:05 ` Jonathan Nieder
2010-08-14 21:41 ` Ævar Arnfjörð Bjarmason [this message]
2010-08-14 22:04 ` Jeff King
2010-08-15 0:21 ` Ævar Arnfjörð Bjarmason
2010-08-15 13:12 ` Enrico Weigelt
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimLHand0g965TJmk=Y4Q+0uTFovZZRZXf9Fx4UB@mail.gmail.com' \
--to=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).