all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Leo Famulari <leo@famulari.name>
Cc: 24366@debbugs.gnu.org, John Darrington <john@darrington.wattle.id.au>
Subject: bug#24366: ntpd cannot write to its drift file.
Date: Sun, 4 Sep 2016 22:24:54 +0200	[thread overview]
Message-ID: <20160904202454.GA5108@jocasta.intra> (raw)
In-Reply-To: <20160904202209.GB32311@jasmine>

[-- Attachment #1: Type: text/plain, Size: 793 bytes --]

On Sun, Sep 04, 2016 at 04:22:09PM -0400, Leo Famulari wrote:
     On Sun, Sep 04, 2016 at 07:45:47PM +0200, John Darrington wrote:
     > Running the ntpd service I see lots of messages in /var/log/messages like:
     > 
     > Sep  4 13:02:21 localhost ntpd[302]: frequency file /var/run/ntp.drift.TEMP: Permission denied
     
     Can the user that runs ntpd write to that directory?

No.  ntpd runs as its own user.  /var/run is owned by root.
     
     Is there a build time configuration that we should tweak?

Not that I'm aware of.

J'


-- 
Avoid eavesdropping.  Send strong encryted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-09-04 20:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-04 17:45 bug#24366: ntpd cannot write to its drift file John Darrington
2016-09-04 20:22 ` Leo Famulari
2016-09-04 20:24   ` John Darrington [this message]
2016-09-04 20:43     ` Leo Famulari
2016-09-04 21:12       ` John Darrington
2016-09-06 19:05       ` bug#24366: [PATCH] gnu: Use a directory owned by ntpd user for " John Darrington
2016-09-09 14:26         ` Ludovic Courtès

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=20160904202454.GA5108@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=24366@debbugs.gnu.org \
    --cc=leo@famulari.name \
    /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.