I did some work today to try to fix Cruise daemonization. Everything looks ok to me on my Mac and Ruby 1.9.2 but I'm having trouble installing and running JRuby locally. If others could take a poke at this I'd greatly appreciate it.
Also, as far as I know, we don't need or use anything in the daemon/ subdirectory now; we're relying on Rails' server daemonization, the killtree script, and straight-up kill to do the work. The init.rb#stop_server method is using kill -KILL rather than kill -INT, which is what I'd prefer, because shutting down the process using -INT while the server is daemonized in Prod mode seems to cause an infinite loop that I haven't locked down yet. Doesn't seem to happen in dev mode. Builders are now creating and cleaning up their own pid files, rather than Platform creating the pid files at builder start time (and getting cleaned up, well, never). If someone could explain why Cruise is creating and using both .pid files and individual builder.lock files that would be extremely helpful to me as a maintainer, since I wasn't around for the creation of that code. After this, nothing much is keeping us from cutting an RC1. Brian _______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
