By registering with us, you'll be able to discuss, share and exchange private messages with other members of our community.

SignUp Now!

WAD Issues with LOG Command

After a fresh reboot, I find that the LOG command is not working properly.

First, after I issued the command

log /a /w c:\tcmd\cmdlog-all.log​

the variable %_logfile is still empty.


The log file is there, and it is logging whatever appears in the tab. Here is what I now see at the end:


The help for the LOG commands states as follows:

Command logging creates a record of each internal and external command executed either from the command prompt or from a batch file in the format below:

[date time][id] command

where the date and time are formatted according to the country code set for your system, id is the process ID, and command is the actual command after any alias or variable expansion.
As can be seen from the snippet of my log file above, there is no time stamp and no process ID. When I use the "/H" option with LOG, I also do not get time stamps or IDs. And "echo %_logfile" still returns "ECHO IS OFF". So does "echo %_hlogfile". But it appears that data is being logged to both files.
Command logs are the default. You don't need to specify anything.

May I suggest, then, adding that statement to the help text.

The following statement in the help file is confusing:

The LOG command provides independent controls for two different methods of logging TCC activity:

·Command Log
·History Log
·Output Log

You can only specify one of the /A, /E, and /H options in a single LOG command.​

It states that there are TWO different methods and then lists three. Under the "Command Log" section, it should state that that is the default if none of the three switches is specified.

Why is there no %_ologfile to determine the name of the output log file?

It would also be nice if the help made clear that each of the three can be specified and that one can have as many as three log files running at the same time.

Similar threads