From owner-freebsd-stable Mon Jun 19 8:17:36 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 EF53837B617 for ; Mon, 19 Jun 2000 08:17:32 -0700 (PDT) (envelope-from str@giganda.komkon.org) Received: (from str@localhost) by giganda.komkon.org (8.9.3/8.9.3) id LAA21698 for stable@freebsd.org; Mon, 19 Jun 2000 11:17:32 -0400 (EDT) Date: Mon, 19 Jun 2000 11:17:32 -0400 (EDT) From: Igor Roshchin Message-Id: <200006191517.LAA21698@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 > From gram@cequrux.com Mon Jun 19 10:59:05 2000 > Date: Mon, 19 Jun 2000 17:00:15 +0200 > From: Graham Wheeler > To: Igor Roshchin > CC: stable@freebsd.org > Subject: Re: Strange behavior of cron > > Igor Roshchin wrote: > > > > 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. > > I'm not sure about the cron problems, but syslog will sometimes stop > logging if there are DNS problems. That may explain the last problem. > > -- Just to correct myself: All messages from cron stopped. Syslog was logging all message without any problem. Igor --LAA21637.961427773/giganda.komkon.org-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message