LinkChecker works great. Thanks for the module.
I thought that LinkChecker was not listening to my 4 week interval setting because I get these two entries with every cron run...
linkchecker 02/27/2015 - 3:51pm Memory usage: 22.21 MB, Peak memory usage: 24.71 MB.
linkchecker 02/27/2015 - 3:51pm Link checks completed.
However, this article explained that all is well, https://www.drupal.org/node/1980034.
However, I keep a small log file for performance reasons and linkchecker is filling up my logs. Could you please add an optionally silent mode log mode or something? Options could include...
1. Silent - errors only
2. Normal
3. Verbose - current state
Comment | File | Size | Author |
---|---|---|---|
#10 | Issue-2443055-by-Alan-D-Optionally-reduce-the-number.patch | 14.15 KB | hass |
| |||
#2 | linkchecker-2443055-2-configurable-watchdog-reporting.patch | 13.88 KB | Alan D. |
Comments
Comment #1
hass CreditAttribution: hass commentedLet's add a "Debug mode" or "Verbose logging" setting checkbox to to module and conditional run this watchdog call only if enabled.
Can you share a patch, please?
Comment #2
Alan D. CreditAttribution: Alan D. commentedI didn't review the watchdog severity levels on all 30 or so calls, but this is a really nice way to provide control to the user. It allows users to decide what level to report and only records these to the watchdog() system.
Change in the default level to exclude debugging. About 6 new t() strings.
And usage is as simple as replacing watchdog() with linkchecker_watchdog_log().
Comment #3
webservant316 CreditAttribution: webservant316 commentedcool. I like it.
Comment #4
Alan D. CreditAttribution: Alan D. commentedWas that a RTBTC?
Comment #5
webservant316 CreditAttribution: webservant316 commentednot yet, sorry I wasn't more clear. hope to test next week.
Comment #6
webservant316 CreditAttribution: webservant316 commentedworks for me. thanks!
Comment #7
Alan D. CreditAttribution: Alan D. commentedExcellent, hopefully the maintainer likes it :)
Comment #8
webservant316 CreditAttribution: webservant316 commentedSimple and clean enough. Also a legit need for those needing a smaller log file so that linkchecker doesn't push logs off the end so quickly.
Comment #9
hass CreditAttribution: hass commentedLooks good to me. Commit this after some testing.
Comment #10
hass CreditAttribution: hass commentedComment #12
hass CreditAttribution: hass commentedI'm personally not going to backport this change as D6 is close to EOL.
Comment #13
Alan D. CreditAttribution: Alan D. commentedCool, thanks.
Now, (totally out of scope of this issue / project), to write something that combines common watchdog entries, like cron run messages so we can have a watchdog table with months worth of useful messages :)
Comment #14
hass CreditAttribution: hass commentedHook_watchdog()... A simple task :-)
Comment #15
hass CreditAttribution: hass commentedHook_watchdog()... A simple task :-)
Comment #16
Alan D. CreditAttribution: Alan D. commented:P delete x where y
Playing with the idea of writing something that produces a single entry per event, "cron last run w and on x,y,z" and "404 favicon.ico requested 57 times", etc; still fairly easy, just a matter of getting the time to write it :)