I posted about my problem executing an exe from a command alias or
from mailproc and wanted to report the issue.
I had set up a mailroot\scripts directory and had my programs in that
folder to run. The programs each opened a log file extended, wrote a line
with the arguments passed, closed, and exited. The log file name was
of the form "program.log" - no path information.
So just to review the issues:
Perl script worked called thusly:
"c:\perl\bin\perl.exe c:\mailroot\scripts\test1.pl"
Wsh vb script worked:
"C:\winnt\system32\cscript.exe //T:120 c:\mailroot\scripts\test2.vbs"
Direct exe did not (seem to) work:
"c:\mailroot\scripts\test3.exe"
And I thought this because I could not find test3.log.
So in the course of searching for this I moved the test3.exe program
to the C:\winnt\system32\ folder and changed my cmdalias line
accordingly. Sent and e-mail and then looked for the log file in the
c:\winnt\system32\ folder.
And sure enough it was there which left me very puzzled since the
permissions were exactly the same. But, suddenly, I noticed there
were other entries in the log file. So I switched back to the
original and sent another e-mail and sure enough the log file in
c:\winnt\system32\ folder was updated.
I am certainly no Windows expert but I assume that the context of the
system user must somehow default to the C:\winnt\system32 directory
(not that that seems strange really) and so the log file was written
there since I didn't give it a better path.
I suppose the lesson must be that you have to really define the file
paths used in the executables.
Thought I'd report in case anyone else was having trouble.
Terry Fritts
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
