from web2py's standpoint, having someone else (the nssm process) to care for service integration is more straightforward, i.e. it runs exactly as if it was launched "normally". Of course winservice.py can be patched and fixed etc etc etc but either someone takes care of testing it under every Windows OS, for every web2py release, for every web2py feature, or it will remain as something that "sometimes work, sometimes doesn't".
Given that for each job there's "a best tool", and that the "best tool" for this job is: - free - available - requires no absolute time to set up I'd go for nssm all the times (and that's why a slice was posted at http://www.web2pyslices.com/slice/show/1614/nssm-webserver-and-scheduler-as-services-in-windows-oses on the matter) -- --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
