Title: Message
Got
it! Thanks for all the help.
The
problem was simply that there was a space in part of the fully qualified
dirmon.pl file specification. When dirmon installs itself, it does this without
enclosing the path name to itself in quotes, and haven't found a way of forcing
this
Andrew McLaren wrote:
> 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 e
07808 826 063
> -Original Message-
> From: [EMAIL PROTECTED]
> [SMTP:[EMAIL PROTECTED]
> Sent: Thursday, August 11, 2005 6:49 AM
> To: perl-win32-users@listserv.ActiveState.com
> Subject: Re: Error 1053 starting Win32::Daemon service
>
> *** WARNING
> 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 appear
Title: Message
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 ex
try "installing" the service with complete requirements like
perl dirmon.pl -install -d -l
Michael
[EMAIL PROTECTED] wrote:
> My apologies if this ends up posted multiple times, but I
> suspect the first attempt failed...
>
> Ive been having a battle getting a simple perl script to
> start
Hi, Andrew
a) can you run the DIRMON.pl script as yourself, interactively?
b) can you rediect STDERR to a file in a BEGIN{} block to see if you're able
to capture any errors from server mgr.
c) That error isn't always a problem - sometimes the service does start, I'm
guessing it's not in your ca
