Mike Perham
2363cef312
Remove more USR1 references
2017-01-03 15:41:48 -08:00
Vicent Llongo
1e715903dc
Set kill timeout to 15 sec. in upstart config
2016-05-18 23:25:29 +03:00
Mike Perham
6e48ed8a4f
Fix #2440
2015-07-16 13:27:18 -07:00
Mike Perham
751488250e
Add support for quiet in Upstart
2015-07-15 12:39:44 -07:00
Mike Perham
8b29f3d201
Remove upstart/manage-many since no one is maintaining it
2015-07-15 12:39:13 -07:00
Maksym Pugach
7e43f70ff4
shutdown all upstart instances on workers stop
2015-07-08 15:21:02 +03:00
Mike Perham
0de36350fb
sidekiq.conf does not start automatically on its own, fixes #2401
2015-06-22 09:19:59 -07:00
James
71bceee9a9
Don't mange sidekiq
...
It works better without the tooth marks.
2015-06-18 15:54:30 +01:00
Mike Perham
54caccd04f
Use bundle exec, not binstub
2015-06-04 06:54:16 -07:00
Abdelkader Boudih
a5e5535472
restore sidekiq manager event.
2015-04-02 13:43:15 +00:00
Robin Böning
9d1d94d45d
Add start on certain runlevel for example configs
2015-04-02 15:24:13 +02:00
Mike Perham
811f005d56
Merge pull request #2078 from pote/improve_bash_in_upstart_example
...
More readable for loop in upstart example
2014-12-07 15:11:44 -08:00
pote
ac86717490
More readable for loop
2014-12-07 21:01:52 -02:00
David Moulton
cb3bb721ef
changed location of pid file in upstart example to be in the app
...
directory, named sidekiq-n
2014-12-05 14:23:17 -07:00
Parker Selbert
b40def9451
Remove fifo logger examples from upstart conf
...
Simply notes the default log location and synchronizes the one and many
example configs.
2014-11-10 14:09:49 -06:00
Parker Selbert
20e686be3a
Use a named pipe for logging in upstart example
...
The ability to log directly to /dev/kmsg was removed in Ubuntu 14.04,
making the existing example config fail to perform any real logging.
Appending a pipe to the last `exec` within the `script` block gives
upstart an incorrect PID to work with, which can lead to various issues.
This uses a FIFO solution that logs to syslog at any permission level
and doesn't leave anything on the file system afterwards.
2014-11-10 11:52:23 -06:00
hartator
9890cbf09e
Update sidekiq.conf
2014-10-30 00:45:52 -06:00
josh
e12b00e9c3
add support optional for user installed rbenv
2014-10-22 16:54:29 +07:00
Mike Perham
f29c770ef3
Fixes from https://stackoverflow.com/questions/26439555/did-upstart-or-bash-scripts-change-on-ubuntu-14-04-trying-to-boot-sidekiq-with
2014-10-19 15:03:36 -07:00
Mike Perham
c3c4d529f7
Sidekiq does not exit on USR1, so we shouldn't need to tell Upstart about it
2014-07-28 13:50:47 -07:00
Mike Perham
e2db9945c1
Dont need to spec config file, fix pidfile name
2014-04-28 20:28:00 -07:00
Jakob Hilden
56a9738956
fixed documentation (file name has changed)
2014-03-24 20:38:11 +01:00
Mike Perham
bbbe318a6c
Lots of cleanup
2014-03-09 14:59:55 -07:00
Thilo Utke
e99a212b1f
Update sidekiq-manager.conf
...
changed the example service commands as upstart uses the config file name.
2013-12-10 12:57:15 +01:00
August Jaenicke
7687e2ff29
uncomment out normal exit codes in upstart examples
2013-10-03 11:46:28 -07:00
August Jaenicke
f18aea4914
Added comments in upstart sidekiq.conf files about normal exit codes to avoid unintentional respawns.
2013-10-03 11:18:05 -07:00
Richard Peng
3bedebb988
make sure sidekiq processes receive proper stop signals
2013-05-23 11:52:23 -04:00
Darío Javier Cravero
5a39a6563d
Added support for many Sidekiq instances on the upstart script.
2013-03-09 19:10:59 -03:00
Mike Perham
82abcb02d9
Pull in latest clymb upstart config for example
2013-02-18 21:19:14 -08:00
