From owner-freebsd-stable Wed Jul 22 13:14:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA15760 for freebsd-stable-outgoing; Wed, 22 Jul 1998 13:14:01 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from camel14.mindspring.com (camel14.mindspring.com [207.69.200.64]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA15720 for ; Wed, 22 Jul 1998 13:13:48 -0700 (PDT) (envelope-from eternal@foci.net) Received: from et (user-38lc37k.dialup.mindspring.com [209.86.12.244]) by camel14.mindspring.com (8.8.5/8.8.5) with SMTP id QAA10669 for ; Wed, 22 Jul 1998 16:13:21 -0400 (EDT) Message-ID: <000701bdb5ac$cf48d0a0$01646464@et.foci.net> From: "Eternal" To: Subject: Cron broken in 2.2.7 ? Date: Wed, 22 Jul 1998 16:10:43 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.1 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG When anyone uses crontab to write a new cron it appears to work fine. Crontab -e has the same file that was wrote, but crontab -l shows this, or something similiar to this (different filename etc.): # DO NOT EDIT THIS FILE - edit the master and reinstall. # (/tmp/crontab.MAhpDD5567 installed on Wed Jul 22 15:47:59 1998) # (Cron version -- $Id: crontab.c,v 1.6.2.3 1998/03/09 11:42:00 jkh Exp $) Any ideas ? - Jeremy Blawn To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message