On Wed, Nov 18, 2009 at 11:42 AM, alex ko <[email protected]>wrote:
> Hi Kenneth,
>
> Thanks a lot for your prompt reply and your commitment.
> I have some success with ruote-kit on win32 so far with one remark:
>
> C:\Users\Alex\Documents\IT\ruote-kit>ruby -e 'puts
> Signal.list.keys.join(" ")'
> TERM SEGV KILL EXIT INT FPE ABRT ILL
>
> So I had to comment out lines 56 - 66 in initializer.rb as follows:
>
> C:/Ruby/lib/ruby/gems/1.8/gems/daemon-kit-0.1.7.10/lib/daemon_kit/
> initializer.rb
>
> def initialize_logger
> return if DaemonKit.logger
>
> unless logger = configuration.logger
> logger = AbstractLogger.new( configuration.log_path )
> logger.level = configuration.log_level
> logger.copy_to_stdout = configuration.log_stdout
> end
>
> DaemonKit.logger = logger
>
> DaemonKit.logger.info "DaemonKit (#{DaemonKit::VERSION}) booting
> in #{DAEMON_ENV} mode"
>
> # configuration.trap("USR1") {
> # DaemonKit.logger.level =
> DaemonKit.logger.debug? ? :info : :debug
> # DaemonKit.logger.info "Log level changed to #
> {DaemonKit.logger.debug? ? 'DEBUG' : 'INFO' }"
> # }
> # configuration.trap("USR2") {
> # DaemonKit.logger.level = :debug
> # DaemonKit.logger.info "Log level changed to DEBUG"
> # }
> # configuration.trap("HUP") {
> # DaemonKit.logger.close
> # }
> end
>
> I know this is awful but it's my best so far. :)
>
This is a big step towards having windows support. I've discussed with a
couple of folks in #daemon-kit what would be required for windows support
and it doesn't seem like too big an issue. Having it as a Windows service
might be another can of worms I have yet to uncover.
Nonetheless, I've made sure daemon-kit doesn't try to trap signals not
supported by underlying OS (
http://github.com/kennethkalmer/daemon-kit/commit/afc66399e7a9339e73934df21768ccdbd00d5d55).
Thanks a lot for this !
I loaded one XML simple process definition through "Launch a new
> process" and it seems persistent over server restarts. Is there any
> kind of fluo available in ruote-kit? Also the process list shows only
> the number of processes at the moment.
>
Today has seen me apply all my working time on ruote-kit, so a lot of the
existing interfaces have been updated a lot since your last clone.
> Can you help me please with the way how to define participants?
>
> I found some of generators available:
> [amqp, cron, cucumber, jabber, nanite_agent, rspec, ruote]
> and generated jabber and ruote samples. Can someone give me a hint how
> to start them?
>
> At the moment I have huge lack of even basic ruote knowledge so I
> apologies for my newbish questions and appreciate any help.
>
This is going to be the tricky part. In order for us (the community) to help
you here we need to have an idea of what you want to achieve with ruote.
Don't worry about getting the terms right or mixing project names, we just
need some feeling for your direction so we can make sure you stay on course.
We're working hard on trying to understand all the issues people have when
exposed to the ecosystem so we can iron them out and communicate more
clearly how everything fits together. I have to admit, a little over a year
ago when I ventured down this path it was just as daunting to me, I am now
forever grateful that I stuck with it and got to understand how it all plugs
in.
Best
--
Kenneth Kalmer
[email protected]
http://opensourcery.co.za
@kennethkalmer
--
you received this message because you are subscribed to the "ruote users" group.
to post : send email to [email protected]
to unsubscribe : send email to [email protected]
more options : http://groups.google.com/group/openwferu-users?hl=en
