From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14356] cronstamp jobs are not performed with bumped version of dcron
Date: Thu, 18 Nov 2021 12:34:12 +0000 [thread overview]
Message-ID: <bug-14356-163-KZgXQ4WwTg@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-14356-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=14356
--- Comment #4 from Dominique Tronche <dominique.tronche@atos.net> ---
We only have a logrotate script in /etc/cron.daily. Has you can see in the
snapshot the timestamp of the cronstamps file are not updated. root.sys-hourly
should be updated every hour
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2021-11-18 12:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-17 9:50 [Buildroot] [Bug 14356] New: cronstamp jobs are not performed with bumped version of dcron bugzilla
2021-11-17 9:52 ` [Buildroot] [Bug 14356] " bugzilla
2021-11-17 20:20 ` bugzilla
2021-11-18 12:32 ` bugzilla
2021-11-18 12:34 ` bugzilla [this message]
2021-12-01 21:17 ` bugzilla
2023-05-05 14:15 ` bugzilla
2023-05-06 15:21 ` bugzilla
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-14356-163-KZgXQ4WwTg@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@uclibc.org \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.