[Pmwiki-users] diff process runaway

[Patrick R. Michaud]

Oh, I need a *lot* more information to diagnose this one...

What version of PmWiki?  What version of PHP?  What OS?  This is the
first time in three years I've heard of a problem with a runaway diff...

You can add $EnableDiag=1; to your config.php file and then run pmwiki
with the ?action=phpinfo option to get more details about OS and PHP
version.  Also, if you can send me the URL that would be helpful too.

Finally, there's the phpdiff.php script which provides a PHP-based
replacement for diff(1), I'll send along more details a bit later
(but would really appreciate knowing the version numbers on the above
asap).

Pm



On Thu, Oct 07, 2004 at 09:30:11PM -0700, Joshua Hunter wrote:
> I got an unhappy email from the IT staff of the university I work at:
> 
> "Your 'php pmwiki.php' process on the staff webserver had spawned a 'diff'
> process that was using 100% of the processor on one of the servers.
> 
> Many other 'php pmwiki.php' processes were also running, but seemed to be
> rapidly created and destroyed again.
> 
> These runaway processes used 1013.79 cpu minutes before I killed them. (see
> output of 'assets' below)"
> 
> Some experimenting has showed that the diff process runs out of
> control whenever I save command on text that is greater than the text
> editing box.  (that is the scroll bar becomes visible).  Short pages
> save fine.  Everything else runs fine without incident.
> 
> I can then shell out and run a kill command on the diff process.  Once
> the kill command is complete the page is saved and looks fine. 
> Obviously I can't run this command on every edit of every page that is
> greater than one page long.
> 
> Any suggestions?
> 
> -- 
> Pmwiki-users mailing list
> Pmwiki-users at pmichaud.com
> http://pmichaud.com/mailman/listinfo/pmwiki-users_pmichaud.com