running systemd terminal commands in SysVinit mode?

[retroD0d0]

Hi, Happy May Day to those parts of the world where they celebrate.

I wanted to know how this systemd-shim thing works in MX in sysVinit mode. If I run a service like docker-desktop, will the usual systemd terminal commands eg. systemctl enable etc. work or do I have to boot in systemd mode?

[DukeComposed]

Hi, Happy May Day to those parts of the world where they celebrate.

I wanted to know how this systemd-shim thing works in MX in sysVinit mode. If I run a service like docker-desktop, will the usual systemd terminal commands eg. systemctl enable etc. work or do I have to boot in systemd mode?

If I sit down at an Apple machine and run "notepad.exe C:\Users\username\Desktop\my_file.txt", is that going to work?

[dolphin_oracle]

Hi, Happy May Day to those parts of the world where they celebrate.

I wanted to know how this systemd-shim thing works in MX in sysVinit mode. If I run a service like docker-desktop, will the usual systemd terminal commands eg. systemctl enable etc. work or do I have to boot in systemd mode?

No. systemctl is nearly non-functional while running sysVinit. things like enabling or disabling, or masking and unmasking, will work, but actually starting or stopping a service will not. In addition, the application you are running will need some kind of service file or init.d script, as systemd service files are not processed by sysVinit. basically anything that requires systemd to actually be running as the init system won't work.

there is a "service" wrapper around all this that can be beneficial. for instant, to start samba (smbd), you could do

Code: Select all

service smbd start

on both systemd and sysVinit.

[retroD0d0]

there is a "service" wrapper around all this that can be beneficial. for instant, to start samba (smbd), you could do

Code: Select all

service smbd start

on both systemd and sysVinit.

Interesting, is this service wrapper unique to MX, can i rely on it to issue typical sysV commands to systemd apps/services?

Thanks for the explanation. I guess what I wanted to better understand in detail ALL the customisations used to get systemd dependent apps/services to work in MX. I have a vague idea what the systemd-shim is doing (emulating helper functions which are otherwise native to the systemd suite) but is there more to it? like the service wrapper example above!

If anyone knows of any resource, would be glad if you could point.Thanks.

[dolphin_oracle]

there is a "service" wrapper around all this that can be beneficial. for instant, to start samba (smbd), you could do

Code: Select all

service smbd start

on both systemd and sysVinit.

Interesting, is this service wrapper unique to MX, can i rely on it to issue typical sysV commands to systemd apps/services?

Thanks for the explanation. I guess what I wanted to better understand in detail ALL the customisations used to get systemd dependent apps/services to work in MX. I have a vague idea what the systemd-shim is doing (emulating helper functions which are otherwise native to the systemd suite) but is there more to it? like the service wrapper example above!

If anyone knows of any resource, would be glad if you could point.Thanks.

service is not unique, at least in the debian world.

there is a little bit of a misconception here I think. systemd services do not run. the system user session management runs, but anything else requires sysVinit service files, or be started by dbus. even pipewire, which normally is started up by user-services under systemd (which sysVinit has no concept of), are autostarted at login to the desktop rather than by a service file.

the systemd-shim and its set of patches allow that stuff to coexist with sysVinit (mostly systemd-logind), as well as allow sytemd to run when its not at PID 1, which is always held by the init system.

What you'll find out there is probably pretty old, but mostly still valid. we are the only distribution out there still using it. however, the maintainer does post his stuff up on salsa.debian.org under the unit-diveristy initiative.. https://salsa.debian.org/knelsonmeister/systemd-shim there are also required patches to systemd. https://salsa.debian.org/knelsonmeister/systemd

[retroD0d0]

there is a little bit of a misconception here I think. systemd services do not run.

Whoops, Sorry i confused you, I meant

Can i rely on the service wrapper to issue typical sysV commands to systemd dependent apps/services?

[dolphin_oracle]

there is a little bit of a misconception here I think. systemd services do not run.

Whoops, Sorry i confused you, I meant

Can i rely on the service wrapper to issue typical sysV commands to systemd dependent apps/services?

if you are running sysVinit, and there is an init script for what you want to run, under /etc/init.d usually, then the service wrapper will work.

[asqwerth]

What do you mean by systemd-dependent?

1) you need systemd to be at PID1, ie running as the init system; or
2) the app simply requires the existence/installation of systemd packages on the system?

[retroD0d0]

What do you mean by systemd-dependent?

1) you need systemd to be at PID1, ie running as the init system; or
2) the app simply requires the existence/installation of systemd packages on the system?

number 2 please!