The following reply was made to PR bin/37376; it has been noted by GNATS.

From: eric@cirr.com (Eric Schnoebelen)
To: gnats-bugs@NetBSD.org
Cc: netbsd-bugs@NetBSD.org
Subject: Re: bin/37376: /etc/{daily,weekly,montly} shouldn't try to "dot in" {}.local 
Date: Tue, 13 Nov 2007 11:24:05 -0600

 "Jeremy C. Reed" writes:
 - The following reply was made to PR bin/37376; it has been noted by GNATS.
 - 
 - From: "Jeremy C. Reed" <reed@reedmedia.net>
 - To: gnats-bugs@NetBSD.org
 - Cc: 
 - Subject: Re: bin/37376: /etc/{daily,weekly,montly} shouldn't try to "dot in
 - "
 -  {}.local
 - Date: Tue, 13 Nov 2007 09:44:02 -0600 (CST)
 - 
 -  On Tue, 13 Nov 2007, eschnoebelen@efjohnson.com wrote:
 -  
 -  >  	also present on 4.0_BETA?/RC?, 3.X.
 -  
 -  I do not have this problem on multiple 3.1 systems where I use a 
 -  /etc/daily.local file. My /etc/daily.local files are not executable.
 -  
 -  I also can't reproduce this problem on my 4.99.27 system.
 
 I've been seeing it regularly with my weekly script.
 
 What I've really been seeing is a lack of output from my .local
 scripts (notably weekly.local), and the appearance of it not
 running.
 
 However, after investigation, the real issue may be that ${TMP}
 is a relative path in /etc/weekly, and my weekly.local changes
 directories (it's primary task is to update the pkgsrc tree and
 rebuild.)
 
 Perhaps the the {daily,weekly,monthly,security} scripts should
 use absolute path names for their temporary files?
 
 --
 Eric Schnoebelen		eric@cirr.com		http://www.cirr.com
 	Artificial Intelligence is neither -- it consists of quite
 	natural people programming computers to do dumb things.
 					- Bob Spitzer