I'm still working on my new implementation of my smartmontools for windows package and ran into some errors.
I run smartd as a windows service and am unable to specify my own error script handling providing the new (i know it's still experimental) way. Here's the event log when i start the service:
File C:/Program Files (x86)/smartmontools for Windows/bin/smartd.conf line 3 (drive DEVICESCAN): unknown Directive: --warnexec=erroraction.cmd
Run smartd -D to print a list of valid Directives.
Configuration file C:/Program Files (x86)/smartmontools for Windows/bin/smartd.conf has fatal syntax errors.
I also tried with -w instead of --warnexec=
I've tried full paths, no paths, whatever i try i get the same.
When i run smartd -D, output doesn't state any -w option.
I can still run my script the old way with -m <nomailer> -M exec erroraction.cmd, but only if the original smartd_warning.cmd script is there, even if i don't use it or i endup with a strange error message... Hardcoded filename ?
Also, running the service with -m <nomailer> -M test -M exec erroraction.cmd gives the following error in event log:
Test of C:\Program Files (x86)\smartmontools for Windows\bin\erroraction.cmd to console produced unexpected output (88 bytes) to STDOUT/STDERR:
Le chemin d'accŠs sp‚cifi‚ est introuvable.
Le chemin d'accŠs sp‚cifi‚ est introuvable
The erroraction.cmd script works and performs the requested tasks, but idoubt it writes any output to STDOUT/ERR because when i run the script manually and redirect it's output (including stderr) to a file, the file weights 0 bytes.
Hopefully i didn't bother you too much with this :)
Orsiris de Jong |
Badministrateur.com - Administrateur Windows & Linux