> > > ----- Oryginalna wiadomoÅÄ ----- >> Od: "Roberto De Ioris" <[email protected]> >> Do: "uWSGI developers and users list" <[email protected]> >> WysÅane: piÄ tek, 4 marzec 2011 9:03:26 >> Temat: Re: [uWSGI] uWSGI 0.9.7-beta1 - emperor >> >> Fixed. >> >> This was caused by a bad usage of getsockname() (at least on gcc 4.5 >> this >> trigger the error you reported) >> > > now works correctly :] > thx > > > How to use SignalFramework to reload uWSGI after file modification ? > > Maybe there is something like this: > uwsgi.add_file_monitor(uwsgi.HUP, 'myfile.py') > > Do I need to register the signal.
Yes, you need to register it uwsgi.register_signal(1, uwsgi.reload) uwsgi.add_file_monitor(1, 'myfile.py') Obviously use the signal number you want (0-255) -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
