Closed dentarg closed 10 years ago
I have
# cat trinidad-init-config.yml app_path: "/srv/apps/foo/current" ruby_compat_version: RUBY1_9 jruby_home: "/usr/local/ruby/jruby-1.7.0" output_path: "/etc/init.d" pid_file: "/srv/apps/foo/shared/pids/trinidad.pid" log_file: "/srv/apps/foo/shared/log/trinidad.log" jsvc_path: "/usr/bin/jsvc" trinidad_options: "-f config/trinidad.production.rb" trinidad_name: foo run_user: deploy
I did
# trinidad_init_service --defaults trinidad-init-config.yml Java home? [/usr/lib/jvm/java-6-sun-1.6.0.26/jre] moving trinidad to /etc/init.d NOTE: you might want to: `[sudo] update-rc.d -f /etc/init.d defaults`
Then I did as I was told:
# update-rc.d -f /etc/init.d defaults update-rc.d: using dependency based boot sequencing update-rc.d: error: unable to read /etc/init.d//etc/init.d
Instead doing
update-rc.d trinidad defaults
worked better.
I'm using trinidad_init_services-1.2.2 and
# uname -a Linux drift 2.6.32-5-amd64 #1 SMP Sun Sep 23 10:07:46 UTC 2012 x86_64 GNU/Linux # cat /etc/debian_version 6.0.6
should be fixed in 1.3.0 ... thanks!
I have
I did
Then I did as I was told:
Instead doing
worked better.
I'm using trinidad_init_services-1.2.2 and