Monitoring the operation of WD

classic Classic list List threaded Threaded
1 message Options
Rob
Reply | Threaded
Open this post in threaded view
|

Monitoring the operation of WD

Rob
WD caches spots for uploading to wsprnet.org under ~/wsprdaemon/uploads.d/wsprnet.d/spots.d

You can see what is cached by executing
find ~/wsprdaemon/uploads.d/wsprnet.d/spots.d -type f

Watch the cache files being loaded and flushed with
watch "find ~/wsprdaemon/uploads.d/wsprnet.d/spots.d -type f"

You can monitor the operation of the uploading daemon with:
tail -F ~/wsprdaemon/uploads.d/wsprnet.d/spots.d/uploads.log

By default verbosity = 0, so there should be nothing in that log file.
You can increase/decrease the verbosity of the upload daemon's logging output to that file with:
cd ~/wsprdaemon/uploads.d/wsprnet.d/spots.d/; ~/wsprdaemon/wsprdaemon.sh -d                 ### increase verbosity
cd ~/wsprdaemon/uploads.d/wsprnet.d/spots.d/; ~/wsprdaemon/wsprdaemon.sh -D                 ### decrease verbosity

There is no mechanism which limits the size of such log files, so don't leave verbosity > 0 for months.
All log files are deleted and reset to 0 length each time WD is started.

That same logging mechanism is used everywhere in WD
To see the recording/decoding/merging daemons in operation, look under /tmp/wsprdaemon/...:

find /tmp/wsprdaemon/ -name '*log'

Then 'cd /tmp/wsprdaemon/...;  ~/wsprdaemon/wsprdaemon.sh -d ;  tail -f XXXX.log'  to see that daemon in operation