On 2013-04-22 12:47 PM, Christian Franke wrote:
> Thanks for the problem report.
> A similar configuration works for me as expected on two Win7 SP1 systems.
We don't use Win7, but the problem I reported occurred on two different
WinXP-SP3 systems, including one which was a fresh install.
>> As you can see it is the attempts at launching "C:\Program
>> Files\smartmontools\bin\cmd.exe" which fail. Obviously that path is
>> wrong and should be "C:\WINDOWS\system32\cmd.exe".
> The above is as expected: The CreateProcess() call always searches the
> parent exe's install directory first, and then the system32 directory:
> It did not consider the PATH variable because cmd.exe was found in
Thanks, that should have occurred to me.
> - Did Process Monitor report any process creations ?
> For example:
> ... smartd.exe ... Process Create C:\Windows\system32\cmd.exe SUCCESS
> ... Command line: cmd /c "C:/Program
Our workaround was to uninstall v6.1-1 and install v5.43-1, so I no
longer have a testbed for this. However, there were no Process Monitor
entries citing smartd_warning.cmd other than the ones included in my
> - Which account is used to run smartd? SYSTEM?
I would imagine so, but I didn't pay attention to that. It's running as
a standard Windows service and certainly v5.43-1 runs as SYSTEM.
> - Is execution of cmd/bat files or cmd.exe possibly disabled for this
> account (ACL, group policies, some security tool)?
No. And note that simply rolling back to v5.43-1 works perfectly, so the
problem lies amongst the differences with v6.1-1, not in my system
>> Note that the smartd process is running "C:\WINDOWS\system32\cmd.exe"
>> correctly for many other of its activities, so it appears that the bug
>> in question may be limited in scope. However, when I run smartd manually
>> with debug enabled, then email works correctly, so perhaps the bug
>> relates to improperly setting the PATH variable for smartd_warning.cmd
>> only when running as a service?
> If it works with "smartd -d" or "smartd -q onecheck" then could be a
> problem related to PATH or account differences.
Only if v6.1-1 requires a different system configuration from v5.4x.
>> If there is a workaround we can use while we wait for a fixed release of
>> smartmontools, please describe it.
> Please try:
> - copy blat.exe to .../smartmontools/bin directory
> - copy cmd.exe to .../smartmontools/bin directory
> and report the result here.
I tried copying blat.exe to that bin directory and I changed my
configuration file to remove the explicit path to blat.exe. The
documentation said that should work, but it did not. My assumption was
therefore that the problem had nothing to do with the location of Blat.
I did not try copying cmd.exe... sorry. As above, we've rolled back to
v5.43-1, so I can't try that now.
Perhaps the bug in v6.1-1 somehow affects only WinXP?