I'm about to deploy my Pylons application and need to daemonize it and set up auto-restart if it dies. "paster serve production.ini start" does not daemonize it, contrary to what "paster serve --help" says. "paster serve --daemon production.ini" does, but it does not create a PID file so you can't stop it.
I made my configuration file executable and put this at the top: #!/usr/bin/env paster [exe] command = serve daemon = true pid_file = %(here)/data/paster.pid log_file = %(here)/data/error.log I can start it and stop it in daemon mode with "./production.ini start" and "./production.ini stop", but if I do "paster serve production.ini start" it starts up in normal console mode with logging to the console. Is this a bug in Paste? My other question is, paster has a --monitor-restart option to restart the server if it dies. But the Pylons Cookbook has recipes for daemontools and supervisor2. Are these better than paster's monitor for some reason, or are they all interchangeable? -- Mike Orr <[EMAIL PROTECTED]> --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
