<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Patrick R. Michaud wrote:
<blockquote cite="mid20070330172356.GG15621@host.pmichaud.com"
type="cite">
<pre wrap="">On Fri, Mar 30, 2007 at 11:54:01AM -0400, Henrik wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I use PmWiki for buckets of websites on a single Unix webserver account.
All was going well until my hosting company upgraded my shared hosting
server to PHP 5.2.1. A good thing to upgrade, but all of a sudden all my
wikis broke, with "unable to obtain .flock file" (among other things).
After several days of (in the end) pointless dialog with my host service
company (webserve.ca), I ended up having to change rights on all wiki.d
and uploads directories from 755 to 777. I presume this means that
whereas PHP previously had owner rights, it now has none, and therefore
needs public access to write directories.
Does anyone know where to look for a configuration change on my host
that would make this happen?
</pre>
</blockquote>
<pre wrap=""><!---->
I'm not sure that a PHP configuration change alone can explain the
entire issue. It would help to know the ownerships for files created
before the change versus the ownerships of the files being created
after the change -- I suspect that the userid also changed in
the process somewhere.
Were the directories really 755 permissions (as opposed to
775) before the upgrade occurred? If the directories were 755
and the files created by PmWiki were 644, that would imply that
previous PmWiki (and PHP) were running under your userid instead
of the "nobody" or "www" user.
</pre>
</blockquote>
FYI, this case seems remarkably like what recently happened to me when
I recently migrated a couple wikis to a new host. I had to go back and
reset all of the permissions in multiple wikis. Perhaps when they
upgraded, everything was also transferred to a new server, and, in the
process, the directory settings were also changed? <br>
<br>
Also, as part of this migration, I moved a Gallery (v1.5) to the new
hos. While setting up in the Gallery config program, a dialog box came
up with some comment about how the host server has some sort of php
server permissions setting that might mess things up, but the config
program would try to "fix it". Since the Gallery runs, I assumed that
the config program resolved the permissions setting problem. Sorry
about being vague, but since the config program self corrected the
problem without my intervention, all I remember was some warning dialog
box popping up with a click to continue button. <br>
<pre class="moz-signature" cols="72">--
Always, Dr Fred C
<a class="moz-txt-link-abbreviated" href="mailto:drfredc@drfredc.com">drfredc@drfredc.com</a></pre>
</body>
</html>