This works!!
in Your cron:
@reboot /bin/bash/ /home/[your user name]/wfviewboot.sh
then make a executable script in your /home called wfviewboot.sh with this in it:
#!/bin/sh
screen -S wfview -d -m /usr/local/bin/wfserver
and on boot, the headless will run, overhead is barely visable in htop!!
user@raspberrypi:~ $ screen -list
There is a screen on:
1461.wfview (20/03/24 23:08:47) (Detached)
1 Socket in /run/screen/S-user.
You may have to connect/disconnect on the client twice at first.
One thing i did notice, if i define the sound card, in any way other than “default” (ie: none, go look and find the right one please…) in the config, errors appear when the server is starting, and sometimes connecting fails, and i have to repeat connecting from the client a few times. LEAVING it as “default” causes the server to probe about and select the correct USB AUDIO for the IC7100. I had been correctly naming the sound devices, and although this sped up the start slightly, it made things more unreliable.
I also decided to nuke the on-board sound on the Pi. The HDMI can be killed by altering the config.txt line “dtoverlay=vc4-kms-v3d” to “dtoverlay=vc4-kms-v3d,noaudio” and analogue audio output can be disabled by omitting “dtparam=audio=on” from the same config.txt. You then will only have the USB AUDIO available in the raspi-config system options/sound, no loss given the pi is dedicated to being a WFview server.
I am still allowing the GUI to start, even though the pi is headless/armless. Switching the server to ‘X’ in raspi-config will allow the running of NOMACHINE remote desktop correctly (no white screen bug), which will allow You to enjoy the best of both worlds, INCLUDING using JTDX or WSJTx or FLDIGI on the pi itself over NOMACHINE, bypassing the need to run a wfview server at all, should that be a thing You like the idea of. I don’t, but it’s there if I am bored.