Hi
I have installed the gem of win32-service-0.6.0-x86-mswin32-60.gem.But
when I run my test code such as:

require ‘rubygems’
require ‘win32/service’
include Win32

s = Service.new
s.create_service{ |srv|
srv.service_name = “foo”
srv.binary_path_name = "D:\Ruby\bin\ruby "+File.expand_path($0) srv.display_name = “Test_service” } s.close Service.start(“foo”) I will get a 1053 ERROR. How can I rescue the error? On Dec 12, 2007 4:51 AM, Kai G. [email protected] wrote: srv.service_name = “foo” srv.binary_path_name = "D:\Ruby\bin\ruby "+File.expand_path($0)
srv.display_name = “Test_service”
}
s.close

Service.start(“foo”)

I will get a 1053 ERROR. How can I rescue the error?

I suggest you google for “1053 ERROR win32-service ruby”.

You may start the service from the command line (net start foo) to see
if you get an additional debug info.

"D:\Ruby\bin\ruby "+File.expand_path($0)) The error you get might be dependant on OS version (XP/2K3/vista) and the user it runs under (default is SYSTEM). There are several constraints what you can and cannot do when running as service. Most notably, you won’t have access to stdin/stdout/stderr, and to any substed/mapped/network disks. The PATH might be different as well. On Dec 11, 8:51 pm, Kai G. [email protected] wrote: srv.service_name = “foo” srv.binary_path_name = "D:\Ruby\bin\ruby "+File.expand_path($0)
srv.display_name = “Test_service”}

s.close

Service.start(“foo”)

One thing you’ll want to be aware of is that there was an interface
change in 0.6.0. Here’s an example that uses most of the available
options:

Create a new service

Service.create(‘some_service’, nil,
:service_type => Service::WIN32_OWN_PROCESS,
:description => ‘A custom service I wrote just for fun’
:start_type => Service::AUTO_START,
:error_control => Service::ERROR_NORMAL,
:binary_path_name => ‘C:\path\to\some_service.exe’,
:dependencies => [‘W32Time’,‘Schedule’]
:service_start_name => ‘SomeDomain\User’,
:display_name => ‘This is some service’,
)

Regards,

Dan

On Dec 12, 2007 12:35 PM, Jano S. [email protected] wrote:

Or, you can merge them in one file, but distinguish among them using
command line options.
I mean, if you run my_service --register or my_service --unregister,
then it will to the register/unregister stuff.
Without option, it will run the Daemon stuff.

see mongrel_service how they do it.

On Dec 12, 2007 4:51 AM, Kai G. [email protected] wrote:

srv.service_name = “foo”
srv.binary_path_name = "D:\Ruby\bin\ruby "+File.expand_path(\$0)
srv.display_name = “Test_service”
}
s.close

Service.start(“foo”)

I will get a 1053 ERROR. How can I rescue the error?

Just make TWO scripts: one for registering the service and the other
for the service itself.
You don’t need to register the service again when it’s just being
started.

Or, you can merge them in one file, but distinguish among them using
command line options.
I mean, if you run my_service --register or my_service --unregister,
then it will to the register/unregister stuff.
Without option, it will run the Daemon stuff.

Note that in order to start the notepad, you might need to allow the
service interact with desktop. (Though
I don’t remember if this is valid for xp or for vista only. Have a
look in the service’s properties.)

Daniel B. wrote:

One thing you’ll want to be aware of is that there was an interface
change in 0.6.0. Here’s an example that uses most of the available
options:

Regards,

Dan