From: chuck <chuck@gelm.net>
To: Peter <heisspf@skyinet.net>, Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: No Locate for User
Date: Tue, 26 Apr 2005 07:53:04 -0400 [thread overview]
Message-ID: <426E2BA0.80307@gelm.net> (raw)
In-Reply-To: <200504260418.j3Q4I8d2000571@skyinet.net>
Peter wrote:
>Sorry for not expressing myself clearly!
>
>ray@comarre.com said:
>
>
>> From what you just wrote this time ("I tried various permission for
>>slocate"), I *still* cannot tell if you tried what I actually suggested --
>>using chmod to set the database file (slocate.db) to mode 644.
>>
>>
>
>Yes I did chmod 644 /var/lib/slocate/slocate.db and it changed nothing.
>
>ray@comarre.com said:
>
>
>>Since you say you tried things with "slocate" rather than "slocate.db", I am
>>uncertain as to which of the two you were modifying.
>>
>>
>
>I did all the changes on slocate.db. I even made myself the owner. Even then I
>get Permission denied.
>
>Updatedb changes permissions of slocate.db back to -rw-r----- 1 root slocate.
>
>ray@comarre.com said:
>
>
>>If it does, then round up the usual suspects:
>> ls -l /var/lib/slocate/slocate.db
>> ls -l /usr/bin/locate (or wherever Slackware puts it)
>> ldd /usr/bin/locate
>>
>>
>
>ls -l /var/lib/slocate/slocate.db
>-rw-r--r-- 1 root slocate 6640136 2005-04-25 18:08 /var/lib/slocate/slocate.db
>
>ls -l /usr/bin/locate
>lrwxrwxrwx 1 root root 7 2005-03-08 17:45 /usr/bin/locate -> slocate
>
>ldd /usr/bin/slocate
>libc.so.6 => /lib/libc.so.6 (0x4001e000)
>/lib/ld-linux.so.2 (0x80000000)
>
>Fedora:
>ls -l /var/lib/slocate/slocate.db
>-rw-r----- 1 root slocate 2874826 2005-04-20 15:07
>/mnt/rh9root/var/lib/slocate/slocate.db
>
>ls -l /usr/bin/locate
>-rwxr-sr-x 1 root slocate 26460 2004-10-20 /usr/bin/locate -> slocate
>
>ldd /usr/bin/slocate
> libc.so.6 => /lib/tls/libc.so.6 (0x004c7000)
> /lib/ld-linux.so.2 (0x004ae000)
>
>
.../tls/... ?
My Slackware 10.1: ldd /usr/bin/slocate:
libc.so.6 => /lib/libc.so.6 (0x40009000)
/lib/ld-linux.so.2 (0x80000000)
HTH, Chuck
-
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 11:53 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
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 [this message]
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=426E2BA0.80307@gelm.net \
--to=chuck@gelm.net \
--cc=heisspf@skyinet.net \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/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