http://bugzilla.opensuse.org/show_bug.cgi?id=1182834 http://bugzilla.opensuse.org/show_bug.cgi?id=1182834#c1 --- Comment #1 from Dario Faggioli <dfaggioli@suse.com> --- (In reply to Dario Faggioli from comment #0)
Still, localtime()/time() are probably pretty popular when it comes to logging (e.g., on webservers... and in fact, I gave a quick look at the code of ngnix, and they're there). Surely excessive logging would be bad for other reasons, but I think that something like this means that even "normal logging" has more impact on performance than it could/should have.
Speaking about possible solutions, I'm not sure what to propose, TBH. Setting TZ, according to documentation (https://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html) should not be necessary in the vast majority of the case, so I don't think we can rely on users/admin doing that themselves that often. We can just always set it up ourselves, but then what if the localtime really changes? This is probably rare enough, but it it happens, apps and services will start to log wrong timestamps (or will have to be rebooted) which we definitely don't want. Speaking with performance people, the idea of rime and/or rate limit the stat() calls (e.g. no more than once a minute) came up. So, thoughts? -- You are receiving this mail because: You are on the CC list for the bug.