From: Efraim Flashner <efraim@flashner.co.il>
To: 31467@debbugs.gnu.org
Subject: bug#31467: switching from ntp to openntpd, openntpd fails to start
Date: Wed, 16 May 2018 10:38:21 +0300 [thread overview]
Message-ID: <20180516073821.GA1239@macbook41> (raw)
[-- Attachment #1: Type: text/plain, Size: 1070 bytes --]
Currently `ntp' from `ntp' runs as ntpd:nobody, and `ntp' from
`openntpd' runs as root:root. ntp from ntp uses /var/empty as it's home
directory, which is owned by ntpd:nobody. When openntpd's ntp starts up,
it gives a permission error on its directory, /var/empty. When I changed
the directory's owner with `sudo chown -v root:root /var/empty' then
openntpd's ntp started working as expected.
Two possible solutions come to mind:
* Make openntpd run as user ntpd. This keeps the user separation
working, requires tweaking to openntpd's service (probably).
* Recreate /var/empty at boot, either as part of the start-up of
ntp/openntpd, or as a tmpfs. Neither ntp or openntpd store data that
needs to persist across reboots, so this might be worth doing anyway.
This would also prevent any suprises in the future like what I came
across.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2018-05-16 7:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 7:38 Efraim Flashner [this message]
2019-02-18 10:03 ` bug#31467: switching from ntp to openntpd, openntpd fails to start Efraim Flashner
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=20180516073821.GA1239@macbook41 \
--to=efraim@flashner.co.il \
--cc=31467@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.