who would have an idea on how to stop this EMail flooding?
Thanks
Martin
Am Wed, Jan 03, 2024 at 06:58:01AM +0000 schrieb Cron Daemon:
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Already up to date.
Sorry about that. Should stop now. I killed the cronjob.
-----Original Message-----
From: Martin Spott <Martin.Spott@mgras.net>
Sent: Wednesday, January 3, 2024 1:59 AM
To: System Administration Committee Discussion/OSGeo <sac@lists.osgeo.org>
Subject: EMail flooding: Cron <root@ldap-web-staging> bash /root/pull-
repository-if-exists.sh
Good morning everybody,
who would have an idea on how to stop this EMail flooding?
Thanks
Martin
Am Wed, Jan 03, 2024 at 06:58:01AM +0000 schrieb Cron Daemon:
> hint: Pulling without specifying how to reconcile divergent branches is
> hint: discouraged. You can squelch this message by running one of the
following
> hint: commands sometime before your next pull:
> hint:
> hint: git config pull.rebase false # merge (the default strategy)
> hint: git config pull.rebase true # rebase
> hint: git config pull.ff only # fast-forward only
> hint:
> hint: You can replace "git config" with "git config --global" to set a
default
> hint: preference for all repositories. You can also pass --rebase,
--no-rebase,
> hint: or --ff-only on the command line to override the configured
Am Wed, Jan 03, 2024 at 12:56:00PM -0600 schrieb Vicky Vergara:
it was my bad, I appended to the cron job.
>/dev/null 2>&1
and restarted the cron.
Please let me know if the issue continues.
Don't worry, it's been a pleasure to show a sign of life
Generally speaking I'd say the best way to silence the GIT cron job is to
choose one of the recommendations shown in the warning. It's just a minimal
config change which, I think, is necessary when adopting an old checkout
with a new version of GIT. Typically you're well advised to go with the
proposed default setting.
By redirecting every output to /dev/null, in contrast, you'll probably miss
truly important messages in the future.
Best regards,
Martin
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
Hi Martin,
Thanks, did the git setup you mention, I removed the /dev/null 2>&1 and
added a -q flag so the mail that says "already up to date don't show up.
Regards
On Wed, Jan 3, 2024 at 4:57 PM Martin Spott <Martin.Spott@mgras.net> wrote:
Hi Vicky,
Am Wed, Jan 03, 2024 at 12:56:00PM -0600 schrieb Vicky Vergara:
> it was my bad, I appended to the cron job.
>
> >/dev/null 2>&1
>
> and restarted the cron.
> Please let me know if the issue continues.
Don't worry, it's been a pleasure to show a sign of life
Generally speaking I'd say the best way to silence the GIT cron job is to
choose one of the recommendations shown in the warning. It's just a minimal
config change which, I think, is necessary when adopting an old checkout
with a new version of GIT. Typically you're well advised to go with the
proposed default setting.
By redirecting every output to /dev/null, in contrast, you'll probably miss
truly important messages in the future.
Best regards,
Martin
--
Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------
