From: Greg Olszewski <noop@nwonknu.org>
To: Peter <heisspf@skyinet.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: No Locate for User
Date: Tue, 26 Apr 2005 00:44:42 -0700 [thread overview]
Message-ID: <426DF16A.4030505@nwonknu.org> (raw)
In-Reply-To: <200504260729.j3Q7T28e001337@skyinet.net>
Peter wrote:
> Thanks Greg but nothing doing.
>
> ll /usr/bin/slocate
> -rwxr-sr-x 1 root slocate 26652 2004-05-30 11:52 /usr/bin/slocate
>
/usr is mounted *without* nosuid, no?
"cat /proc/mounts | grep '/usr'"
and
"cat /proc/mounts | grep ' / '"
> @~:$ locate fips
> warning: locate: could not open database: /var/lib/slocate/slocate.db:
> Permission denied
>
grr. Frustrating.
what does 'ls -ld /var/lib/slocate' say?
does 'chmod 750 /var/lib/slocate/' or 'chown root:slocate
/var/lib/slocate' help (if it isn't rwxr-x--- root slocate already)?
If not, what does 'slocate -V' say?
How about
'ls -ld /var'
'ls -ld /var/lib'
also?
Thanks a bunch. Apologies if you've posted this output before and I
missed it.
> noop@nwonknu.org said:
>
>>'chroot /mnt/rh9root locate fips' ought to work fine.
>
>
> Yes as su and that is exactly what I want to avoid to go su for locate since I
> use this command relatively frequently.
>
totally understood. I was just trying to point out that it is unlikely
for the redhat slocate binary to work with the slackware data files.
hope this helps,
-greg
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
next prev parent reply other threads:[~2005-04-26 7:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 4:27 No Locate for User Peter H.
2005-04-25 5:06 ` Ray Olszewski
2005-04-25 8:11 ` Peter
2005-04-25 16:40 ` Ray Olszewski
2005-04-26 4:18 ` Peter
2005-04-26 5:42 ` Greg Olszewski
2005-04-26 7:29 ` Peter
2005-04-26 7:44 ` Greg Olszewski [this message]
2005-04-26 8:27 ` Peter
2005-04-26 8:41 ` Greg Olszewski
2005-04-26 9:11 ` Peter
2005-04-26 11:53 ` chuck
2005-04-26 11:37 ` chuck
2005-04-25 8:33 ` Peter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=426DF16A.4030505@nwonknu.org \
--to=noop@nwonknu.org \
--cc=heisspf@skyinet.net \
--cc=linux-newbie@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox