Hi Chris,
I'd guess the issue is that god is starting your sh shell and the shell is
starting ruby, rather than god. I am not sure how god deals with processes
like these but I'd guess the issue not to be with bundle exec.
I'd suggest running resque scheduler directly without wrapping in sh -c if your
environment allows.
here's my w.start command that is confirmed to be working correctly under
bundle exec
w.start = "#{BIN_PATH}/bundle exec rake -f #{RAILS_ROOT}/Rakefile
resque:scheduler"
Hope this helps.
On Friday, March 16, 2012 at 11:36 AM, Christopher J. Bottaro wrote:
> Hello,
>
> I'm having a problem with god trying to watch a non-daemon process that is
> started by "bundle exec".
>
> God starts the process just fine, as seen by ps:
>
> 6856 ? Ss 0:00 sh -c bundle exec rake resque:scheduler >>
> /home/rails/project_a/shared/log/scheduler.log 2>&1
> 6860 ? Sl 0:23 ruby
> /home/rails/project_a/shared/bundle/ruby/1.9.1/bin/rake resque:scheduler
>
>
> The problem is that god is monitoring the first process (6856), so that a
> "god stop" or "god restart" nukes the first process, but the second one
> remains.
>
> Any ideas? Thanks for the help.
>
> --
> You received this message because you are subscribed to the Google Groups
> "god.rb" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/god-rb/-/W83Awd_b3mkJ.
> To post to this group, send email to [email protected]
> (mailto:[email protected]).
> To unsubscribe from this group, send email to
> [email protected]
> (mailto:[email protected]).
> For more options, visit this group at
> http://groups.google.com/group/god-rb?hl=en.
--
You received this message because you are subscribed to the Google Groups
"god.rb" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/god-rb?hl=en.
