All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla@busybox.net
To: buildroot@uclibc.org
Subject: [Buildroot] [Bug 14356] New: cronstamp jobs are not performed with bumped version of dcron
Date: Wed, 17 Nov 2021 09:50:10 +0000	[thread overview]
Message-ID: <bug-14356-163@https.bugs.busybox.net/> (raw)

https://bugs.busybox.net/show_bug.cgi?id=14356

            Bug ID: 14356
           Summary: cronstamp jobs are not performed with bumped version
                    of dcron
           Product: buildroot
           Version: 2021.02.7
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: major
          Priority: P5
         Component: Other
          Assignee: unassigned@buildroot.uclibc.org
          Reporter: dominique.tronche@atos.net
                CC: buildroot@uclibc.org
  Target Milestone: ---

Since we have integrated the commit 8a0d4e6a which bumps dcron to a non
released version, we have noticed that the cronstamp jobs are not executed. 
The timestamp of the files in /var/spool/cron/cronstamps/ directory are not
updated. 
If we revert the commit and get back to version 4.5 of dcron, the jobs are
working nominally.

-- 
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

             reply	other threads:[~2021-11-17  9:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-17  9:50 bugzilla [this message]
2021-11-17  9:52 ` [Buildroot] [Bug 14356] cronstamp jobs are not performed with bumped version of dcron bugzilla
2021-11-17 20:20 ` bugzilla
2021-11-18 12:32 ` bugzilla
2021-11-18 12:34 ` bugzilla
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@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.