Re: Perl network server as a service on Windows 2003 Server

I have used svrany for years to run perl programs (mostly mrtg data collectors) for over 5 years.

It works fine , once you get past the learning curve, and poor documentation.

I would suggest your program write to a log (Eventlog, or flat file), so you can see what state it is in.

Feel free to /msg me to discuss.

"As you get older three things happen. The first is your memory goes, and I can't remember the other two... " - Sir Norman Wisdom

Comment on Re: Perl network server as a service on Windows 2003 Server

Replies are listed 'Best First'.
Re^2: Perl network server as a service on Windows 2003 Server by dgbillotte (Initiate) on Mar 12, 2008 at 00:34 UTC
I was using EventLog initially and added some logging to flat-file just to be redundant and don't get any output to either of those sources when I run it as a process. I started this proj a while ago and am just getting back to it and I'm wondering if I perhaps missed a step in the installation of srvany. I'm going to do that over again and see if it helps. Thanks for your feedback. - daniel	[reply]
Re^3: Perl network server as a service on Windows 2003 Server by NetWallah (Canon) on Mar 12, 2008 at 15:55 UTC
When I was creating SRVANY based services frequently, I wrote the code below. Even if it is not directly usable, the registry entry documentation in this should help you. I hereby place this in the public domain. Read more... (10 kB) "As you get older three things happen. The first is your memory goes, and I can't remember the other two... " - Sir Norman Wisdom	[reply] [d/l]
Re^4: Perl network server as a service on Windows 2003 Server by dgbillotte (Initiate) on Apr 14, 2008 at 23:37 UTC
I finally got back to this and found out that my problem was a space in the path to my perl program. Double quoting the value in the registry fixed it up quick. Thanks for your help. - daniel	[reply]