Christian Schlaefcke
2007-Apr-07 19:20 UTC
[Backgroundrb-devel] Error when starting Backgroundrb
Hi Folks, I want to set up backgroundrb on my laptop to do some tests. But when I run "scripts/background start" I get this error: ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in `setsid'': the setsid() function is unimplemented on this machine (NotImplementedError) from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in `call_as_daemon'' from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:191:in `start_proc'' from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:227:in `start'' from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/controller.rb:69:in `run'' from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb:182:in `run_proc'' from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb:105:in `call'' from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb:105:in `catch_exceptions'' from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb:181:in `run_proc'' from Test/vendor/plugins/backgroundrb-0.2.1/server/lib/backgroundrb_server.rb:301:in `run'' from Test/vendor/plugins/backgroundrb-0.2.1/script/backgroundrb:31 I had the fork-not-implemented-error before so I use "require ''win32/process''" on my WinXP Notebook. This "setsid is unimplemented" is new and even google could not tell me much about it. Anybody here who experienced this error and could help with a workaround? Thanks & Regards, Christian -------------- next part -------------- A non-text attachment was scrubbed... Name: cschlaefcke.vcf Type: text/x-vcard Size: 368 bytes Desc: not available Url : http://rubyforge.org/pipermail/backgroundrb-devel/attachments/20070407/e7170100/attachment.vcf
On 4/8/07, Christian Schlaefcke <cschlaefcke at wms-network.de> wrote:> Hi Folks, > > I want to set up backgroundrb on my laptop to do some tests. But when I > run "scripts/background start" I get this error: > > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in > `setsid'': the setsid() function is unimplemented on this machine > (NotImplementedError) > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in > `call_as_daemon'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:191:in > `start_proc'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:227:in > `start'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/controller.rb:69:in > `run'' > from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb:182:in > `run_proc'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb:105:in > `call'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb:105:in > `catch_exceptions'' > from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb:181:in > `run_proc'' > from > Test/vendor/plugins/backgroundrb-0.2.1/server/lib/backgroundrb_server.rb:301:in > > `run'' > from Test/vendor/plugins/backgroundrb-0.2.1/script/backgroundrb:31 > > I had the fork-not-implemented-error before so I use "require > ''win32/process''" on my WinXP Notebook. This "setsid is unimplemented" is > new and even google could not tell me much about it. Anybody here who > experienced this error and could help with a workaround? > > Thanks & Regards, > > Christian >You do realize that, bdrb is not supported on Windows platforms.
On 7 Apr 2007, at 20:20, Christian Schlaefcke wrote:> Hi Folks, > > I want to set up backgroundrb on my laptop to do some tests. But > when I > run "scripts/background start" I get this error: > > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb: > 160:in > `setsid'': the setsid() function is unimplemented on this machine > (NotImplementedError) > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb: > 160:in > `call_as_daemon'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/ > application.rb:191:in > `start_proc'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/ > application.rb:227:in > `start'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/controller.rb: > 69:in > `run'' > from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb: > 182:in > `run_proc'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb: > 105:in > `call'' > from > ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb: > 105:in > `catch_exceptions'' > from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb: > 181:in > `run_proc'' > from > Test/vendor/plugins/backgroundrb-0.2.1/server/lib/ > backgroundrb_server.rb:301:in > `run'' > from Test/vendor/plugins/backgroundrb-0.2.1/script/backgroundrb:31 > > I had the fork-not-implemented-error before so I use "require > ''win32/process''" on my WinXP Notebook. This "setsid is > unimplemented" is > new and even google could not tell me much about it. Anybody here who > experienced this error and could help with a workaround? > > Thanks & Regards, > > Christian > > > <cschlaefcke.vcf> > _______________________________________________ > Backgroundrb-devel mailing list > Backgroundrb-devel at rubyforge.org > http://rubyforge.org/mailman/listinfo/backgroundrb-develAs far as I know `sesid` is a unix call which sets the session id of a "leader" process. All processes then spawned by that process belong to the same session. Think a unix shell and any programs it starts up. I''m not sure what you need to do to get this work properly on windows but that might help you turn up something. - Geoff
Christian Schlaefcke
2007-Apr-08 18:15 UTC
[Backgroundrb-devel] Error when starting Backgroundrb
Geoff Garside schrieb:> On 7 Apr 2007, at 20:20, Christian Schlaefcke wrote: > >> Hi Folks, >> >> I want to set up backgroundrb on my laptop to do some tests. But when I >> run "scripts/background start" I get this error: >> >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in >> >> `setsid'': the setsid() function is unimplemented on this machine >> (NotImplementedError) >> from >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in >> >> `call_as_daemon'' >> from >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:191:in >> >> `start_proc'' >> from >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:227:in >> >> `start'' >> from >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/controller.rb:69:in >> >> `run'' >> from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb:182:in >> `run_proc'' >> from >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb:105:in >> `call'' >> from >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb:105:in >> `catch_exceptions'' >> from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb:181:in >> `run_proc'' >> from >> Test/vendor/plugins/backgroundrb-0.2.1/server/lib/backgroundrb_server.rb:301:in >> >> `run'' >> from Test/vendor/plugins/backgroundrb-0.2.1/script/backgroundrb:31 >> >> I had the fork-not-implemented-error before so I use "require >> ''win32/process''" on my WinXP Notebook. This "setsid is unimplemented" is >> new and even google could not tell me much about it. Anybody here who >> experienced this error and could help with a workaround? >> >> Thanks & Regards, >> >> Christian >> >> >> <cschlaefcke.vcf> >> _______________________________________________ >> Backgroundrb-devel mailing list >> Backgroundrb-devel at rubyforge.org >> http://rubyforge.org/mailman/listinfo/backgroundrb-devel > > As far as I know `sesid` is a unix call which sets the session id of a > "leader" process. All processes then spawned by that process belong to > the same session. Think a unix shell and any programs it starts up. > > I''m not sure what you need to do to get this work properly on windows > but that might help you turn up something. > > - GeoffHi, by the way: I had it working on another WinXP machine. Could it be that it depends on the CPU architecture (Intel/AMD)? Regards, Christian
On 4/8/07, Christian Schlaefcke <cschlaefcke at wms-network.de> wrote:> Geoff Garside schrieb: > > On 7 Apr 2007, at 20:20, Christian Schlaefcke wrote: > > > >> Hi Folks, > >> > >> I want to set up backgroundrb on my laptop to do some tests. But when I > >> run "scripts/background start" I get this error: > >> > >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in > >> > >> `setsid'': the setsid() function is unimplemented on this machine > >> (NotImplementedError) > >> from > >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/daemonize.rb:160:in > >> > >> `call_as_daemon'' > >> from > >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:191:in > >> > >> `start_proc'' > >> from > >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/application.rb:227:in > >> > >> `start'' > >> from > >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/controller.rb:69:in > >> > >> `run'' > >> from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb:182:in > >> `run_proc'' > >> from > >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb:105:in > >> `call'' > >> from > >> ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons/cmdline.rb:105:in > >> `catch_exceptions'' > >> from ruby/lib/ruby/gems/1.8/gems/daemons-1.0.5/lib/daemons.rb:181:in > >> `run_proc'' > >> from > >> Test/vendor/plugins/backgroundrb-0.2.1/server/lib/backgroundrb_server.rb:301:in > >> > >> `run'' > >> from Test/vendor/plugins/backgroundrb-0.2.1/script/backgroundrb:31 > >> > >> I had the fork-not-implemented-error before so I use "require > >> ''win32/process''" on my WinXP Notebook. This "setsid is unimplemented" is > >> new and even google could not tell me much about it. Anybody here who > >> experienced this error and could help with a workaround? > >> > >> Thanks & Regards, > >> > >> Christian > >> > >> > >> <cschlaefcke.vcf> > >> _______________________________________________ > >> Backgroundrb-devel mailing list > >> Backgroundrb-devel at rubyforge.org > >> http://rubyforge.org/mailman/listinfo/backgroundrb-devel > > > > As far as I know `sesid` is a unix call which sets the session id of a > > "leader" process. All processes then spawned by that process belong to > > the same session. Think a unix shell and any programs it starts up. > > > > I''m not sure what you need to do to get this work properly on windows > > but that might help you turn up something. > > > > - Geoff > > Hi, > > by the way: I had it working on another WinXP machine. Could it be that > it depends on the CPU architecture (Intel/AMD)?You had 0.2.1 working on Windows XP? thats wierd. -- gnufied ----------- There was only one Road; that it was like a great river: its springs were at every doorstep, and every path was its tributary. http://people.inxsasia.com/~hemant