From owner-freebsd-bugs Wed Nov 22 7:51:43 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from spammie.svbug.com (mg134-015.ricochet.net [204.179.134.15]) by hub.freebsd.org (Postfix) with ESMTP id 29BA537B479 for ; Wed, 22 Nov 2000 07:51:38 -0800 (PST) Received: from spammie.svbug.com (localhost.mozie.org [127.0.0.1]) by spammie.svbug.com (8.9.3/8.9.3) with ESMTP id HAA00702; Wed, 22 Nov 2000 07:50:28 -0800 (PST) (envelope-from jessem@spammie.svbug.com) Message-Id: <200011221550.HAA00702@spammie.svbug.com> Date: Wed, 22 Nov 2000 07:50:27 -0800 (PST) From: opentrax@email.com Reply-To: opentrax@email.com Subject: Re: bin/22954: cron isn't daylight savings-aware To: roam@orbitel.bg Cc: freebsd-bugs@FreeBSD.ORG In-Reply-To: <20001122171124.B1641@ringworld.oblivion.bg> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 22 Nov, Peter Pentchev wrote: > Jessem, > > Your reply seems to indicate that you've taken my explanation to mean > that cvsweb is something you could use to make changes to your systems. > In this case, it's way simpler - cvsweb is something the FreeBSD Project > is using so you can see what changes have been made to FreeBSD. > > Just go to http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/crontab/ > and you'll see the history of changes to crontab; in particular, > you'll see a commit made by Doug Barton on Sun Nov 19 18:16:46 UTC, > and a link named 'Diff to previous 1.22', pointing to: > > http://www.freebsd.org/cgi/cvsweb.cgi/src/etc/crontab.diff?r1=1.22&r2=1.23 > > Do take the ten to fifteen seconds needed to check out those links; > you might find them useful in the future. > I have no doubt that these links are extremely useful. However, using any mechanism that encompasses CVS encourages use within our organisation. Something we will not do. I can also see that, at the current time, FreeBSD has no other means by which to pass this information to our organization. Further, I see that any such improvement in the system would require time, something all of us are short on. Lastly, I don't see that the aforementined 'crontab' fix would benefit us any more than fixing the cronjob(s) run twice once a year. So let me state now, on this subject, that the effort and time we've spent (me included) on this subject has been a waste. I don't mean to imply that anyone has not been helpful or even suggestive. I am just stating that the current system has a frailty(sp?) which we cannot overcome. Such things are common in the real world -- especially in the commercial world; we make comprimises. Our policies and the current system (in place) for FreeBSD collide (on this one topic). Lastly, if it's okay with you, let's just drop this subject (for now), :-) best regards, Jessem. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message