Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12011] New: cronstamps directory is not created by dcron package
Date: Mon, 08 Jul 2019 13:00:50 +0000	[thread overview]
Message-ID: <bug-12011-163@https.bugs.busybox.net/> (raw)

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

            Bug ID: 12011
           Summary: cronstamps directory is not created by dcron package
           Product: buildroot
           Version: 2019.02.3
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at buildroot.uclibc.org
          Reporter: dominique.tronche at atos.net
                CC: buildroot at uclibc.org
  Target Milestone: ---

In package dcron makefile, the per-users directory /var/spool/cron/crontabs is
created but not the timestamp directory /var/spool/cron/cronstamps.
As a consequence, the cron jobs from /etc/cron.hourly, /etc/cron.daily,... do
not work

When crond is run manually we get the error message:
no timestamp found (user root job sys-hourly)
unable to write timestamp to /var/spool/cron/cronstamps/root.sys-hourly (user
root job sys-hourly)

-- 
You are receiving this mail because:
You are on the CC list for the bug.

             reply	other threads:[~2019-07-08 13:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 13:00 bugzilla at busybox.net [this message]
2019-07-10  9:29 ` [Buildroot] [Bug 12011] cronstamps directory is not created by dcron package bugzilla at busybox.net
2019-07-10 10:57 ` bugzilla at busybox.net
2019-07-18 19:05 ` bugzilla at busybox.net
2019-07-20  4:32 ` bugzilla at busybox.net
2019-07-20 18:41 ` bugzilla at busybox.net
2019-07-22  9:07 ` bugzilla at busybox.net
2019-07-22 11:11 ` bugzilla at busybox.net
2020-05-29 21:04 ` bugzilla at busybox.net
2024-06-15 14:50 ` 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-12011-163@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox