开云体育

I just noticed that the default dw-start.sh includes "screen", so the previous may or may not apply.

There are also some distros that kill user processes on logout. It's part of systemd/logind

Hope this helps...

========

Hi Adam

Generally when you run a SSH remote terminal session the process will be stopped after disconnection. It's called "hup" and disabling is "nohup". There are a few ways around it, but these is about the simplest;


Using disown and backgrounding

?ctrl-z within the terminal window

?bg (moves process to background)

?disown -h (keeps running on terminal close)


Also possible to precede the process command with nohup". eg;

?nohup dwstart &

This also saves the running session to a file, the default being nohup.out in the home directory


Use "screen"

?ssh into your remote box and type screen, then start direwolf normally.

?Ctrl+A, then Ctrl+D. This will detach your screen session. You can now log out of the remote box.

?If you want to reconnect, ssh in again and type screen -r


Lots of help in manpages etc over this


Cheers Bob VK2YQA

On 5/8/24 12:57, Adam Liette wrote:
> Hello. I’ve recently started to learn about and experiment with > Direwolf. I have a Pi Zero 2w running a server/headless installation, > an AIOC cable, USB GPS puck, and a Quansheng UV-K5 HT to make up the > rig. It’s in an ammo box, with a larger phone backup battery. As long > as I’m using an external/remote antenna, I don’t seem to have RF > issues. Just using the HT with a rubber duck causes the AIOC to be > wiped out, and the sound card is disabled. > > Occasionally, it will take off and beacon when it’s booted, but > usually I have to restart Direwolf manually over SSH. As long as I > have a terminal connected, it operates fine. If I disconnect the SSH > session and just let it run, it gets quiet and seems to quit. I can > log back in and start over, and repeat the process. It’s usually > connected to my phone’s Wi-Fi hotspot when I’m traveling with it. > This morning on a 30 mile trip, it stalled before I left town. This > evening, it ran beautifully, as I kept a SSH client connected. My > TBEACON string is basic minimum/maximum speed smart beaconing. > > It’s like it’s not continuing to run after I’ve logged off from the > SSH session. I’ve found logs in /var/log/direwolf/, but that’s just > bland logs of APRS traffic, rather than software failures, etc. When > I log into SSH, I get a message that Direwolf is running, and I have > to send a Ctl-C break to get a prompt and start over. I’d like to be > able to boot the Pi, and just let it do its thing in the trunk, but > for some reason it stops running. >