I just run XSP with /etc/init.d/xsp start, xsp runs with aspnet user and therefore creates /tmp/.wapi with owner being aspnet. Then if i stop XSP and start mod-mono-server (either with /etc/init.d/mod-mono-server start or automatically by apache module mod_mono), mod-mono-server can not access /tmp/.wapi because mod-mono-server runs with apache user and does not have permission to access /tmp/.wapi created by xsp. Reproducible: Always Steps to Reproduce: 1./etc/init.d/xsp start 2./etc/init.d/xsp stop 3./etc/init.d/mod-mono-server start Actual Results: mod-mono-server doesn't start at all Expected Results: mod-mono-server should be able to access /tmp/.wapi and should start normally. I am running mono-1.1.7, xsp-1.0.8 and mod_mono-1.0.8-r1. Applied patch from bug 70943 to have /etc/init.d/mod-mono-server installed (http://bugs.gentoo.org/attachment.cgi?id=53686&action=view). See also http://bugs.gentoo.org/show_bug.cgi?id=70943#c8.
Created attachment 88221 [details, diff] /etc/init.d/xsp patch to make it start
Created attachment 88222 [details, diff] /etc/init.d/mod-mono-server patch to make it start
Here's a couple of patches for /etc/init.d/xsp and /etc/init.d/mod-mono-server it fixes this little conflict and also closes bug #92338
Is it the fact that the file exists after the init script stops the process? I'd rather force remove the file than chmod it every time. To me that almost creates a minor security risk.
i don't know the details about what's in .wapi... but it works if you rm -rf it every time :)
xsp and mod-mono-server now both run using aspnet user rather than apache user. Thanks
