Gary, this seems like a good tweak. Also during our LSARC meeting this morning, John F. suggested changing the word "shall" to "should" throughout the guidelines. These are not requirements, and the wording *should* be spacious :-)
Can you please make these two changes and send me an update, for reposting? Thanks, -tdc On Aug 26, 2008, at 10:30 AM, John Plocher wrote: > John Fischer wrote: >> John, >> Then rewrite the guideline to say something about correcting >> left over lock files and not lockfiles in general. This is >> my problem with the guideline. It is overly general. > > This is intended to be a best practice, and not a policy. As such, > it reflects the current best understanding of an area where guidance > is needed. Don't forget, good guidance is often overly general by > intent, simply because it needs to apply to a very diverse set of > applications. > >> Again, the guideline states: >>> * The product shall ensure that no files exist that can prevent the >>> product from running (i.e., lock files, temporary files, etc.) >> i.e., do not use lock files or temporary files to prevent >> the product from running. > > Using lockfiles to validly prevent an application from running when > it shouldn't is not the focus here - which should be obvious from the > context of the "how to best service things that are broken" document > itself. > > Tom/Gary: In order to prevent future misunderstandings like > this, please change the guideline above to read > > The product shall ensure that no files exist that can > improperly prevent the product from running (i.e., stale > lock files, temporary files, etc.) > > -John
