Date format bug

[jaym]

The dates within log files (example: WinGate NAT.log) is recorded incorrectly. It is in mm/dd/yy format and I have no idea where that format is coming from. The file name is correctly shown as yymmdd.hhmmss.log.
Is there a fix to this, or maybe this program does not follow Windows convention of using the Regional Settings in Control Panel?

[adrien]

Hi

I'm sure that originally we followed the regional settings, but it does appear that the log entries don't do that any more. It is possible that this changed with the major changes to logging in version 4. It's been a long time since the date format in log entries has been looked into though.

some log analysis software will break if we change it. Having said that however, the next major version of WinGate comes with remote logging via a logging service, so we are re-writing and reformatting all log entries to be more consistent, and useful (we are in discussions with several log analyser vendors about this too).

Adrien

[jaym]

Well, it is one thing to forget to follow the standard, but it is another to use a non-sorted mm/dd/yy as a default for log files. It would seem that this would break the log analyser rather than the expected YY-MM-DD or YYMMDD. Is there a patch that can be applied to fix this in the mean time? You do keep the date format code in one location only and not hard-coded anyplace, right? Not only is this format hard to scan, but it is hard to read when you deal with international correspondence and it is easy to lose track of what format is in use.

Thanks for the reply.
...Jay

[SkyMan]

mm/dd/yy is generally standard in the US.

You do keep the date format code in one location only and not hard-coded anyplace, right?

That's funny.