> > >> >> I am heavily studying the gccgo project, and maybe it is a better >> approach >> for uWSGI (in the short term) >> >> Go 1.0.x continue to be supported, as well as go 1.1 without >> master,processes, mules, spoolers (ehm, what remains ???) >> > > > Does that reduce the value proposition of uwsgi + Go?
yes, extremely > > I get the following: > > gracefully (RE)spawned uWSGI master process (pid: 5364) > spawned uWSGI worker 1 (pid: 5368, cores: 1) > mach error semaphore_wait: 15 > fatal error: mach error > > goroutine 1 [runnable]: > uwsgi._Cfunc_uwsgi_init(0x2, 0x15200000, 0x0, 0x400000001) > uwsgi/_obj/_cgo_defun.c:149 +0x2f > uwsgi.Run() > uwsgi/_obj/_cgo_gotypes.go:4211 +0xef > main.main() > /Users/0x6e6562/Workspace/src/main.go:33 +0x13a > this is caused by go 1.1 expecting threads that are no more running after fork(). All of the "touch" features, requires the master, so you are out of luck with go 1.1 -- Roberto De Ioris http://unbit.it _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
