Subject: Re: bin/7662: crontab(1) does not always save changed crontab file
To: NetBSD Bugs and PR posting List <firstname.lastname@example.org>
From: Andrew Brown <email@example.com>
Date: 06/02/1999 21:53:14
>> the proposition: simply to adjust the mtime of the temp file back to
>> the mtime of the original crontab file being edited. any saved data
>> would automatically move the mtime to "now", providing proff that the
>> file was at least saved, if not changed. then you'd only lose if you
>> did two complete edits within one second. things being what they are,
>> i only discovered this bug because i was trying to do one edit within
>> a second.
>Yes, this does solve this particular sub-class of the "has this file
>been written to" problem. However this only solves the problem if the
>parent process has made a copy of the file to be manipulated.
well...uh...yeah. but in the case where the parent process *hasn't*
made a copy, the newly-perhaps-saved file doesn't need to be "checked
in". unless you're thinking of some other application like this?
|-----< "CODE WARRIOR" >-----|
firstname.lastname@example.org * "ah! i see you have the internet
email@example.com (Andrew Brown) that goes *ping*!"
firstname.lastname@example.org * "information is power -- share the wealth."