Date: Wed, 20 Mar 2002 14:05:23 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Jens Schweikhardt <schweikh@schweikhardt.net> Cc: freebsd-audit@FreeBSD.ORG, joerg@FreeBSD.ORG Subject: Re: crontab changes for PR bin/22612; please comment Message-ID: <p0510151fb8be8b748a93@[128.113.24.47]> In-Reply-To: <20020320192624.A1258@schweikhardt.net> References: <20020318130904.A3869@schweikhardt.net> <p05101502b8bc01b04024@[128.113.24.47]> <20020320192624.A1258@schweikhardt.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 7:26 PM +0100 3/20/02, Jens Schweikhardt wrote: >Hmm. What about completely removing the test whether the >tmp file was modified? Just try to install the crontab, >no matter what. Or is there a reason why crontab files >must not be installed if they havn't changed? I don't know if there are any technical reasons, but I would want the check there for the peace of mine of the user. Let's say you start to edit a crontab, and then really screw it up due to some typos or something. You know it's screwed up, so you just want to bail out. You type :q! and you then see the message "installing new crontab". You then think -- "Oh no! What just happened?!?" In that situation, I would rather keep the current behavior, where you see "no changes made to crontab". -- Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu Senior Systems Programmer or gad@freebsd.org Rensselaer Polytechnic Institute or drosih@rpi.edu To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-audit" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p0510151fb8be8b748a93>