From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] systemd-timesyncd fails to start
Date: Tue, 18 Oct 2016 11:45:00 +0200 [thread overview]
Message-ID: <20161018114500.1a6f76e0@free-electrons.com> (raw)
In-Reply-To: <e98da8cb-40e1-c8bf-4393-dfff8c828d79@jikos.cz>
Hello,
On Tue, 18 Oct 2016 10:55:26 +0200, Petr Kulhavy wrote:
> there is a peculiar problem with systemd NTP synchronization, that in
> the default rootfs the systemd-timesyncd.service always fails to start.
> The reason is that systemd-timesyncd requires the /var/tmp to be a
> permanent storage and not just a link to /tmp.
> See the second comment on this page:
> https://bbs.archlinux.org/viewtopic.php?id=151937
> And really, if I replace the symlink with an empty folder it starts working.
>
> I'm wondering what is the proper way to fix this. By default buildroot
> creates /var/tmp as a link to /tmp, however
> on some platforms the rootfs might be read-only or very limited in
> space, so making /var/tmp permanent might break other things...
>
> It would be greatly appreciated if anybody could shed more light on this.
I've added Yann E. Morin in Cc. He is working on a revamp of the root
filesystem skeleton for the systemd case, specifically to solve this
sort of problem.
You can have a look at
https://github.com/yann-morin-1998/buildroot/commits/yem/systemd-skeleton,
but I'm not sure it's the latest updated work from Yann.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-10-18 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-18 8:55 [Buildroot] systemd-timesyncd fails to start Petr Kulhavy
2016-10-18 9:45 ` Thomas Petazzoni [this message]
2016-10-19 19:38 ` Yann E. MORIN
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=20161018114500.1a6f76e0@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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