unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
* bug#31467: switching from ntp to openntpd, openntpd fails to start
@ 2018-05-16  7:38 Efraim Flashner
  2019-02-18 10:03 ` Efraim Flashner
  0 siblings, 1 reply; 2+ messages in thread
From: Efraim Flashner @ 2018-05-16  7:38 UTC (permalink / raw)
  To: 31467

[-- 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 --]

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2019-02-18 10:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-05-16  7:38 bug#31467: switching from ntp to openntpd, openntpd fails to start Efraim Flashner
2019-02-18 10:03 ` Efraim Flashner

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).