[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#31467: switching from ntp to openntpd, openntpd fails to start
From: |
Efraim Flashner |
Subject: |
bug#31467: switching from ntp to openntpd, openntpd fails to start |
Date: |
Wed, 16 May 2018 10:38:21 +0300 |
User-agent: |
Mutt/1.9.5 (2018-04-13) |
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 <address@hidden> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
signature.asc
Description: PGP signature
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- bug#31467: switching from ntp to openntpd, openntpd fails to start,
Efraim Flashner <=