Basil, i just want to report that having made the change you suggested, direwolf logging and file rotation works normally. 73 and thanks, John NX2I

Basil, I have been using tail -F all along.... I have edited the /etc/logrotate.d/direwolf file as per your note and will test over the next few days. thanks, John

David, thanks for the response. Yes, I have seen this documentation. I can see how tail would be stopped by the logrotation. My recollection is that this was not an issue in the past, but this is only

I guess I do not understand how this works (or should work). 1) on the NWDR22 image, how does /var/log/direwolf/direwolf.log get it's data? I have commented out the line in /etc/direwolf.conf so that

Here's an update to the direwolf logging issue I see in the NWDR22 image. The output below shows the /var/log/direwolf directory before and after a log rotation has occurred: pi@draws:/var/log/direwol

regarding the direwolf log issue, running ax25-stop followed by ax25-start re-enables the direwolf logging function; tail -F /var/log/direwolf/direwolf.log works after this procedure. I looked at the

Ok. Thanks. This is fixed.

OK. I must have run autoclean. How do I get it?

turns out FLDIGi doesn't work either because of a missing dependency: pi@draws:~ $ fldigi fldigi: error while loading shared libraries: libjpeg.so.9: cannot open shared object file: No such file or di

There's still another oddity I can mention... I use the command "tail -F /var/log/direwolf/direwolf.log" to monitor activity on my setup. In past years, I have not seen a problem. However, since insta

Thanks Paul. I will check for this on my system. 73, John

I am seeing another issue.. wsjtx does not install properly using the provided script: the image file includes wsjtx-2.5.4. However, pi@draws:~/n7nix/hfprogs $ ./hf_verchk.sh js8call: current version:

Basil, from diff config.nwdr14.txt config-currentimage.txt > diffs.txt, see the attached.

I have managed to find a solution, but it leaves me with some suspicion about the /boot/config.txt in the current image. Your mileage may vary, I am willing to admit. I have a second system (another P

I had this problem originally without performing any edits to /boot/config.txt. For my own mental health I downloaded the current image file again, checked the file with sha256sum, and wrote it to the

since my earlier note I updated : sudo apt update sudo full-upgrade I notice the output of buginfo is slightly different, so here's the current version of this output: pi@draws:~/bin $ ./buginfo.sh ==

To confirm your suspicion, I see 2 notifications in the upper right of the desktop immediately after login: "failed to load HAT overlay" "dterror: can't find symbol cprman" these disappear quite quick

here's the output from buginfo.sh pi@draws:~/bin $ ./buginfo.sh === Versions === == Kernel: Linux draws 5.15.32-v7+ #1538 SMP Thu Mar 31 19:38:48 BST 2022 armv7l GNU/Linux == Firmware: Oct 26 2022 11:

OK, because I was unable to fix the missing libraries under buster I decided to upgrade to the current image (bullseye). I downloaded, checked the image against the checksum using sha256sum (it was OK

On Mon, Jan 30, 2023 at 11:16 AM, Basil Gunn wrote: email/pat/pat_verchk.sh -u Hi Basil, I got pat to update using email/pat/pat_install.sh -f. then checked the result: pi@draws:~/n7nix/email/pat $ ./