On Fri, 22.06.12 11:57, Paul Menzel (paulepan...@users.sourceforge.net) wrote:
Dear systemd folks,
Fedora ships systemd service files for chrony [1][2].
• chrony-wait.service:
1 [Unit]
2 Description=Wait for chrony to synchronize system clock
3 After=chronyd.service
4
On Sat, 30.06.12 01:00, Paul Menzel (paulepan...@users.sourceforge.net) wrote:
It was pointed out that the service files above are very Fedora
specific. Mantas pointed out that Arch Linux now ships unit files
directly [4]
[Unit]
Description=Chrony Network Time Daemon
On Fri, Jun 29, 2012 at 4:00 PM, Paul Menzel
paulepan...@users.sourceforge.net wrote:
So does the last service file look reasonable and should be used for
upstream inclusion?
The After=syslog.target part is probably unnecessary given how systemd
handles buffering the syslog socket.
--
David
Am Montag, den 02.07.2012, 13:04 -0700 schrieb David Strauss:
On Fri, Jun 29, 2012 at 4:00 PM, Paul Menzel wrote:
Additionally `After=nss-lockup.target` should be set, so that the NTP
Ah, nice typo I got here: s/lockup/lookup/.
daemon actually finds a NTP server.
Also, is this necessary?
On Tue, Jul 3, 2012 at 12:44 AM, Paul Menzel
paulepan...@users.sourceforge.net wrote:
I'm also generally skeptical of After= without a corresponding
Requires= entry because it only affects the ordering if the other unit
is already present in the working set of services then being started.
I
Am Dienstag, den 03.07.2012, 00:55 +0200 schrieb Kay Sievers:
On Tue, Jul 3, 2012 at 12:44 AM, Paul Menzel wrote:
I'm also generally skeptical of After= without a corresponding
Requires= entry because it only affects the ordering if the other unit
is already present in the working set of
On Tue, Jul 3, 2012 at 1:20 AM, Paul Menzel
paulepan...@users.sourceforge.net wrote:
Am Dienstag, den 03.07.2012, 00:55 +0200 schrieb Kay Sievers:
On Tue, Jul 3, 2012 at 12:44 AM, Paul Menzel wrote:
I'm also generally skeptical of After= without a corresponding
Requires= entry because it
On Mon, Jul 2, 2012 at 3:44 PM, Paul Menzel
paulepan...@users.sourceforge.net wrote:
daemon actually finds a NTP server.
Also, is this necessary? Can't chronyd just fail to sync NTP until it
works? There's value to an NTP daemon running even if it lacks
upstream sync sources for a while.
On Mon, Jul 2, 2012 at 4:20 PM, Paul Menzel
paulepan...@users.sourceforge.net wrote:
Before=, After=
Configures ordering dependencies between units. If a unit foo.service
contains a setting Before=bar.service and both units are being
started, bar.service's start-up is delayed until foo.service
Dear systemd folks,
Am Samstag, den 30.06.2012, 01:00 +0200 schrieb Paul Menzel:
Am Freitag, den 22.06.2012, 11:57 +0200 schrieb Paul Menzel:
Fedora ships systemd service files for chrony [1][2].
• chrony-wait.service:
1 [Unit]
2 Description=Wait for chrony to synchronize
Dear systemd folks,
I got some private (I do not know why) replies regarding this service
files giving me some hints.
Am Freitag, den 22.06.2012, 11:57 +0200 schrieb Paul Menzel:
Fedora ships systemd service files for chrony [1][2].
• chrony-wait.service:
1 [Unit]
2
Dear systemd folks,
Fedora ships systemd service files for chrony [1][2].
• chrony-wait.service:
1 [Unit]
2 Description=Wait for chrony to synchronize system clock
3 After=chronyd.service
4 Requires=chronyd.service
5 Before=time-sync.target
6 Wants=time-sync.target
7
8
12 matches
Mail list logo
