On Mon, 2005-04-04 at 12:02 +0200, COLLOT Jean-Yves wrote: > > I don't understand difference 3. It could be some privilege or file > > protection issue. However, I try with users without any privileges, > > and my file protection, as far as I know, are the same as > Ben's, and I > > can't get the same results. Could you give me all the details about > > the file protections and the characteristics of your users? > > Users are all unprivileged and belong to the [dv,*] group. > Nightly, a generic "dymax" user (also unprivileged) handles > batch processing of our "task" files. Thus, on a typical > morning when I'm deciding what to do for the day, my task > file initially is owned by [dv,dymax]. Several seconds after > I start editing this file with Cream, the warning message is > triggered. If I write the file, it becomes owned by [dv,bg] (my vms > uid) and no further warnings appear. If I subsequently edit > this file now owned by [dv,bg] the warning no longer appears. > Also, if, before I start editing, I change the ownership > alone (e.g. by set file/own=bg from a privileged account) and > edit it (i.e. without first changing the file type from > Variable to Stream) the warning no longer appears. So far as > I can see, ownership is definitely a factor.
I just noticed something further about this unresolved issue that is puzzling me quite a bit. I wonder if these observations will help us understand what is going on. Today I was editing a file not owned by me using Cream and was greeted with the regular "file has changed" error. I then wrote the file using Cream's "Save" and continued editing. Later in the session I received the same message *again* and again I did a "Save". I noticed at that point that even though I had saved the file as my own UID [DV,BG] it was still owned by [DV,DYMAX]! I resumed my edits and then exited Cream, saving my final changes, resulting in a file with the following ownership & dates: BG.TAS;1 File ID: (11239,469,0) Size: 1001/1035 Owner: [DV,DYMAX] Created: 5-JUN-2005 23:59:11.76 Revised: 6-JUN-2005 11:06:08.21 (33) Expires: 6-JUN-2015 11:06:08.21 So as you can see, bg.tas ends up with a "Revised" date reflecting the latest write to the file, but retains the original ownership & creation date from when [DV,DYMAX] took ownership of the file in the previous night's regular batch processing. However, if I copy this file into my home directory (so it is now owned by me) and then do a "Save," each time I save the file both the "Created" and the "Revised" dates are updated to reflect the current time (in spite of the fact that the file version# is not incremented!) [ There is one difference in our setup here that I think I may have failed to mention before: because we implement our own method of keeping track of current & prior versions of files, we have the "version limit" set on most directories and files, including this bg.tas, to be = 1. Does setting /ver=1 help you reproduce my problem? Still, I wonder if this isn't a red herring. I tried setting /ver=2 on the file (still owned by [DV,DYMAX]) and edited it again with Cream. Again the "file has changed" error occurred, and again the file ownership remained as [DV,DYMAX] after writing the file & the ownership & "Created" date remained the same, while the "Revised" date changed. ] Ben PLEASE READ THIS IMPORTANT ETIQUETTE MESSAGE BEFORE POSTING: http://www.catb.org/~esr/faqs/smart-questions.html
