RubyForge: Win32 Utils: help

Discussion Forums: help

RE: win32-service problems starting [ reply ]
2006-11-08 20:18

Thanks ... that did it. However, since I didn't have the regular install directory, I ended up replacing the service.so file in c:\ruby\lib\ruby\gems\1.8\gems\win32-service-0.5.0-mswin32\lib\win32.

Either way, the end result is that it works.

Thanks,
Clark

By: Daniel Berger

RE: win32-service problems starting [ reply ]
2006-11-08 11:51

Hi Clark,

You should be using 0.5.1. You can get the precompiled shared object at http://rubyforge.org/frs/download.php/11169/service-0.5.1-vc6.so.

Rename that file to just "service.so" and install it manually in C:\ruby\lib\ruby\site_ruby\1.8\i386-msvcrt\win32.

Let me know if you have any more problems. If there were problems with the Ruby code itself you should see a file called "C:\\test.log" with the error.

HTH,

Dan

By: Clark Snowdall

RE: win32-service problems starting [ reply ]
2006-11-08 07:55

Daniel,

Thanks for the help. Unfortunately, the new test files did not solve the problem. One question I do have is what version should I be using. I am currently using the 0.5.0 gem install from rubyforge. I noticed elsewhere on these forums you have a 0.5.1 version. However, I don't have a compiler and don't exactly know where to install the 0.5.1 version. Any suggestions?

Thanks,
Clark

By: Daniel Berger

RE: win32-service problems starting [ reply ]
2006-11-07 01:16

Hi Clark,

The example is bad. I've actually revamped the example completely in CVS. It's now two files - the daemon itself, and a controller file (tdaemon.rb, tdaemon_ctl.rb).

You can grab those out of CVS or you can wait for the next release, which I plan to have out by the end of the month.

- Dan

By: Clark Snowdall

win32-service problems starting [ reply ]
2006-11-06 23:17

I have installed win32-service, but am unable to get the example to work properly. It installs the service correctly. But a call to start it results in the ever classic: "The service did not respond to the start or control request in a timely fashion". I have tried this on two different windows XP pro machines with the same results. I have checked and double checked the paths to both the ruby executible and the ruby daemon itself many many times. Is there something I'm missing perhaps?

Snowdall