EMail flooding: Cron <root at ldap-web-staging> bash /root/pull-repository-if-exists.sh

[Vicky Vergara]

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 at 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 !
> --------------------------------------------------------------------------
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/sac/attachments/20240103/864e1c94/attachment.htm>