Date: Sun, 21 Jan 2001 17:55:37 -0500 From: Sergey Babkin <babkin@bellatlantic.net> To: Greg Black <gjb@gbch.net> Cc: Neil Blakey-Milner <nbm@mithrandr.moria.org>, Matt Dillon <dillon@earth.backplane.com>, John Gregor <johng@vieo.com>, Gerhard.Sittig@gmx.net, leifn@neland.dk, freebsd-hackers@FreeBSD.ORG Subject: Re: how to test out cron.c changes? (was: cvs commit: src/etc crontab) Message-ID: <3A6B68E9.278A6BBB@bellatlantic.net> References: <200101140244.f0E2i3518278@vieo.com> <3A621ABF.FA2C6432@bellatlantic.net> <200101142155.f0ELtLO64117@earth.backplane.com> <3A6A059C.486F6237@bellatlantic.net> <20010120235412.A42508@rapier.smartspace.co.za> <3A6B3D85.9773C9ED@bellatlantic.net> <nospam-3a6b44dfe00a3f3@maxim.gbch.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Greg Black wrote: > > Sergey Babkin wrote: > > > Neil Blakey-Milner wrote: > > > > > > On Sat 2001-01-20 (16:39), Sergey Babkin wrote: > > > > All, > > > > > > > > I've committed these changes for cron to support DST change > > > > to -current (see PR bin/24494 for description of my tests). > > > > Everyone is welcome to test them out. > > > > Please let me know if you encounter any problems caused by them > > > > (and better do that before these changes would be MFCed to -stable > > > > in a few weeks). > > > > > > I do believe this is premature. There really should at least be an > > > option for the old behaviour, and there is a good argument for making > > > the new behaviour optional dependent on a variable with the old > > > > Let me ask a simple question: Why ? What are the benefits of > > preserving the old behavior ? As far as I've watched this thread > > nobody had explained it. So could you please elaborate ? > > You have not been paying attention. Please go back and /read/ > the archives on this topic which has been thrashed out in great > detail here. We did not reach agreement about the desired > behaviour because the nature of this issue is that different > people desire different behaviour. Actually, yes, I was paying not quite a close attention. But I went to the -hackers archive and re-read all the thread now. The end result is that I've seen exactly zero technical arguments on why changing the current behavior is bad. As well as zero real-life examples and only one imaginary example. That was one example of a job running at 2:30 and another job which depends on it running at 3:45. However with the current behavior if 2:30 disappears, the first job won't run anyway and thus the second job would not be able to work correctly as well. So this does not look like a quite compelling example. > What was agreed by those who contributed was clearly that the > old behaviour was to be preserved by default and that new > behaviour was to be enabled by a command-line option, which > could be set in rc.conf. You have shown no reason not to go > with the solution that was agreed, so please don't just jump in I did and if you re-read the thread you could see my e-mail on this. In short it is that a) this is what people normally expect (I agree, an arguable statement) b) practically all the commercial Unix implemenattions do support the DST changes in cron I'll comment more in answers to other e-mails. -SB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A6B68E9.278A6BBB>