From: Chris N. <cni...@fo...> - 2013-03-08 18:49:25
|
On Fri, Mar 8, 2013 at 1:35 PM, Chris Nighswonger <cni...@fo...> wrote: > On Fri, Mar 8, 2013 at 1:07 PM, Jamie Cameron <jca...@we...> wrote: >> >> Perhaps forcing a change of package (as happens in that block) is the >> cause of the problem? > > I thought the same thing. So I ran a one-liner from the cli doing and > eval and forcing a package change. Sure enough: it threw the same > error. Sadly, though, when I commented out the package change in > miniserv, it still borked. > > Also, when using the very simple script in which the actual Python was > embedded, forcing a package change made no difference. The simple > script worked either way. When I force the module cgi script to be executed in the root user's env (by changing the shebang line to #!/usr/bin/env /usr/bin/perl), it works and miniserv borks due to the lack of headers (which is what I would expect). So something must differ from root's environment in the environment miniserv executes the script in. At present I don't see any significant difference, however. Kind Regards, Chris |