开云体育

Log directory option not working?


 

I am running direwolf with the -l option, but it's not writing the log files to where I specify, its still writing to stdout.? ?I don't have log file settings in the conf file and I tried putting a "/" at the end and not doing so with the same result.

radio@rmsgwpi:/var/log/radio/direwolf $ ps -ef | grep dire
radio? ? 31276 31275? 7 Nov23 pts/4? ? 13:50:21 direwolf -c /usr/local/radio/direwolf/direwolf.conf -l /var/log/radio/direwolf/ -d n -d v
?
I validated that the "radio" user can write to that location
radio@rmsgwpi:/var/log/radio/direwolf $ touch /var/log/radio/direwolf/xx
radio@rmsgwpi:/var/log/radio/direwolf $ ls -l /var/log/radio/direwolf/
total 0
-rw-r--r-- 1 radio radio 0 Dec? 1 09:18 xx


?


 

开云体育

I can't explain the -l/-L options.. you could redirect all output to a file with

direwolf > /var/log/radio/direwolf/direwolf.log 2>&1


I happened to use "tee" in my implementations,

direwolf -d t -p -q d -t 0 -c /run/direwolf.tnc.conf | tee /var/log/radio/direwolf/direwolf.log



did you try -L /path/to/logfile.log? ?? (upper case L)


-craig
KM6LYW

On 12/1/22 09:23, ksmolkowski@... wrote:

I am running direwolf with the -l option, but it's not writing the log files to where I specify, its still writing to stdout.? ?I don't have log file settings in the conf file and I tried putting a "/" at the end and not doing so with the same result.

radio@rmsgwpi:/var/log/radio/direwolf $ ps -ef | grep dire
radio? ? 31276 31275? 7 Nov23 pts/4? ? 13:50:21 direwolf -c /usr/local/radio/direwolf/direwolf.conf -l /var/log/radio/direwolf/ -d n -d v
?
I validated that the "radio" user can write to that location
radio@rmsgwpi:/var/log/radio/direwolf $ touch /var/log/radio/direwolf/xx
radio@rmsgwpi:/var/log/radio/direwolf $ ls -l /var/log/radio/direwolf/
total 0
-rw-r--r-- 1 radio radio 0 Dec? 1 09:18 xx


?


 

I could do what you suggest, but the think I like about the -l option is that its supposed to create a daily log file so it will clean up after itself.? ? This setup will run in a very remote location and my goal is to make it as automated as possible.

There are lots of options I know,? with tee and logrotate, but if the application supports it, then why re-invent the wheel?


 

开云体育

Yah, I'm with you on that, using ramdiscs in remote locations now.? I use logrotate as you
suggested, I didn't know direwolf has that kind of feature.? Let us know what you come up
with.



On 12/1/22 09:59, ksmolkowski@... wrote:

I could do what you suggest, but the think I like about the -l option is that its supposed to create a daily log file so it will clean up after itself.? ? This setup will run in a very remote location and my goal is to make it as automated as possible.

There are lots of options I know,? with tee and logrotate, but if the application supports it, then why re-invent the wheel?


 

I believe I have it figured out.? ? The "stock" logging option is only for APRS packets.? ?I wanted to log all "heard" packets so I can display them on a simple web page so users of my gateway can see if they are being received or not.? ? I know I could parse this info from the stdout, but that seems awkward.? ?Instead I added a bit of code and compiled my own version that optionally creates a "heard" log file like so:

rmsgwpi:/var/log/radio# cat 2022-12-03.log
2022-12-03 04:09:21Z, KK7CXF, 110(22/14),? [NONE] , |||||||__
2022-12-03 04:09:30Z, KK7CXF, 82(16/12),? [NONE] , __||_____
2022-12-03 04:09:33Z, KK7CXF, 71(17/15), , _1000____
2022-12-03 04:09:34Z, KK7CXF, 63(18/14), , 5000000__
2022-12-03 04:09:34Z, KK7CXF, 64(18/15), , 3000000__
2022-12-03 04:09:35Z, KK7CXF, 63(18/15), , 2000000__
2022-12-03 04:09:37Z, KK7CXF, 82(15/12), , __000____
2022-12-03 04:09:40Z, KK7CXF, 81(14/9),? [NONE] , __|||____
2022-12-03 04:09:41Z, KK7CXF, 88(17/15),? [NONE] , _||||||__

If anyone thinks this is useful, I can do a pull request and post it.


 

开云体育

Yeah, thanks for that info. ?Sure. I wouldn’t mind doing the same thing with my igate (posting to html heard stations).


13 Pro Max

On Dec 2, 2022, at 11:24 PM, ksmolkowski@... wrote:

?I believe I have it figured out.? ? The "stock" logging option is only for APRS packets.? ?I wanted to log all "heard" packets so I can display them on a simple web page so users of my gateway can see if they are being received or not.? ? I know I could parse this info from the stdout, but that seems awkward.? ?Instead I added a bit of code and compiled my own version that optionally creates a "heard" log file like so:

rmsgwpi:/var/log/radio# cat 2022-12-03.log
2022-12-03 04:09:21Z, KK7CXF, 110(22/14),? [NONE] , |||||||__
2022-12-03 04:09:30Z, KK7CXF, 82(16/12),? [NONE] , __||_____
2022-12-03 04:09:33Z, KK7CXF, 71(17/15), , _1000____
2022-12-03 04:09:34Z, KK7CXF, 63(18/14), , 5000000__
2022-12-03 04:09:34Z, KK7CXF, 64(18/15), , 3000000__
2022-12-03 04:09:35Z, KK7CXF, 63(18/15), , 2000000__
2022-12-03 04:09:37Z, KK7CXF, 82(15/12), , __000____
2022-12-03 04:09:40Z, KK7CXF, 81(14/9),? [NONE] , __|||____
2022-12-03 04:09:41Z, KK7CXF, 88(17/15),? [NONE] , _||||||__

If anyone thinks this is useful, I can do a pull request and post it.


 

I would really appreciate if you would post a diff with your heard logging changes. That is exactly what I have been looking for.

Thanks,
-Chris
KO4YAW


 

I put in a pull request, you can checkout my changes.