Bug 3886 - slocate & updatedb return code and exit status
slocate & updatedb return code and exit status
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: findutils (Show other bugs)
6.0
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: David Lawrence
pushf@club-internet.fr
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 1999-07-03 10:45 EDT by pushf
Modified: 2008-05-01 11:37 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 1999-08-19 18:15:40 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)

  None (edit)
Description pushf 1999-07-03 10:45:37 EDT
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 11:00:59 EDT
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 18:15:59 EDT
closed ; lack of input

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