Ah sorry. I recall now: Under Windows, calling subprocesses from a service does not work at all. After a couple of days of work I was not able to get this running. If somebody has some idea, I'm happy to try it. So most people use the elogd daemon in the background only under Linux.
Stefan
| Stefan Ritt wrote: |
|
I don't undersand myself fully how services see the environment. Like if they see the PATH at all. In some occations it helped to run the service not under the SYSTEM account, but under the (admin) account of a real user.
Stefan
| christian wrote: |
|
This I do not fully understand: To my understanding the PATH environment variable (includes the ImageMagick path) is a system variable and should be accessable from any account and should be valid under any conditions. Am I wrong? Additionally, I tried adding the system Path variable to the user specific variables for that user that runs the service (Path = %Path%) in the system settings. Finally, I tried copying the imdisplay.exe (ImageMagick executable) and convert.exe (used for the software detection) from the ImageMagick installation directory to the same directory as elogd. Neither of these approaches was successfull.
Christian
| Stefan Ritt wrote: |
|
Must be your PATH environment variable. You have usually different paths when running interactively or as a service. Try to change the path seen by services, or put the ImageMagick executable in the same directory as elogd.
Stefan
| christian wrote: |
|
Update:
While the image scaling via ImageMagick works when running elog manually it doesn't when running elog as a service. The service is hosted in the same user environment that allows image scaling with elog started manually. What else could go wrong?
Christian
|
|
|
|
|