I received by e-mail this kind of error. I would appreciate if some one could help me.

Thank you

The command was: "submitPart"
The message is: "RCS "/usr/bin/ci -l -mnull -t-null /home/httpd/cgi-bin/fom-serve/item//244 fom-meta//RCS/244,v" failed: (1, 0, Illegal seek, fom-meta//RCS/244,v  <--  /home/httpd/cgi-bin/fom-serve/item//244
ci: fom-meta//RCS/244,v: no lock set by apache
, ARRAY(0x82dcbdc), pid=5563, wrc=5563)".
The process number is: 5562
The user had given this ID: <(noID)>
The browser was: <Mozilla/5.0 (compatible; Konqueror/2.0; X11); Supports MD5-Digest; Supports gzip encoding> 

This kind of error happens if the username of the user running the CGI changes
after the RCS database has been created. The old "user" still has every file
checked out and "locked," preventing the new "user" from tweaking them.


Possible fixes:

1. Change $RCSuser to the original username that has the files locked. This won't work
if some of the (new) RCS files are now locked by the new user.

2. Perform an 'rcs -u RCS/*,v' to remove the lock mark from all of the RCS files. I'm
not sure if you need to be any trickier than this.

3. Remove all of the RCS/*,v files, and allow FOM to rebuild them as it goes. This
approach is a bummer if you prefer to keep the history of your files.

4. Get extremely tricky and write a script to "repair" the lock annotations inside all
of the RCS files. But this seems needlessly risky. I'd be surprised if #2 didn't work.

I solved the problem in this way:
#unlock
rcs -M -u RCS/*,v #to avoid to enter a comment

su nobody or apache #to lock again
#lock
rcs -l -M RCS/*,v 

then, you can rebuild the dependencies
with fom?cmd=install