From owner-freebsd-stable Mon Jun 19 7:47: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 8230B37B68F for ; Mon, 19 Jun 2000 07:47:50 -0700 (PDT) (envelope-from str@giganda.komkon.org) Received: (from str@localhost) by giganda.komkon.org (8.9.3/8.9.3) id KAA20823; Mon, 19 Jun 2000 10:47:48 -0400 (EDT) Date: Mon, 19 Jun 2000 10:47:48 -0400 (EDT) From: Igor Roshchin Message-Id: <200006191447.KAA20823@giganda.komkon.org> To: stable@freebsd.org Subject: Strange behavior of cron Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hello! I am puzzled: On a 3.4-STABLE (~Jan.2000) FreeBSD box that has been working just fine, in one night there were about 10 messages from cron. One was generated while running periodic/daily, the rest, - while running adjkentz -a. Then all messages just stopped. The load on this host is usually rather low, and practically never exceeds 1, if that matters. An example of the messages is below. Any idea is appreciated. Igor Message 249: From daemon Mon Jun 19 00:31:01 2000 Date: Mon, 19 Jun 2000 00:31:00 -0400 (EDT) From: root (Cron Daemon) To: root Subject: Cron adjkerntz -a Abort trap & 251 Message 251: From daemon Mon Jun 19 00:33:08 2000 Date: Mon, 19 Jun 2000 00:33:08 -0400 (EDT) From: root (Cron Daemon) To: root Subject: Cron periodic daily 2>&1 | sendmail root Segmentation fault & Message 252: From daemon Mon Jun 19 01:01:00 2000 Date: Mon, 19 Jun 2000 01:01:00 -0400 (EDT) From: root (Cron Daemon) To: root Subject: Cron adjkerntz -a Abort trap To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message