do not really like it, because actually the space can be used in the /path/to/file
won't this cause a problem?
Do you mean
3/17/09 11:58:26 AM firstname.lastname@example.org:1104 Requested GET /Server/Shared_Files/Last Value In Range.doc
the spaces as marked in blue ? No. The significant log info is, Date, Time, User, and IP.
Anything to the right of IP can be re-combined, but anything with no space (I at least)
someone may be relying on the current format to analyze the data
If they are I wish they'd share the method. I see no way, with out seperating user and IP,
which is what apache does, 192.168.1.35 - user [17/Mar/2009:03:13:50 -0600]
I'm aware of TABS, but haven't used it.
We'll give it a try. Should work.
My purpose is to get away from apache log format, as I feel it was never intended to log the
info HFS can log. HFS is out growing apache log's design intent. There will soon come a point
where the log analyzer prog's just wont be able to read whats available.
It should be possible to use a database to show #1 download, #1 user, # visits by IP, etc.
even charts are a possibility.