OK, getting a bit further with this :-) So after rebuilding uwsgi (updated to 1aac5be), rebuilding the handler code, the rebuild was triggered by a change to the underling file, but it ended with a bad address error:
Tue May 7 14:56:01 2013 - [uwsgi-touch-exec] running go build main3.go Tue May 7 14:56:02 2013 - *** /Users/0x6e6562/Workspace/src/main3 has been touched... grace them all !!! *** gateway "uWSGI http 1" has been buried (pid: 92886) ...gracefully killing workers... subprocess 92891 exited with code 0 Gracefully killing worker 1 (pid: 92885)... worker 1 buried after 1 seconds binary reloading uWSGI... chdir() to /Users/0x6e6562/Workspace/src closing all non-uwsgi socket fds > 2 (max_fd = 2560)... found fd 3 mapped to socket 0 (127.0.0.1:56274) running /Users/0x6e6562/Workspace/src/main3 execvp(): Bad address [core/master_utils.c line 443] I'll have a look into the master_utils module. On Tue, May 7, 2013 at 2:17 PM, Roberto De Ioris <[email protected]> wrote: > > > OK I see what you mean. I've now pulled the latest uwsgi from Github > > (d6eecd1) and that seems to fixed the issue with the reload :-) > > > > So now that the reload is working for changes to the underlying source > > file, what would be better is for the reload to get triggered by changes > > to > > the newly compiled file - is this a case of pointing the --touch-reload > at > > the resulting binary? > > > > Also, I imagine there isn't any magic to have the whole re-compile and > > reload procedure get kicked off when the source file is saved in an > > editor? > > > > > > Try this (after having pulled new uwsgi code from github): > > [uwsgi] > http = :9090 > http-modifier1 = 11 > touch-exec = /home/foobar/test.go go build test.go > touch-reload = /home/foobar/test > > this should trigger a compilation whenever test.go changes, and a reload > as soon as the binary changes > > > -- > 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
