with low / no disk space and be unable to "escape." In the event of a backlog,
the loop in birdnet_analysis.sh runs continuously, which means analyzed files
do not get moved, which means in turn extract_new_birdsounds.sh cannot create
mp3 extractions and move the processed files again, which would allow them to
be cleaned up by the cron jobs.
This patch is the obvious fix, i.e. to just limit the maximum amount of files
birdnet_analysis.sh can process to 20. This should be a good trade off given
the small overhead of listing files etc before the main loop begins - note that
for the "normal" case of no backlog, birdnet_analysis usually exits after a
single analysis anyway.
Attempt to quieten the amount of log noise being generated by some of the birdnet services visible in the syslog and daemon.log
Recording service
When using RTSP streams the recording service is generating massive amounts of noise in the logs as it's basically outputting all it's startup info and also outputting stream and export info.
- Set the log level to only output errors
Also the birdnet_recoding service script is outputting it;s contents, I assume was doing this because of the set -x option at the beginning,
-Commenting this fixed that issue
Analysis Service
Small change to this it doesn't output a error when it can't find today's recording directory. It's a non issue if your recording via sound card but it pops up a bit when using RTSP streams as that directory is never created.
Livestream Service
Same treatment as the recording service, set log level to error. It was previously set to info and would occasionally output a massive chunk of output.. presumably abut the encoding processes.
Steve Dodd