On Wed, Nov 30, 2022 at 12:09:56AM +0100, Steinar H. Gunderson wrote:
> Most of this logic is inherited from mlocate's updatedb, though not all.
> It may be fixable or it may not; I'd really need to check. But it really
> sounds like one should be able to stat() something without bad things
>
On Tue, Nov 29, 2022 at 03:04:01PM -0800, Ross Vandegrift wrote:
> Interesting - stat -f does the same, and it always returns nfs. Here's
> a lame idea: /proc/mounts knows it's actually autofs...
Most of this logic is inherited from mlocate's updatedb, though not all.
It may be fixable or it may
On Tue, Nov 29, 2022 at 09:27:26PM +0100, Steinar H. Gunderson wrote:
> On Tue, Nov 29, 2022 at 11:31:39AM -0800, Ross Vandegrift wrote:
> >> Subject: Bug#1025099: plocate: autofs pruning doesn't seem to work
> > That subject wasn't too clear- updatedb.plocate does not in
On Tue, Nov 29, 2022 at 11:31:39AM -0800, Ross Vandegrift wrote:
>> Subject: Bug#1025099: plocate: autofs pruning doesn't seem to work
> That subject wasn't too clear- updatedb.plocate does not index the
> remote filesystem, it just triggeres the automount unnecessarily.
I don't
Control: retitle -1 autofs mount triggered in spite of pruning
On Tue, Nov 29, 2022 at 11:24:03AM -0800, Ross Vandegrift wrote:
> Subject: Bug#1025099: plocate: autofs pruning doesn't seem to work
That subject wasn't too clear- updatedb.plocate does not index the
remote filesystem, it j
Package: plocate
Version: 1.1.17-2
Severity: normal
X-Debbugs-Cc: rvandegr...@debian.org
Hello,
I noticed that an autofs mount is being triggered by updatedb.plocate:
systemd[1]: mnt-storage.automount: Got automount request for /mnt/storage,
triggered by 63669 (updatedb.plocat)
It looks like
6 matches
Mail list logo
