Mailinglist Archive: opensuse (794 mails)

< Previous Next >
Re: [opensuse] systemctl stop
  • From: "Carlos E. R." <robin.listas@xxxxxxxxxxxxxx>
  • Date: Tue, 28 Nov 2017 23:16:28 +0100 (CET)
  • Message-id: <alpine.LSU.2.21.1711282314510.31979@Telcontar.valinor>
Hash: SHA1

On Tuesday, 2017-11-28 at 22:10 -0000, Richmond wrote:
Felix Miata wrote:
Richmond composed on 2017-11-28 18:22 (UTC):

If I can start X with:
systemctl start
should I not also be able to stop it again with:
systemctl stop ?
I have found this leaves the system unusable with no virtual console or
graphical interface, so I have to reboot.
As it was with runlevels, where one ended X with 'init 3' or 'telinit 3', in
systemd one switches the "target", thus: 'systemctl isolate'.
'init 3' is said to be an alias to 'systemctl isolate', and to
switch back to X, 'systemctl isolate', or 'init 5'.

systemctl isolate
systemctl isolate

These commands seem to be working now too. Something must have got messed up
before, maybe by my use of start

It maybe easier to remember the traditional "init 5" and "init 3". They are supposed to be supported for ever in systemd.

- -- Cheers,
Carlos E. R.
(from openSUSE 42.2 x86_64 "Malachite" at Telcontar)

Version: GnuPG v2


To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse+owner@xxxxxxxxxxxx

< Previous Next >