On Mo, 07.10.19 11:43, Andy Pieters (syst...@andypieters.me.uk) wrote:
> Hi guys
>
> Just lately ran into a fumble. I was trying to stop and disable a
> service and I typed in:
>
> systemctl stop --now example.service
>
> The service duly stopped but wasn't disabled because the --now switch
> is o
‐‐‐ Original Message ‐‐‐
On Monday, 7 October 2019 г., 13:48, Reindl Harald
wrote:
>
>
> Am 07.10.19 um 12:43 schrieb Andy Pieters:
>
> > Just lately ran into a fumble. I was trying to stop and disable a
> > service and I typed in:
> > systemctl stop --now example.service
>
> but noweher
On Mon, 7 Oct 2019 at 11:48, Reindl Harald wrote:
>
>
>
> Am 07.10.19 um 12:43 schrieb Andy Pieters:
> > Just lately ran into a fumble. I was trying to stop and disable a
> > service and I typed in:
> >
> > systemctl stop --now example.service
>
> but nowehere "disable" is statet with that command
Am 07.10.19 um 12:43 schrieb Andy Pieters:
> Just lately ran into a fumble. I was trying to stop and disable a
> service and I typed in:
>
> systemctl stop --now example.service
but nowehere "disable" is statet with that command
> The service duly stopped but wasn't disabled because the --now
Hi guys
Just lately ran into a fumble. I was trying to stop and disable a
service and I typed in:
systemctl stop --now example.service
The service duly stopped but wasn't disabled because the --now switch
is only applicable on the disable/enable/mask commands
However, shouldn't it be good pract
