> On Mon, 27 Feb 2012 14:44:36 +0100 > Roberto De Ioris <[email protected]> wrote: > >> --need-app is dependent from the fork() configuration: >> >> In default mode (the master loading the applications) uWSGI will >> simply exit with code 22 (app failed). In lazy mode, the master will >> detect the code 22 and will respawn the processes until they fully >> load at least one app. > > This does not work in daemon mode (-d / 1.1 snapshot11) for PSGI app: > startup process exists with 0 although application fails later as we > can see it in the log. Removing -d brings intended behaviour. Is this > expected ? > >
Yes, it is expected, as daemonizing happens a lot earlier than app loading (so the exit code is the one from the parent process that is always 0). We could have a --daemonize2 (like we have pidfile2, chdir2 and logto2) to posticipate daemoniziation after app loading. Some objection ? -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
