rpms
/
uwsgi
2
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
42 Commits 19 Branches 29 Tags 325 KiB
RPM Spec 80.9%
Diff 17.4%
Shell 1.7%
Go to file
Jorge Gallegos c04fd62ef2 This was actually right. From the documentation 
> By default sending the SIGTERM signal to uWSGI means "brutally
> reload the stack" while the convention is to shut an application
> down on SIGTERM. To shutdown uWSGI use SIGINT or SIGQUIT instead.
> If you absolutely can not live with uWSGI being so disrespectful
> towards SIGTERM, by all means enable the die-on-term option.

(https://uwsgi-docs.readthedocs.org/en/latest/ThingsToKnow.html)

And:

> Sending SIGHUP to the Emperor will reload all vassals.

(https://uwsgi-docs.readthedocs.org/en/latest/Emperor.html)
 		2013-10-05 12:18:13 -07:00
.gitignore Perhaps it will hold this time? 2013-10-02 22:27:14 -07:00
emperor.ini Enabling stats log socket, and capabilities 2013-10-05 12:17:36 -07:00
fedora.ini Use the right plugin names 2013-10-04 09:57:06 -07:00
sources Perhaps it will hold this time? 2013-10-02 22:27:14 -07:00
uwsgi.service This was actually right. From the documentation 2013-10-05 12:18:13 -07:00
uwsgi.spec More patches. If this works will send upstream 2013-10-04 15:43:08 -07:00
uwsgi_fix_jvm_in_arm.patch More patches. If this works will send upstream 2013-10-04 15:43:08 -07:00
uwsgi_fix_lua.patch Updated patches to match 1.9.17 tree 2013-10-02 22:23:06 -07:00
uwsgi_fix_rpath.patch Updated patches to match 1.9.17 tree 2013-10-02 22:23:06 -07:00
uwsgi_ruby20_compatibility.patch Bumped version to 1.9.8 for f19 2013-04-23 22:17:02 -07:00
uwsgi_trick_chroot_rpmbuild.patch Bumped version to 1.9.8 for f19 2013-04-23 22:17:02 -07:00