adjust a use of `[INFO]` log level that is spewing 10's of thousands of lines of log data into the journal

[m10d]

with the -D flag, it seems that [INFO] level contains text much more appropriate at [DEBUG] level.

Due to some consistent oddities, i'd like to keep etesync logging turned up a bit. I attempted adding both of these to my systemd unit:

• -D flag to enable verbose logging
• LogLevelMax=6 to allow [INFO] and above but disallow the [DEBUG]

[DEBUG] (level 7) logs occupy tens of thousands of lines per second in some sync cases, so it's just not practical to keep those on long term.

could you please send this type of insanely verbose data to debug, so there is a meaningful difference between notice|info|debug levels? Thank you.

The contents of this message in particular should be [DEBUG] level, as it alone spans many thousands of lines:

etesync-dav[4178]: [2023-04-19 11:55:57 -0600] [4178/Thread-374] [INFO] PROPFIND response status for '/e>
Apr 19 11:55:57 dev1 etesync-dav[4178]: </multistatus>
Apr 19 11:55:57 dev1 etesync-dav[4178]:   </response>
Apr 19 11:55:57 dev1 etesync-dav[4178]:     </propstat>
Apr 19 11:55:57 dev1 etesync-dav[4178]:       <status>HTTP/1.1 404 Not Found</status>
Apr 19 11:55:57 dev1 etesync-dav[4178]:       </prop>
Apr 19 11:55:57 dev1 etesync-dav[4178]:         <CS:getctag />
Apr 19 11:55:57 dev1 etesync-dav[4178]:       <prop>
Apr 19 11:55:57 dev1 etesync-dav[4178]:     <propstat>
Apr 19 11:55:57 dev1 etesync-dav[4178]:     </propstat>
Apr 19 11:55:57 dev1 etesync-dav[4178]:       <status>HTTP/1.1 200 OK</status>
Apr 19 11:55:57 dev1 etesync-dav[4178]:       </prop>
Apr 19 11:55:57 dev1 etesync-dav[4178]:         <getetag>"EgRFKAtSrqoI33RsM0CpHg"</getetag>
Apr 19 11:55:57 dev1 etesync-dav[4178]:         <resourcetype />
Apr 19 11:55:57 dev1 etesync-dav[4178]:       <prop>
Apr 19 11:55:57 dev1 etesync-dav[4178]:     <propstat
...