|The stupid question is the question not asked|
I want to thank the original poster for dropping this node into PerlMonks.
However, I've come to this node to drink many times over the past several years, and each time I came away without a functioning Windows Service.
To be fair, the largest culprit was time available, followed closely on its heels by that demon I face with increasing frequency in my life: inability to focus.
But yesterday, I broke through. The information on this node was key to breaking the ice. So, once again, many thanks to the original author.
Unfortunately, the way I was able to break the ice was to take the perl script provided here and put debugging display statements after every step so I could see what it was trying to accomplish, then to pick and play with the things it tried to do and eventually adjusted all my incorrect perceptions and assumptions until they were in alignment with system expectations and -- voila! I had a functioning Perl script installed as a Windows Service.
I am considering posting a completely functional do-it-yourself kit as a way to pave this path to the Windows Service tree in the gardens of the Monastery, that other visitors may find it more easily when they visit these hallowed grounds.
The question is, would a fully working example of something which will take you from start to finish be of value, or is it better to force the Acolyte to earn his chops the way I did? Which approach better fits the ideology of the Monastery?
In reply to Re: Install a perl script as a Win NT/2000/XP service.