On Wed, Jan 11, 2012 at 4:08 PM, L. V. Lammert <l...@omnitec.net> wrote: > On Wed, 11 Jan 2012, Philip Guenther wrote: > >> > Agreed, .. but if locate.update does NOT run as root, that would seem to >> > indicate some problem other than permissions. >> >> If you're saying what I think you're saying, then I disagree and think >> your logic is backwards. >> What user do you think locate.updatedb is run as? >> > If it does not run as root, then it isn't a permission issue as running as > root provides all required permissions, eh?
I'm sorry, but I don't understand that sentence. It appears to conflate running as root with not running as root, or I'm miscounting the 'not's. So let me try again: what user do you think locate.updatedb is run as? > I have never seen locate.updatedb fail when run as root (3.0 to 5.0, > actually), .. but, then, it isn't exactly 'failing', it just isn't > indexing anything except "/home". I don't understand this sentence either. If the word "fail" is ambiguous or unclear, then use a different word instead! I cannot tell from what you wrote what behavior you saw when you manually ran locate.updatedb as root on (say) 3.0. Philip Guenther
