If you tell the job to do it that is what it will do. I for one fail to see why you would be trying to renew a certification twice a day as it is. I would think a monthly job at the most would be the idea or depending on the length of the certificate a yearly job would most likely be the best. This twice a day foolishness in the comments make very little sense if their process is that useless it is needed I would not be trusting them for anything as critical as security of my website. You could do a separate script for the apache2 reload that wold test something like the date on certificate then it will only reload if it has changed.

When you  want to access previous items that have been in the clipboard using a history function to not be limited to the last entry in the paste buffer or as some of them offer it have preexisting entries that will paste when wanted as they are selected for use. I will add my vote for CopyQ a lovely program that works without problems for me for many years now.

No it tells you that changes are needed if running systemd which Devuan does not do so it is proper as it is. The line in the package is correct, the line you suggest to use is the one that is wrongly formatted with the 0,12 shown by you.

No nothing with the systemd gets installed when getting the package on your machine. Who knows afterwards I have nothing to test it with.

root@9600k:~# apt install open-iscsi
Installing:                     
  open-iscsi

Installing dependencies:
  libisns0t64  libopeniscsiusr

Summary:
  Upgrading: 0, Installing: 3, Removing: 0, Not Upgrading: 3
  Download size: 475 kB
  Space needed: 2,183 kB / 17.9 GB available

Continue? [Y/n] y
Get:1 http://ca.deb.devuan.org/merged excalibur/main amd64 libopeniscsiusr amd64 2.1.11-1 [61.1 kB]
Get:2 http://ca.deb.devuan.org/merged excalibur/main amd64 libisns0t64 amd64 0.101-1+b1 [93.5 kB]
Get:3 http://ca.deb.devuan.org/merged excalibur/main amd64 open-iscsi amd64 2.1.11-1 [320 kB]
Fetched 475 kB in 5s (88.6 kB/s)    
Preconfiguring packages ...
Selecting previously unselected package libopeniscsiusr.
(Reading database ... 192304 files and directories currently installed.)
Preparing to unpack .../libopeniscsiusr_2.1.11-1_amd64.deb ...
Unpacking libopeniscsiusr (2.1.11-1) ...
Selecting previously unselected package libisns0t64:amd64.
Preparing to unpack .../libisns0t64_0.101-1+b1_amd64.deb ...
Unpacking libisns0t64:amd64 (0.101-1+b1) ...
Selecting previously unselected package open-iscsi.
Preparing to unpack .../open-iscsi_2.1.11-1_amd64.deb ...
Unpacking open-iscsi (2.1.11-1) ...
Setting up libisns0t64:amd64 (0.101-1+b1) ...
Setting up libopeniscsiusr (2.1.11-1) ...
Setting up open-iscsi (2.1.11-1) ...
Processing triggers for libc-bin (2.41-7) ...
Processing triggers for man-db (2.13.0-1) ...
Processing triggers for initramfs-tools (0.147) ...
update-initramfs: Generating /boot/initrd.img-6.12.22-amd64

And now it pops into my head you have to start pipewire manually to have sound using it, from my startup script I use in the autostart of kde but as the comment shows was used as .xsessionrc file to have it loaded when X started.

zeus@9600k:~$ cat bin/pipewire_start.sh 
#!/bin/bash

# Added to start pipewire on login to desktop
# https://dev1galaxy.org/viewtopic.php?id=5867
# was the ~/.xsessionrc -rw-rw-r-- permissions
# now ~/bin/pipewire_start.sh executable permissions
# as bash script loaded from KDE autostart in System Settings

# kill any existing pipewire instance to restore sound
pkill -u "$USER" -fx /usr/bin/pipewire-pulse 1>/dev/null 2>&1
pkill -u "$USER" -fx /usr/bin/wireplumber 1>/dev/null 2>&1
pkill -u "$USER" -fx /usr/bin/pipewire 1>/dev/null 2>&1

# start pipewire
exec /usr/bin/pipewire &

# wait for pipewire to start before attempting to start related daemons
while [ "$(pgrep -f /usr/bin/pipewire)" = "" ] ; do
   sleep 1
done

# start wireplumber
exec /usr/bin/wireplumber &

# start pipewire-pulse
exec /usr/bin/pipewire-pulse &

Usually when faced with things like this I always use similar to the below.

apt-cache policy pipewire-audio libspa-0.2-bluetooth libspa-0.2-modules pipewire-alsa pipewire libpipewire-0.3-0 wireplumber

Then once you have determined the version available and looking at the output of what it says is needed you go with.

apt install libspa-0.2-modules=0.3.65-3+deb12u1 libpipewire-0.3-0=0.3.65-3+deb12u1

Then you need to find out why the pipewire (= 0.3.65-3+deb12u1) has nothing at all to install because looking at Debian packages it is certainly there to be installed.

https://packages.debian.org/search?keyw … ection=all

Indeed it is and the worst part is the situation shows no signs of improvement.

Well without a graphical console running there will be no option to switch to it. Once you have started a graphical login console you should be able to switch between it and a cli console as normal. At least that is the way it works here for me when I logout of desktop and switch to a cli console and back to display manager login once more. That is the expected behavior when you have removed it and it never gets the chance to start.

So create the stupid directory it searches for and be done with it. That is all them .d's are a configuration directory to put files into to be loaded instead of editing the system configuration file that can be overwritten on update/upgrade losing the changes you want to have in the default behavior contained in the system file. I have no .d directory on my install either and it works fine.

root@9600k:~# ll /etc/inittab 
4 -rw-r--r-- 1 root root 2348 Jan  7 05:26 /etc/inittab

I do however have a modules-load.d which contains a file that is used to load cups related options.

root@9600k:~# ll /etc/modules*
4 -rw-r--r-- 1 root root  295 Jan 24 20:23 /etc/modules

/etc/modules-load.d:
total 4
4 -rw-r--r-- 1 root root 119 Jan 16 04:53 cups-filters.conf

Yes the *nix method of do one thing and do it well, a concept seemingly lost to many of today's programmers. And their let's copy ever GD bad idea out there chasing the new shinney. I am shocked the fools have not just dumped that AI garbage into everything yet like they usually do with such trash.

I think it was the sddm-theme-debian-maui that did that to me, remove it and install the plain sddm-theme-maui to see if it gets rid of that foolishness. At least it was one of them -debian pieces of junk that did it to me.

You are welcome, yes I can see why give it a couple of more years, they will find some other new shinny to chase and you will get to learn another new system of doing it. Been like that for the twenty-five plus years I have been using it, I have every confidence they will do it yet again.