SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Hi: I've just reinstalled Slackware 12.1 and have just noticed slocate is running. I used to disable it and run updatedb whenever I consider it convimient. But I think to remember there was a cron file in charge of running it. Now my whole disk is being searched and I do not know how to stop it (I don't won't to use kill). Could you tell what is the script run at boot time responsible for this behavior (in case it is a script).
EDIT: but what may make slocate to spontaneously run? If it were updatedb I would understand it.
For what it's worth, slocate was replaced by mlocate in the -current tree, and it's much less resource-intensive than slocate. You might consider building it yourself on that machine and replacing slocate. Note that you should *not* install the package from the -current tree; you need to build it on a 14.2 system. Here's the build script and associated files: https://mirrors.slackware.com/slackw...rce/a/mlocate/
EDIT: to answer your own 'EDIT' part, I don't know how that could happen - for "locate" itself to be running, some user must have run it, as far as I'm aware.
Last edited by rworkman; 01-16-2018 at 02:12 AM.
Reason: Re slocate running....
Alright, and thanks. As I ran the locate command to locate slocate, maybe ps found the instance I was running. On the other hand I ran grep on /etc and couldn't find an instance of the string slocate. Perhaps ... Oh! Of course: the string in /etc/cron.daily is "updatedb", and not slocate. That's why grep deceived me.
Having been lucky to obtain a precise answer, I'd like you to tell me (I'm still running 14.1) if there is much difference with 14.2. As regards general resources and specially in disk space. If it is not to abuse.
EDIT: first thing I had done when I saw the disk activity was to look into /etc/rc.d. Of course I couldn't find anything. Those files have /etc directly as there parent.
14.2 is pretty incremental from 14.1, but that's a matter of perspective, I suppose, and my perspective is certainly not shared among the entire userbase.
This is about the best summary I can give you: https://mirrors.slackware.com/slackw..._AND_HINTS.TXT
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.