From owner-freebsd-stable Mon Jun 19 11:41:42 2000 Delivered-To: freebsd-stable@freebsd.org Received: from cfdnet.me.tuns.ca (CFDnet.me.TUNS.Ca [134.190.50.164]) by hub.freebsd.org (Postfix) with ESMTP id EDBDC37B840 for ; Mon, 19 Jun 2000 11:41:27 -0700 (PDT) (envelope-from freebsd@cfdnet.me.tuns.ca) Received: from localhost (freebsd@localhost) by cfdnet.me.tuns.ca (8.9.3/8.9.3) with ESMTP id PAA40450; Mon, 19 Jun 2000 15:38:15 -0300 (ADT) (envelope-from freebsd@cfdnet.me.tuns.ca) Date: Mon, 19 Jun 2000 15:38:15 -0300 (ADT) From: Theo Bell To: Jim Weeks Cc: freebsd-stable@FreeBSD.ORG Subject: Re: Strange behavior of cron In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello All.. Its seems that the original poster must have sent the cron job messages to the list. I'm pretty sure everyone received them and that's why we got them at our mailing list addresses and not where our root mail normally gets sent. Theo On Mon, 19 Jun 2000, Jim Weeks wrote: > > On Mon, 19 Jun 2000, Bob K wrote: > > > Just to add to the chorus of "Me Too!"'s: Got these this morning with a > > late February 3.4-STABLE. If it helps, the machine is set to EST as > > opposed to UTC, and has ye olde Neptune chipset. > > Same here as to EST. I also sync periodically with ntpdate run from > cron. Dual PII Intel 440BX chipset. > > I could shoot myself for deleting the original messages before examining > the headers more closely. > > To add to the confusion consider this. I received them at this address > which I reserver for newsgroups, and an occasional solicitation from > Russian girls ;-) My normal system messages came to another address as > always. > > Jim Weeks > -------- A mind is a terrible thing to lose! How I miss mine.. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message