On Thu, 23 May 2019 at 09:07, Brian Murray wrote:
> The Ubuntu Foundations team was recently looking at an issue with
> mlocate[1] and the effect it has on all users of Ubuntu. While that
> specific issue is fixable there are also issues[2,3] with keeping
> PRUNEFS and PRUNEPATHS current in
On Thu, May 23, 2019 at 08:25:20PM +0200, Sebastien Bacher wrote:
> Le 22/05/2019 à 21:47, Julian Andres Klode a écrit :
> > containing about 1435134 files. mlocate foo takes 1s, find / -mount
> > -name '*foo*' takes about 7-9 secs, or 19 seconds with all mount points
> > (but there is a davfs
I don't know if anyone has said it already but I want to applaud you for asking
rather than just doing.
From: ubuntu-server on behalf of Steve
Langasek
Sent: Thursday, May 23, 2019 12:48:35 PM
To: jim
Cc: ubuntu-ser...@lists.ubuntu.com;
Le 22/05/2019 à 21:47, Julian Andres Klode a écrit :
> containing about 1435134 files. mlocate foo takes 1s, find / -mount
> -name '*foo*' takes about 7-9 secs, or 19 seconds with all mount points
> (but there is a davfs mount of an internet server, so things might be
Well here on a few years
Hi Jim,
On Wed, May 22, 2019 at 03:51:14PM -0400, jim wrote:
> Seems to me for an individual user such
> as I (my laptop runs Ubuntu 18.04), locate
> and (the cumbersome) find are sufficient.
> To what extent does decision-making balance
> net ops and large system administrators as
> opposed to
On Wed, 22 May 2019, Seth Arnold wrote:
> Anyway, I believe locate can have great value to all our users,
> experienced or brand new, huge systems or small systems. I'd like
> us to keep it in default installs.
>
IMO, find has its place and so does mlocate. I still use locate myself fairly
On Wed, May 22, 2019 at 11:25:45PM -0700, Bryan Quigley wrote:
> The mentioned Debian bug #880507 is one of the advantages of moving from
> cron to systemd units -see proposed unit file in [1]. The timers in
> systemd are really perfect for this...
>
> I use locate all the time. I really like
On Wed, May 22, 2019 at 09:47:22PM +0200, Julian Andres Klode wrote:
> I think mlocate only really makes sense on data storage servers with
> huge disks, or on machines with HDDs. I therefore do not think the
> overhead of building the index is warranted for most users. It might
> make sense to
The mentioned Debian bug #880507 is one of the advantages of moving from
cron to systemd units -see proposed unit file in [1]. The timers in
systemd are really perfect for this...
I use locate all the time. I really like how much simpler it is then
find. I don't have to think to usually get
