From owner-freebsd-stable Tue Jun 20 8: 1:54 2000 Delivered-To: freebsd-stable@freebsd.org Received: from giganda.komkon.org (giganda.komkon.org [209.125.17.66]) by hub.freebsd.org (Postfix) with ESMTP id EE9CB37BB77 for ; Tue, 20 Jun 2000 08:01:50 -0700 (PDT) (envelope-from str@giganda.komkon.org) Received: (from str@localhost) by giganda.komkon.org (8.9.3/8.9.3) id LAA53867 for stable@freebsd.org; Tue, 20 Jun 2000 11:01:49 -0400 (EDT) Date: Tue, 20 Jun 2000 11:01:49 -0400 (EDT) From: Igor Roshchin Message-Id: <200006201501.LAA53867@giganda.komkon.org> To: stable@freebsd.org Subject: Re: Strange behavior of cron Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! Sorry for messing up some people's mailboxes. When I sent the original message, I just "cut-and-pasted" messages without shifting "From" in the first position. (I used regular mail in FreeBSD). As a result some people's mail agents could've considered these three included messages as separate messages. (Note, that I replaced the name of my host as "host". Normally it should be the host name of yours) Anyway, last night I observed the same type of messages again. (from cron - see an example of one message below ) It's rather strange that cron has these problems only in night. (second night in a row). I wonder if this could be a result of some attack against this host that prevents cron working properly. Igor ================== 8< ======================================== > > From daemon Tue Jun 20 05:31:01 2000 > Received: (from root@localhost) > by myhost.mydomain (8.9.3/8.9.3) id FAA93592; > Tue, 20 Jun 2000 05:31:01 -0400 (EDT) > Date: Tue, 20 Jun 2000 05:31:01 -0400 (EDT) > Message-Id: <200006200931.FAA93592@myhost.mydomain> > From: root (Cron Daemon) > To: root > Subject: Cron adjkerntz -a > X-Cron-Env: > X-Cron-Env: > X-Cron-Env: > X-Cron-Env: > X-Cron-Env: > Status: R > > Abort trap > > =========================== >8 ============================ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message