Bug 13611 – slocate -u prints "no database" message

Bug 13611 - slocate -u prints "no database" message

Summary:	slocate -u prints "no database" message

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	slocate (Show other bugs)
Sub Component:
Version:	7.0
Hardware:	i386 Linux

Priority	medium Severity low
Target Milestone:	---
Target Release:	---
Assigned To:	Bill Nottingham
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2000-07-08 17:27 EDT by Jay Freeman
Modified:	2014-03-16 22:14 EDT (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-08-01 11:10:32 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Jay Freeman 2000-07-08 17:27:37 EDT

slocate prints a message to run /etc/cron.daily/slocate.cron when there 
isn't an existing slocate database.  slocate.cron (which runs slocate -u) 
does as well :).  After that point (as there is now a database), 
everything works fine, but that slocate warning message is going to end up 
getting sent to root in an e-mail from crond, telling him to run 
slocate.cron...

Comment 1 Matt Domsch 2000-07-21 14:52:01 EDT

Winston Beta 4 does the same thing, and root is sent an email immediately upon 
the first system boot.

Comment 2 Michael Redinger 2000-08-01 11:10:30 EDT

Hm, didn't see this in Pinstripe anymore (I've to confess that I didn't
specially look for it, but more than 1 day is over and I did at least not get a
mail). Can anybody confirm this? Think we can close this.

Comment 3 Bill Nottingham 2000-08-01 11:11:43 EDT

Yes, this got fixed.

Note You need to log in before you can comment on or make changes to this bug.