On Tue, 04.07.17 20:33, Mariusz Wojcik (m6woj...@outlook.com) wrote:
> Hi,
>
> I’m just asking because of the latest “not-a-bug” [1]. As far as I
> know, there aren’t many services that need full root access (maybe
> for getting a low port number). Except for that I don’t see many use
> cases.
Am 10.07.2017 um 10:49 schrieb Lennart Poettering:
On Tue, 04.07.17 20:33, Mariusz Wojcik (m6woj...@outlook.com) wrote:
Hi,
I’m just asking because of the latest “not-a-bug” [1]. As far as I
know, there aren’t many services that need full root access (maybe
for getting a low port number).
Am 04.07.2017 um 22:33 schrieb Mariusz Wojcik:
I’m just asking because of the latest “not-a-bug” [1]. As far as I know,
there aren’t many services that need full root access (maybe for getting
a low port number). Except for that I don’t see many use cases.
Therefore, I think it would be
On Tue, 04 Jul 2017 at 20:33:54 +, Mariusz Wojcik wrote:
> As far as I know, there
> aren’t many services that need full root access (maybe for getting a low port
> number).
systemd system units are basically a replacement for LSB (or sysvinit
if you prefer) init scripts, which always run as
On Wed, 5 Jul 2017, Mariusz Wojcik wrote:
Hi,
I’m just asking because of the latest “not-a-bug” [1]. As far as I know,
there aren’t many services that need full root access (maybe for getting
a low port number). Except for that I don’t see many use cases.
Therefore, I think it would be
Hi,
I’m just asking because of the latest “not-a-bug” [1]. As far as I know, there
aren’t many services that need full root access (maybe for getting a low port
number). Except for that I don’t see many use cases. Therefore, I think it
would be useful to make the decision for root access more
