yes, if the application in question logs to /var/log/messages, adding a regular expression for a pattern present in every message it emits should be sufficient.
To add a more general comment on logging: Currently, most applications and daemons on IPFire log to /var/log/messages, which makes this file a bit bloated. You might have noticed if you are trying to troubleshoot something, conduct a tail -f on this file and need to grep out any log messages from programs you are not interested in. Example (removes log messages from IPsec):
tail -f /var/log/messages | grep -v "charon"
Some things, such as Suricata (IPS) and Squid, log into their own logfiles. I don’t know about other developers’ opinions, but to me, trying to split up log destinations makes sense.
To keep it short: Please consider logging into a custom logfile, if possible.
Thanks. I’m definitely logging to a separate file. I’m building out some scripts to integrate UPSPACK_V3/README_en.md at master · rcdrones/UPSPACK_V3 · GitHub with my setup. Looking at the reference from @jon , I’m not seeing how I would add a separate file versus lines within the /var/log/messages file. I will so some more digging, but would love any pointers.
The section starting on line 211 in log.dat is where the appropriate filename is defined depending on the $section that was defined as shown in the link from Jon.
The default is the var/log/messages but if the $section variable is dma then the logs are taken from /var/log/mail
You would need to add your $section name and file location for your log info into this if/else section.
Bear in mind that as with any editing of IPFire files that they might be reset during an IPFIre Core Update and you would have to redo your changes.