Make log file name the same as Script name

[woodfold]

Instead of writing over the same log and destroying its info, each script could have its own log file.

[jeroen]

Thanks for sharing your idea, I appreciate it. But I'm afraid I disagree, I think a single logfile is better. You can very easily change the name of the logfile if you want, by editing the scripts.

[dev0]

I share woodfold's basic idea.  I've had an instance where I started a defrag and walked away, when I came back and wanted to examine the log file, I noticed it was overwritten by a scheduled defrag which ran after the initial one had finished.  Realizing you can specify the logfile name in the script, sometimes it's cumbersome to have to write multiple scripts that do the same thing, just so you can protect their log file.  As such, I have the following macro suggestions: 

!ScriptName! (for example "OptimizeWeekly")
!TimeStamp! (for example "20091002135501")

This would allow me to define something like:

Code:

WriteLogfile("!ScriptName!-!TimeStamp!.log",STRING)

Which would create a file called: OptimizeWeekly-20091002135501.log

These macros could prove useful in other applications as well.

[woodfold]

After I've modified my scripts, the next update overwrites them, and I have to edit them again. If I change their names, I have to compare the new script contents with my modified ones and edit them to comply with the new instructions.

This latest version, for instance, completely changed the way the scripts were handled. Maybe a Setting command like
UseScriptNameforLog(Yes)
could be added.

[jeroen]

Maybe a Setting command like
UseScriptNameforLog(Yes)
could be added.

See the "!ScriptTitle!" macro to use the title of a script in the name of the logfile.