All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12011] cronstamps directory is not created by dcron package
Date: Sat, 20 Jul 2019 04:32:18 +0000	[thread overview]
Message-ID: <bug-12011-163-1y0puPVzuQ@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12011-163@https.bugs.busybox.net/>

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

--- Comment #4 from Carlos Santos <unixmania@gmail.com> ---
I identified two problems with dcron:

1. The installation creates the required directory /var/spool/cron/ but
   at run-time /var/spool is by default a symlink to /tmp, which by
   default is a tmpfs so the installed /var/spool/<foo> directories
   disappear. This can be solved in the init script as made in
   package/at/S99at but I'm not sure if it's a reasonable approach,
   since the directory contents will not persist between reboots.

2. The error messages that should be sent so the console on startup are
   not shown because crond is started with the "-f" argument via start-
   stop-daemon in order to create a PID file (see the explanation in
   commit 994e9fa72e80f8d618393619fefd68f65821144f). In order to solve
   this problem we must make dcron crate a PID file by itself and run
   in daemon mode, sending the error messages to syslog. Meanwhile we
   can just use pidof to PID file.

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

  parent reply	other threads:[~2019-07-20  4:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 13:00 [Buildroot] [Bug 12011] New: cronstamps directory is not created by dcron package bugzilla at busybox.net
2019-07-10  9:29 ` [Buildroot] [Bug 12011] " 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 [this message]
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

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-1y0puPVzuQ@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 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.