Re: contrib 1.2.1 for PyBlosxom 1.2 release

On Mon, 9 May 2005, Joseph Reagle wrote:
>
> I spent a chunk of time and actually got the logging working briefly. 
> There's some very odd side-effects in the server environ. Clearly, 
> uploading local pyc's to the server is bad. But even if I delete all the 
> pyc's on the server -- and I expect them to be regenerated -- they're 
> not. For example, I can be having pages served, but after:
>
> [[[
> manganese.sabren.com:/home/reagle/data/2web/reagle.org/joseph> find
> ~/data/2web/pyblosxom-1.2/ -name "*.pyc" -exec rm {} \;
> ]]]
>
> I'll get a "ImportError: No module named comments
>      args = ('No module named comments',)"
>
> But running pyblosxom2.cgi  from the command line, then the server version
> begins working again. If I edit any file, I also have to run that script
> manually to get the changes to be operational, but it doesn't always
> work!?! Why would this be?

What's going on is that you're not running Apache with suexec.  There's 
nothing wrong with that, but what happens is that Apache doesn't have 
write access to the plugins directory.  When you edit plugins or remove 
the .pyc files then go view your blog through a web-browser, Apache goes 
to run the pyblosxom script as whatever Apache runs as and can't write the 
.pyc files to the directory with the plugins.

If you were running with suexec, then Apache would run the pyblosxom.cgi 
script as you and thus would have the file/directory access it needed to 
do things like generate .pyc files.

So that's why you're seeing what you're seeing.  I'll make a note of it in 
the next rev of the manual.

<insert discussion about the pros and cons of suexec usage here>

/will


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click