I’m sorry but I don’t understand the confusion here. WeeWX ships with 3 logwatch files; 2 config files and a script. The script is what analyses the WeeWX log and produces the WeeWX logwatch report. The WeeWX installer does not ‘install’ the WeeWX logwatch files, rather the user must install them separately as per the wiki. The suggested approach is to create symlinks (in the relevant logwatch directories) to the supplied files.
Of course you can make a copy of the script elsewhere, modify it to suit your needs and then link to that file instead (this is what I do). Problem is if there is a change to the core WeeWX logging, and the WeeWX logwatch script is changed accordingly, then those logwatch script changes will not flow through to the copied/modified script being used. The other approach is to create another separate script, a link for which can be placed in the appropriate logwatch directory. Works fine but you will now have a second logwatch report being produced, it will not be part of the logwatch report produced by the logwatch script shipped with WeeWX. Have never been a sysadmin but I don’t think either approach is appropriate or acceptable. This is very similar to customising some WeeWX function. You can modify the core code on your install and it will certainly work as you want, though you now have an orphan that will likely fail post upgrade. Alternatively, you can create a custom service, driver or whatever, place it in the user directory and call it appropriately from weewx.conf and it will coexist quite happily with WeeWX into the future even across upgrades. Gary -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/eb566540-37d9-4376-87da-29b6a7563cba%40googlegroups.com.
