That worked (--attach-daemon). Thank you.
On Sun, Feb 9, 2014 at 10:42 AM, Roberto De Ioris <[email protected]> wrote: > > > Hi, > > > > I tried starting the python scheduler (web2py) via uwsgi like this - > > smart-attach-daemon = /opt/python/bin/python /var/www/web2py/web2py.py > > -K everest > > The scheduler did start, but I have entries like this in the uwsgi log - > > > > [uwsgi-daemons] spawning " /var/www/web2py/web2py.py -K everest" (uid: > > 499 gid: 499) > > Thu Feb 6 23:21:46 2014 - [uwsgi-daemons] " /var/www/web2py/web2py.py > > -K > > everest" (pid: 21570) *did not daemoniz*e !!! > > > > The "did not daemonize" keeps getting printed over and over. If I stop > > uwsgi, the scheduler does not stop. I have to kill it. > > > > How can I fix these 2 issues? > > > > Regards, > > Jayadevan > > > "smart" variants expect your process to daemonize. > > If it is not the case (as suggested by your logs) use the simple > --attach-daemon. > > If you prefer the web2py scheduler to "stay alive" after uWSGI reload use > --smart-attach-daemon2 that will daemonize the process for you: > > http://uwsgi-docs.readthedocs.org/en/latest/AttachingDaemons.html > > > -- > Roberto De Ioris > http://unbit.it > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
