All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zoltan Gyarmati <mr.zoltan.gyarmati@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] systemd-timesyncd doesn't start with default config and skeleton
Date: Mon, 22 Aug 2016 11:03:58 +0200	[thread overview]
Message-ID: <78aeaa18-9631-65df-dc9b-2ddb1ff16190@gmail.com> (raw)
In-Reply-To: <20160822085101.GA5779@free.fr>

Dear Yann,


great, thx, i overlooked that thread. I'll dedicate some time to review
that patchset as well, in the meantime i'll just add a a post-build script.

Thanks, regards
zgyarmati

On 2016-08-22 10:51, Yann E. MORIN wrote:
> Zoltan, All,
>
> On 2016-08-22 10:41 +0200, Zoltan Gyarmati spake thusly:
>> Dear All,
>> with version 2016.08-rc2, with the default systemd configuration the
>> systemd-timesyncd start fails with the error msg:
>>
>> buildroot systemd[115]: systemd-timesyncd.service: Failed at step
>> NAMESPACE spawning /lib/systemd/systemd-timesyncd: No such file or directory
>>
>>  It seems that the problem is that in the default rootfs skeleton the
>> /var/tmp dir is a symlink to /tmp, and in
>> /usr/lib/systemd/system/systemd-timesyncd.service the PrivateTmp
>> variable is set.
>> Either removing the PrivateTmp=yes or making /var/tmp a directory on its
>> own solves the issue. What solution would be preferable to fix this?
> The best solution is that I get to finish my skeleton-revamp series and
> get it merged( first was submitted on the lkist, second is WIP taking
> into account the comments that were made on the first):
>     https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/systemd-skeleton
>     https://git.buildroot.org/~ymorin/git/buildroot/log/?h=yem/systemd-skeleton-2
>
> Unfortunately, that won't be in 2016.08, as I haven't had time to finish
> it properly before rc1. So it will only go in for next cycle... :-/
>
> In the meantime, just use a post-build script that cleans up the mess,
> like tweaking the unit file to not require PrivateTmp, or to remove the
> /var/tmp symlink and make it a directory.
>
> Regards,
> Yann E. MORIN.
>


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: OpenPGP digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160822/6d1161d5/attachment.asc>

      reply	other threads:[~2016-08-22  9:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-22  8:41 [Buildroot] systemd-timesyncd doesn't start with default config and skeleton Zoltan Gyarmati
2016-08-22  8:51 ` Yann E. MORIN
2016-08-22  9:03   ` Zoltan Gyarmati [this message]

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=78aeaa18-9631-65df-dc9b-2ddb1ff16190@gmail.com \
    --to=mr.zoltan.gyarmati@gmail.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 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.