From: Greg Olszewski <noop@nwonknu.org>
To: Peter <heisspf@skyinet.net>
Cc: linux-newbie@vger.kernel.org
Subject: Re: No Locate for User
Date: Mon, 25 Apr 2005 22:42:41 -0700 [thread overview]
Message-ID: <426DD4D1.3000505@nwonknu.org> (raw)
In-Reply-To: <200504260418.j3Q4I8d2000571@skyinet.net>
I suspect you'll simply need to do:
chmod 2755 $(which slocate)
chown root:slocate $(which slocate)
(which is probably the same as)
chmod 2755 /usr/bin/slocate
chown root:slocate /usr/bin/slocate
slocate considers the db file to be sensitive (as well it should). the
slocate binary needs to run as the slocate group to use it.
> @~:$ /mnt/rh9root/usr/bin/locate fips
> warning: locate: could not open database: /var/lib/slocate/slocate.db:
> Permission denied
> warning: You need to run the 'updatedb' command (as root) to create the
> database.
>
Um. This could be due to many things. Perhaps the partition is mounted
nosuid, and slocate isn't running with the right permissions. Perhaps
you've got a different version of slocate on fedora than slackware.
Running a binary from one version against data from another shouldn't be
expected to work. 'chroot /mnt/rh9root locate fips' ought to work fine.
have fun,
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 5:42 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 [this message]
2005-04-26 7:29 ` Peter
2005-04-26 7:44 ` Greg Olszewski
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=426DD4D1.3000505@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