I appreciate the pain of not being able to immediately read squid's logs. I've suffered this myself.
Amos, it occurs to me that most of your argument applies equally to every service running on an Ubuntu server, not just to squid. I think a reasonable counterargument is that Ubuntu users should expect the same principle to be applied to all packages. Therefore I think it makes sense for distribution packaging to change upstream defaults so that distribution users see consistency across all packages. This may temporarily break log analysers, but I think that's something that should be fixed in the log analysers to be able to cope with this new form of output - it doesn't make sense to lock in the log format forever if we think an improvement can be made, just for that. If we do conclude that we want to make the change, then the right time is as early as possible to give plenty of time to catch issues before the next Ubuntu LTS release. Amos, in mitigation, how would you feel about adding a human readable timestamp like other system log files but retaining the current numeric timestamp? Is this something that would be acceptable to do upstream? Then you'll get the accuracy/unambiguity of numeric timestamps retained but we'll also get the non-human-readability issue fixed. > Human calendar systems are a legal fiction, not a technical or scientific measure - the government of any country can redefine them at any time (and some do so even today). So is a Unix timestamp. Admittedly less so, but there are complications wrt. leap seconds, Google's "smearing" and so forth. Time is complicated :) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1780341 Title: squid should default to more human friendly timestamps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/1780341/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
