Are two daily logfiles for a webserver that begin with 'W1' and 'W2,' followed by a standard timestamp, really deserving of this attack?
Why scold me? Why not make a positive contribution to the thread?
They are classic examples of the "programmer as lame namer" problem.
Christian says helpfully, while illustrating the very problem:
"The 'W1YYMMDD' log is the Web Messaging Administration log (logons/logoffs, password changes, AUTH failures, etc)."
How about: webmail_admin_yyyymmdd.log, or
webmail_security_yyyymmdd.log
note: did we learn anything from the Y2K problem? (use yyyy, not yy)
"The 'W2YYMMDD' log is the raw activity log."
how about: webmail_act_yyyymmdd.log
trying to prevent the damage:
"Neither of these should be confused with the W11YYMMDD and the W21YYMMDD logs which are used by Web Calendaring and the Monitor
service."
"1", "2", "11", "21' permutations for human-readable filenames?? GMAFB, please!!
how about: webmail_cal_yyyymmdd.log
how about: imail_mon_yyyymmdd.log
Simple self-documenting, easy to recall when looking at the log dir after a long hiatus, etc.
You can nitpick my specific filename suggestions, but my idea is unassailable vs the current lame filenames, which are indefensible.
Len
_____________________________________________________________________ http://IMGate.MEIway.com : free anti-spam gateway, runs on 1000's of sites
To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
