<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <style type="text/css" style="display:none;"></style> </head> <body dir="ltr"> <div id="divtagdefaultwrapper" style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;" dir="ltr"> I don't know if anyone has said it already but I want to applaud you for asking rather than just doing. </div> <hr style="display:inline-block;width:98%" tabindex="-1"> <div id="divRplyFwdMsg" dir="ltr">From: ubuntu-server <ubuntu-server-bounces@lists.ubuntu.com> on behalf of Steve Langasek <steve.langasek@ubuntu.com> Sent: Thursday, May 23, 2019 12:48:35 PM To: jim Cc: ubuntu-server@lists.ubuntu.com; ubuntu-devel@lists.ubuntu.com Subject: [EXTERNAL] Re: mlocate - what is it good for? <div> </div> </div> <div class="BodyFragment"> <div class="PlainText">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 individual users? Currently, this is seeded as part of ubuntu-standard, which is common to all Ubuntu flavors. If the discussion led to a determination that this still made sense to include by default on desktops but not servers, or vice versa, we could seed this as part of one Ubuntu flavor or the other. My own sense is that this is not a server vs desktop thing; there are users of locate, to be sure, but I believe they are a very small minority on both desktop and server (small on desktop because the user will generally use the gui instead; small on server because most server use is not interactive at the shell). I don't think the benefit of having locate available by default justifies the daily disk thrashing / energy usage on every Ubuntu machine everywhere. I think it's not onerous for those who want to use locate to manually install it the first time they need it on a machine. But this thread is here to be a sanity check on that opinion, to understand if the locate db being available by default either affects so many users, or has so great an impact on some use cases, that we should consider leaving it enabled by default despite the daily disk usage for everyone not using it. Harriscomputer <TABLE id=c1-id-8 style="BORDER-LEFT-WIDTH: 0px; BORDER-RIGHT-WIDTH: 0px; BORDER-BOTTOM-WIDTH: 0px; PADDING-BOTTOM: 0px; PADDING-TOP: 0px; PADDING-LEFT: 0px; MARGIN: 0px; PADDING-RIGHT: 0px; BORDER-TOP-WIDTH: 0px"> <COLGROUP id=c1-id-9> <COL id=c1-id-10></COL></COLGROUP> <TBODY id=c1-id-11> <TR id=c1-id-12> <TD id=c1-id-13> <TABLE id=c1-id-14 style="HEIGHT: 0px; WIDTH: 100%" cellSpacing=0 cellPadding=0 border=0> <COLGROUP id=c1-id-15> <COL id=c1-id-16> <COL id=c1-id-17> <COL id=c1-id-18></COL></COL></COL></COLGROUP> <TBODY id=c1-id-19> <TR id=c1-id-27> <TD id=c1-id-28 style="WIDTH: 33%"> Leroy Tennison Network Information/Cyber Security Specialist E: leroy@datavoiceint.com</TD> <TD id=c1-id-40 style="WIDTH: 33%"> <IMG border=0 src="cid:Data-Voice-International-LOGO_aa3d1c6e-5cfb-451f-ba2c-af8059e69609.PNG"></TD> <TD id=c1-id-45 style="WIDTH: 33%"> 2220 Bush Dr McKinney, Texas 75070 <A href="http://www..com">www.datavoiceint.com</A> </TD></TR></TBODY></TABLE> <TABLE id=c1-id-57 style="WIDTH: 100%" cellSpacing=2 border=0> <COLGROUP id=c1-id-58> <COL id=c1-id-59> <COL id=c1-id-60> <COL id=c1-id-61></COL></COL></COL></COLGROUP> <TBODY id=c1-id-62> <TR id=c1-id-63> <TD id=c1-id-64 colSpan=3> This message has been sent on behalf of a company that is part of the Harris Operating Group of Constellation Software Inc. These companies are listed <A href="http://subscribe.harriscomputer.com/">here</A>. If you prefer not to be contacted by Harris Operating Group <A href="http://subscribe.harriscomputer.com/">please notify us</A>. This message is intended exclusively for the individual or entity to which it is addressed. This communication may contain information that is proprietary, privileged or confidential or otherwise legally exempt from disclosure. If you are not the named addressee, you are not authorized to read, print, retain, copy or disseminate this message or any part of it. If you have received this message in error, please notify the sender immediately by e-mail and delete all copies of the message.</TD></TR></TBODY></TABLE></TD></TR></TBODY></TABLE> > On 5/22/19 3:47 PM, Julian Andres Klode wrote: > > On Wed, May 22, 2019 at 01:19:48PM -0600, Neal McBurnett wrote: > > > I use mlocate multiple times a day. > > > Find is way too slow and inconvenient for finding files in a big > > > set of filesystems, compared to properly configuring mlocate. > > Specifically, the filesystem must be huge or on a slow medium. It might make > > sense to move it out of standard and elsewhere, as I don't think it's > > necessarily needed everywhere, such as laptops. > > > > Consider my laptop, fairly standard, 512 GB NVME SSD, about 250G allocated, > > 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 > > screwed up a bit). > > > > 19s to find something is perfectly workable, also you don't usually > > find from /, but you have an idea where things are, so it will be much > > faster. > > > > 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 keep mlocate in always-on tasks, like servers, but get > > rid of it from desktop scenarios. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer <a href="https://www.debian.org/"> https://www.debian.org/</a> slangasek@ubuntu.com vorlon@debian.org </div> </div> </body> </html>