Bug 3886

Summary:	slocate & updatedb return code and exit status
Product:	[Retired] Red Hat Linux	Reporter:	pushf
Component:	findutils	Assignee:	David Lawrence <dkl>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.0	CC:	pushf
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
URL:	pushf@club-internet.fr
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	1999-08-19 22:15:40 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description pushf 1999-07-03 14:45:37 UTC

I am runnig under RH 6.0 and when root starts updatedb, the
exit status is always 1. Normally, it must be 0.
ex :
(root@foo)# updatedb

(root@foo)# echo $?
1
(root@foo)#

When I try with parameters like -u and -l 1 or -l 0, the
exit status is 1 yet.
When I try with slocate, the exit status is 1...

I just want to know if this problem comes from my system, or
the whole Redhat 6 has the same matter.

Thank.

Pierre-Frangois LAURAND
France

Comment 1 Bill Nottingham 1999-07-06 15:00:59 UTC

is it actually creating the database?
The exit code of 1 for slocate seems only to be used for
error conditions...

Comment 2 Bill Nottingham 1999-08-19 22:15:59 UTC

closed ; lack of input