https://bugzilla.novell.com/show_bug.cgi?id=847801
https://bugzilla.novell.com/show_bug.cgi?id=847801#c12
Karl Eichwalder changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P3 - Medium
Status|RESOLVED |REOPENED
Resolution|FIXED |
AssignedTo|tchvatal@suse.com |ke@suse.com
Summary|mlocate only useable for |RN: mlocate only useable
|users in "locate" group |for users in "locate" group
--- Comment #12 from Karl Eichwalder 2013-11-13 09:16:05 CET ---
ok, now it works :)
I think to attack the delay issue, I should a statement to the release notes.
Here is what you said previously:
"BTW: in https://bugzilla.novell.com/show_bug.cgi?id=847826 I also stated that
the new database for Mlocate was created correctly as soon as the daily cron
job was run - which can mean a delay of up to 24 hours. For somebody who wants
to use locate for post processing (e.g. rpmnew or rpmsav) files after the
upgrade this is inconvenient."
I think it's sufficient if I'd recommend to cron.daily and ask to wait ~15min.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.