From owner-freebsd-current@FreeBSD.ORG  Thu Jan 29 08:45:37 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 3732216A4CE
	for <freebsd-current@freebsd.org>;
	Thu, 29 Jan 2004 08:45:37 -0800 (PST)
Received: from orwell.lost-angel.com (134.153.252.64.snet.net
	[64.252.153.134])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CD6C043D46
	for <freebsd-current@freebsd.org>;
	Thu, 29 Jan 2004 08:45:35 -0800 (PST)
	(envelope-from sammy@lost-angel.com)
Received: from [192.168.1.6] (tereza.euplastic.com [192.168.1.6])
	(authenticated bits=0)i0TGi8Cs054432
	(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NO)
	for <freebsd-current@freebsd.org>;
	Thu, 29 Jan 2004 11:44:08 -0500 (EST)
	(envelope-from sammy@lost-angel.com)
Mime-Version: 1.0 (Apple Message framework v612)
Content-Transfer-Encoding: 7bit
Message-Id: <8DE990B0-527A-11D8-B3B3-000393CE1FDA@lost-angel.com>
Content-Type: text/plain; charset=US-ASCII; format=flowed
To: freebsd-current@freebsd.org
From: sammy!!! <sammy@lost-angel.com>
Date: Thu, 29 Jan 2004 11:45:32 -0500
X-Mailer: Apple Mail (2.612)
Subject: Periodic not running in FreeBSD 5.2
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Jan 2004 16:45:37 -0000

I've noticed my periodic scripts have not been running for about a week 
now.  Is there something that might have been broken with them when 
upgrading to 5.2 from 5.1?