und kein BOCK dauern runterzuregeln, also gesucht und https://linuxhint.com/use-rc-local-on-ubuntu/ gefunden, nur läuft da was nicht richtig und ich weiß nicht, was zu tun ist.
hier mein try and failure
ede@tg14:~$ sudo nano /etc/rc.local [sudo] Passwort für ede: ede@tg14:~$ sudo systemctl status rc-local ● rc-local.service - /etc/rc.local Compatibility Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor prese> Drop-In: /usr/lib/systemd/system/rc-local.service.d └─debian.conf Active: inactive (dead) Docs: man:systemd-rc-local-generator(8) ...skipping... ● rc-local.service - /etc/rc.local Compatibility Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor prese> Drop-In: /usr/lib/systemd/system/rc-local.service.d └─debian.conf Active: inactive (dead) Docs: man:systemd-rc-local-generator(8) ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ ~ lines 1-6/6 (END)...skipping...
dann kommt noch 70x
● rc-local.service - /etc/rc.local Compatibility Loaded: loaded (/lib/systemd/system/rc-local.service; static; vendor preset: enabled) Drop-In: /usr/lib/systemd/system/rc-local.service.d └─debian.conf Active: inactive (dead) Docs: man:systemd-rc-local-generator(8)
dann gebe ich ein
ede@tg14:~$ sudo systemctl enable rc-local The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some
dann wird gdruckt und aktiviert
ede@tg14:~$ sudo systemctl enable rc-local The unit files have no installation config (WantedBy=, RequiredBy=, Also=, Alias= settings in the [Install] section, and DefaultInstance= for template units). This means they are not meant to be enabled using systemctl. Possible reasons for having this kind of units are: • A unit may be statically enabled by being symlinked from another unit's .wants/ or .requires/ directory. • A unit's purpose may be to act as a helper for some other unit which has a requirement dependency on it. • A unit may be started when needed via activation (socket, path, timer, D-Bus, udev, scripted systemctl call, ...). • In case of template units, the unit is meant to be enabled with some
startet nur nicht
ede@tg14:~$ sudo systemctl start rc-local Job for rc-local.service failed because the control process exited with error code. See "systemctl status rc-local.service" and "journalctl -xe" for details.
ich frage nochmal ab
ede@tg14:~$ sudo systemctl status rc-local ● rc-local.service - /etc/rc.local Compability Loaded: loaded (/etc/systemd/system/rc-local.service; enabled; vendor preset: enabled) Drop-In: /usr/lib/systemd/system/rc-local.service.d └─debian.conf Active: failed (Result: exit-code) since Fri 2022-05-13 09:08:50 CEST; 2min 58s ago Process: 3605 ExecStart=/etc/rc.local start (code=exited, status=203/EXEC) Mai 13 09:08:50 tg14 systemd[1]: Starting /etc/rc.local Compability... Mai 13 09:08:50 tg14 systemd[3605]: rc-local.service: Failed to execute command: Exec format error Mai 13 09:08:50 tg14 systemd[3605]: rc-local.service: Failed at step EXEC spawning /etc/rc.local: Exec format error Mai 13 09:08:50 tg14 systemd[1]: rc-local.service: Control process exited, code=exited, status=203/EXEC Mai 13 09:08:50 tg14 systemd[1]: rc-local.service: Failed with result 'exit-code'. Mai 13 09:08:50 tg14 systemd[1]: Failed to start /etc/rc.local Compability.
WTF was habe ich falsch gemacht.