You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi, I noticed that runner with --daemonize option silently fails if pidfile dir doesn't exist. Which might be an issue, since tmp dir might be empty and when you don't specify pidfile path, it uses ./tmp/pids/good_job.pid and exists the process without any output.
Is this intentional or a bug? I'd suggest using mkdir_p at least for cases when the pidfile wasn't specified. I can put up a pull request if you're okay with that change.
The text was updated successfully, but these errors were encountered:
Hi, I noticed that runner with
--daemonize
option silently fails if pidfile dir doesn't exist. Which might be an issue, since tmp dir might be empty and when you don't specify pidfile path, it uses./tmp/pids/good_job.pid
and exists the process without any output.Is this intentional or a bug? I'd suggest using mkdir_p at least for cases when the pidfile wasn't specified. I can put up a pull request if you're okay with that change.
The text was updated successfully, but these errors were encountered: