Question

I have a Twiki installed and we're having problems with revisions not being tracked.

- for new files, the ,v files do not appear to be created

- for existing files, (eg: TWikiInstallationGuide) I can edit and save changes but my changes do not show up when I run a diff. Other changes do show up (ex: v1.53 & 1.52)

- Testenv says apachesrv must own the files so I've verified that apachesrv owns the files (using grep 'strict;$').

-Other than that testenv is clean (well the issue with locale is there but from other Support pages that's a non-issue)

- Running NTFilemon when I try to edit a file that is missing a ,v file, Twiki creates a .lock file but no ,v file

So where do the ,v files come from? Other Support posts suggest Twiki will create missing ,v files - any thoughts as to why is that not happening?

What else can I check?

My goal is to move this to new hardware, but my test bombed because while page rrevision is working under the fresh install, moving this data over broke it.

\\Greg Martin gmartin@etsPLEASENOSPAM.org

Environment

-- GregMartin - 14 Oct 2003

Answer

I'm not getting any help - here's what I've found

• The ,v files were not getting created due to an NT permissions problem. Looks like the apachesrv userid did not have some permissions
• So now I'm getting ,v files but still no differences are showing up

\\Greg

-- GregMartin - 20 Oct 2003

Providing the information requested in the SupportGuidelines (e.g. the complete testenv output) is a good way to increase your chances of getting some help. Searching with Google for similar problems is also a good way to go, as suggested on that page - this is basically a TWikiDebugging issue to figure out why the RCS commands are not being run properly, which has been covered many times. The ,v files are created by RCS commands, usually ci -l when creating a new page I think (full list is in TWiki.cfg).

It may also be useful to compare your configuration with the recommended config in WindowsInstallCookbook - if you didn't use the cookbook, re-installing based on the cookbook is probably the quickest option if you don't find a solution quickly.

This could also be a permissions issue or wrong userid, which is why testenv output would help. Another thing to check is that diff is accessible and in the same location as expected by RCS - if you use the WindowsInstallCookbook it takes care of this issue.

-- RichardDonkin - 21 Oct 2003

Richard thanks for getting back. I certainly understand the value of testenv which is why I referenced what I saw. testenv is now attached. (For some reason my browser wouldn't allow me to save the output of testenv at the time I opened the Support page or I would have. My apologies)

I also understand that my problem is not unique. I've been unable to find an answer which is why posted here.

I did use the WindowsInstallCookbook. So far as I know I did not deviate from it. Currently the RCS files are locked as apachesrv which is the local user acct Apache runs under.

What I'm seeing at this point is that new files .txt & .txt,v are being created with severly restricted ACLs such that even the apachesrv account, System and Everyone only have Read rights to the newly created files. I do not understand why the new files are not inheriting the ACLs of the parent directory. Since parent rights should be inherited, I cannot understand what is happening. This, of course, appears to prevent RCS from deleting the ,v files.

\\Greg

-- GregMartin - 21 Oct 2003