Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syslog support #26

Open
nevans opened this issue Apr 5, 2011 · 2 comments
Open

syslog support #26

nevans opened this issue Apr 5, 2011 · 2 comments

Comments

@nevans
Copy link
Collaborator

nevans commented Apr 5, 2011

No description provided.

@nevans
Copy link
Collaborator Author

nevans commented Apr 5, 2011

shouldn't be hard at all. see Heroku's blog post: Logs are Streams, Not Files

@benprew
Copy link

benprew commented Sep 14, 2016

I know this is an old issue, but wanted to add syslog support to resque-pool, but then I realized I probably didn't need to, I can handle it in the init script (with bash). Though it does mean I have to background the command instead of using --daemonize:

bundle exec resque-pool \
  --pidfile $PIDFILE \
  > >(logger -p user.info -t "$NAME") \
  2> >(logger -p user.warn -t "$NAME") &

Maybe this is just adding this to the init scripts examples or mentioning it in the readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants