misc/160225: /etc/periodic/weekly/310.locate doesn't see /etc/locate.rc.

Hiroaki Abe hiroaki0404 at gmail.com
Sat Aug 27 00:40:02 UTC 2011


>Number:         160225
>Category:       misc
>Synopsis:       /etc/periodic/weekly/310.locate doesn't see /etc/locate.rc.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Aug 27 00:40:02 UTC 2011
>Closed-Date:
>Last-Modified:
>Originator:     Hiroaki Abe
>Release:        FreeBSD 8.1-RELEASE i386
>Organization:
>Environment:
System: FreeBSD ns.group.jp 8.1-RELEASE FreeBSD 8.1-RELEASE #0: Mon Jul 19 02:55:53 UTC 2010 root at almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC i386


$FreeBSD: src/etc/periodic/weekly/310.locate,v 1.7.10.1.4.1 2010/06/14 02:09:06 kensmith Exp $
>Description:
	The location of locate database can change in /etc/locate.rc.
	But the script of rebuilding locate database, 310.locate,
	doesn't see the definition in /etc/locate.rc. The location of
	locate database is hard coded in the script as "locdb=/var/db/locate.database".
	So, when changed the location of locate database in /etc/locate.rc,
	it failed to update the locate database.
>How-To-Repeat:
	Change the "FCODES" in /etc/locate.rc from the default settings.
	Then run the /etc/periodic/weekly/310.locate.
>Fix:



>Release-Note:
>Audit-Trail:
>Unformatted:


More information about the freebsd-bugs mailing list