Jens Elkner
Jens Elkner
Actually the platform independent, universal (IMHO correct) way is to make the process a daemon and let the parent process exit with `0`, if it is known, that the config...
... > However, that doesn't need to be mutually exclusive with also signalling readyness via the systemd notification socket. Yepp, but overhead, which needs to be maintained, too. And just...
My guts say, `2 + Runtime.getRuntime().availableProcessors()` should be enough. However, today most instances probably run in a zone[like environment], which is not the only one wrt. the bare metal box....
The problem is, that you do not pass `PYTHONPATH` but set it to a new, possibly unexpected value ... Therefore I use the following workaround in our cluster: ``` export...
Don't understand, why there need to be 3 files for the same? purpose. Which one should be taken? The timeout should be a param as well, so that it can...
No - this is a no go. This way the application logic is pushed back to the starter script which is wrong, buys us nothing (especially because Linux has no...
Okidoki, I'll try it ... :)
The service (i.e. sidekiq_wrapper) does not daemonize itself, but every service always should after it has validated config[s] and runability (started needed workers) successfully. If not, it should exit wqith...
Waiting for sidekiq service wrapper ...
Well, not surprising for me because travis env is precise aka 12.04 release ( not supported by hets anymore) and thus is probably using an outdated hets version (actually it...