At 10:45 AM 2/24/2006 +1030, you wrote:
>1. Why has Valve decided it is a great idea to have the log naming
>convention of "L<mm><dd><nnn>.log" ??
I find it kind of handy, but then the file timestamp is generally
all I'd need to determine what log was associated with a particular day.
I'd almost rather have the file named L<mapname><increment>.log since
invariably I wind up searching logs based upon, "Last night on de_dust..."
>2. Is there an automated tool already available that can archive logs to
>directories based on either day or month?
Probably, though it wouldn't be hard to write in Perl or
VBScript or something like that. For that matter, this could
be a good exercise to brush up on your command scripting skills. That's
code for "you're not going to like this, but it'll be good for ya." :-)
Hmmmm... Just off the top of my head, play with this:
Rem: Bzip anything with a logfile
for %%i in (L*.log) do bzip %%i %ni.zip
Rem: big kludge to create MM\DD subdirectory structure, run once
for /L %%i in (1,1,12) do
(for %%j in (1,1,31) do if not exist %%i%%j mkdir %%i\%%j))
Rem: re-cycle that to move to the appropriate folder
for /L %%i in (1,1,12) do
(for %%j in (1,1,31) do if exist L%%i%%j*.zip move %%i%%j\))
This is broken code, of course. It won't work, certainly not
first time out in one batch file. You'll need to probably create
a few outside batch files you can issue a CALL to with the %i or %j
variables passed to as arguments. Then you can do tests
(like if $1=="1" set $1=="01" and that sort of thing) but it's possible,
even in the primitive DOS shell, to automate some of these things.
Of course, there's tools and programming languages out there
that can make this a lot easier, but I'm a firm believer in staying
in practice on stuff I know will always be on any box I'm in charge of,
so that means DOS. Sometimes, in an emergency, being proficient
in these things comes in handy. Like when a virus corrupts a box to
the point you have to boot the CD, enter the recovery console, and
replace all the executables and .dll's and .ocx's in the \windows
and \windows\system32 folders, a knowledge of the FOR construct and
IF conditional can save you a lot of time.
- Dan
* Dan Sorenson DoD #1066 A.H.M.C. #35 [EMAIL PROTECTED] *
* Vikings? There ain't no vikings here. Just us honest farmers. *
* The town was burning, the villagers were dead. They didn't need *
* those sheep anyway. That's our story and we're sticking to it. *
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please
visit:
http://list.valvesoftware.com/mailman/listinfo/hlds
