From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] crontab: can't change directory to '/var/spool/cron/crontabs': No such file or directory
Date: Thu, 28 Jan 2016 17:02:57 +0000 [thread overview]
Message-ID: <1454000577.4304.27.camel@synopsys.com> (raw)
Hello,
Just noticed this:
------------------>8-------------------
# crontab -e
crontab: can't change directory to '/var/spool/cron/crontabs': No such file or directory
------------------>8-------------------
Obvious solution is:
------------------>8-------------------
# mkdir -p /var/spool/cron/crontabs
------------------>8-------------------
But the question is if we want that to be done automatically and if
we do want how (read "where") to do it properly?
The point is crond is enabled by default in Busybox, see
https://git.busybox.net/buildroot/tree/package/busybox/busybox.config#n664
so users expect crond to just work but that doesn't happen :)
Any thoughts?
-Alexey
next reply other threads:[~2016-01-28 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-28 17:02 Alexey Brodkin [this message]
2016-01-28 22:02 ` [Buildroot] crontab: can't change directory to '/var/spool/cron/crontabs': No such file or directory Peter Korsgaard
2016-01-29 10:13 ` Luca Ceresoli
2016-02-01 18:17 ` Arnout Vandecappelle
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=1454000577.4304.27.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--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