From 95a32e9750124c0e5d84f5127a420af04d357e0b Mon Sep 17 00:00:00 2001
From: Martin Pitt <martinpitt@users.noreply.github.com>
Date: Fri, 22 Feb 2019 08:04:37 +0100
Subject: [PATCH] units: re-drop ProtectHostname from systemd-hostnamed.service
 (#11792)

This was an overzealous setting from commit 99894b867f. Without this,
`hostnamectl set-hostname` fails with

    Could not set property: Access denied

as `sethostname()` fails with `EPERM`.
---
 units/systemd-hostnamed.service.in | 1 -
 1 file changed, 1 deletion(-)

diff --git a/units/systemd-hostnamed.service.in b/units/systemd-hostnamed.service.in
index 62e9b28f5b7..9c925e80d9f 100644
--- a/units/systemd-hostnamed.service.in
+++ b/units/systemd-hostnamed.service.in
@@ -25,7 +25,6 @@ PrivateNetwork=yes
 PrivateTmp=yes
 ProtectControlGroups=yes
 ProtectHome=yes
-ProtectHostname=yes
 ProtectKernelModules=yes
 ProtectKernelTunables=yes
 ProtectSystem=strict