[pve-devel] [RFC cluster] fix #2049: avoid conflict with chrony service
Thomas Lamprecht
t.lamprecht at proxmox.com
Mon Jan 14 15:22:53 CET 2019
On 1/14/19 11:34 AM, Oguz Bektas wrote:
> Signed-off-by: Oguz Bektas <o.bektas at proxmox.com>
> ---
>
> This is a fix attempt for bug #2049, per comment from Thomas on
> Bugzilla, though it hasn't been thoroughly tested. Ideas?
>
> debian/pve-cluster.service | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/debian/pve-cluster.service b/debian/pve-cluster.service
> index cebe4ee..9cd1a0e 100644
> --- a/debian/pve-cluster.service
> +++ b/debian/pve-cluster.service
> @@ -2,14 +2,14 @@
> Description=The Proxmox VE cluster filesystem
> ConditionFileIsExecutable=/usr/bin/pmxcfs
> Wants=corosync.service
> -Wants=systemd-timesyncd.service
> +Wants=time-sync.target
> Wants=rrdcached.service
> Before=corosync.service
> Before=ceph.service
> Before=cron.service
> After=network.target
> After=sys-fs-fuse-connections.mount
> -After=systemd-timesyncd.service
> +After=time-sync.target
> After=rrdcached.service
> DefaultDependencies=no
> Before=shutdown.target
>
applied, with a slightly extended commit message, thanks!
More information about the pve-devel
mailing list