Question

I just set up a TWiki instance of Windows using the WindowsInstallCookbook. I'm running my Apache service as a local user (apache_user, NOT using a system account), so when I re-locked the RCS files, I changed the locks from nobody to apache_user.

After starting up TWiki, I set up basic auth and am now able to edit my site after logging in. The problem is that every new page I create is locked in rcs by the system user. All of the original pages are still locked by apache_user; it's just the new ones that I'm having a problem with.

The end result is that my version numbers on the new pages never increase past 1.1.

Another odd side affect is that my changes to existing pages also aren't updated. When I edited the TWiki/WelcomeGuest page, it didn't increment the Rcs number. The page is updated, but I can view the diff. This page is "rcs-locked" by the apache_user.

So the new pages are rcs-locked by system and I can't increment the revision past 1.1. All existing pages are rcs-locked by apache_user, and I can't increment the rcs revision.

Thanks in advance for any help!

Also, I fogot to mention that I looked at the RCSNotTrackingChangesOrViews topic and, while it seems very similar, it did not fix my problem.

Environment

-- TomPurl - 20 Sep 2005

Answer

If you answer a question - or someone answered one of your questions - please remember to edit the page and set the status to answered. The status selector is below the edit box.

I fixed my own problem. When I ran http://url/bin/testenv, I found that my cgi scripts were running under the system user (by looking at the LOGNAME variable). I then edited httpd.conf LOGNAME directive so that it was apache_user instead of system, and re-locked my rcs files using a slight variation on the command found in the WindowsInstallCookbook.

-- TomPurl - 21 Sep 2005

Yes. And that makes me wonder whether IsRelockMandatory. Simply changing the SetEnv LOGNAME in the httpd.conf would be, if it works correctly as seems for me, a lot easier and less error prone than a relock.

-- JeromeBouvattier - 21 Sep 2005