From unknown Fri Mar 29 06:00:48 2024 Received: (at 269) by bugs.devuan.org; 8 Dec 2018 09:59:40 +0000 Return-Path: Delivered-To: devuanbugs@dyne.org Received: from tupac3.dyne.org [195.169.149.119] by fulcanelli with IMAP (fetchmail-6.3.26) for (single-drop); Sat, 08 Dec 2018 10:59:40 +0100 (CET) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: katolaz@freaknet.org) with ESMTPSA id 00210F60A4D Date: Sat, 8 Dec 2018 10:58:35 +0100 From: KatolaZ To: 269@bugs.devuan.org Subject: mmhhh Message-ID: <20181208095835.fva7jscctb6giqsq@katolaz.homeunix.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: NeoMutt/20170113 (1.7.2) X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED autolearn=disabled version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on tupac3.dyne.org [Reported here due to a glitch with #268] There is no need to become root in order to use `service`: $ /usr/sbin/service nginx status [ ok ] nginx is running. $ Even with a user with id larger than 4000000000: $ sudo -u testpolkit /usr/sbin/service nginx stop [....] Stopping nginx: nginxstart-stop-daemon: warning: failed to kill 2509: Operation not permitted . ok $ That's because sudo does *not* use policykit to test user privileges (rather, it uses its own config files). So maybe this is not applicable in this case? HND KatolaZ