Mark,
Michael,
Thanks for the
ideas.
The account that
this defaults to if the -user parameter is not used, is shown in the SCM as the
Local System account.
First up, tried
installing this with fully qualified -l, -d and -t parameters, but no change. I
didn't really expect anything dramatic here because the defaults generated by
DIRMON looked pretty valid.
Next up, added the
redirection of stderr in a BEGIN block (good idea!). However, no luck there, as
nothing is ever written to the log file. In fact, the log file is only created
on the install, but if then removed, is not recreated when the SCM attempts to
start the service. It appears to me that it never gets as far as loading the
script.
I can run the script
interactively, but to tell the truth, I'm not really sure what to expect when
this is done. Is it then still visible and controllable via the SCM? I
suspect not, as the install is what adds most of the SCM specific information.
For what its worth, the script appears to run once through its main service loop
(Daemon::State() first returns a state value of 0 which DIRMON treats as
unknown, then a STOPPED state (1) which causes it to exit.
Andrew
_______________________________________________ Perl-Win32-Users mailing list [email protected] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
