On Mon, 11 Apr 2022 at 09:50, Greg Wooledge wrote:
> On Mon, Apr 11, 2022 at 09:34:42AM +1000, David wrote:
> > On Mon, 11 Apr 2022 at 09:24, David Wright wrote:
> >
> > > systemctl disable mlocate.service before you fiddle with its
> > > configuration, then enable it afterwards.
> >
> > Hi, I
On Mon, Apr 11, 2022 at 09:34:42AM +1000, David wrote:
> On Mon, 11 Apr 2022 at 09:24, David Wright wrote:
>
> > systemctl disable mlocate.service before you fiddle with its
> > configuration, then enable it afterwards.
>
> Hi, I think you need "stop" and "start" there, not "disable" and
>
On Mon, 11 Apr 2022 at 09:24, David Wright wrote:
> systemctl disable mlocate.service before you fiddle with its
> configuration, then enable it afterwards.
Hi, I think you need "stop" and "start" there, not "disable" and
and "enable".
Or maybe "systemctl daemon-reload" although I'm not sure
On Sun 10 Apr 2022 at 09:52:15 (-0500), Roy J. Tellason, Sr. wrote:
> On Saturday 09 April 2022 01:22:08 pm Charles Curley wrote:
> > On Sat, 9 Apr 2022 11:04:18 -0500
> > "Roy J. Tellason, Sr." wrote:
> >
> > > How do I find out where this is invoked, so I can get rid of it?
> >
> > You may
On Sun 10 Apr 2022 at 10:04:53 (-0400), Greg Wooledge wrote:
> On Sun, Apr 10, 2022 at 11:33:53AM +0200, Linux-Fan wrote:
> > Greg Wooledge writes:
> > > unicorn:~$ less /lib/systemd/system/mlocate.timer
> > > [Unit]
> > > Description=Updates mlocate database every day
> > >
> > > [Timer]
> > >
On Sunday, 10 April 2022 10:04:53 EDT Greg Wooledge wrote:
> On Sun, Apr 10, 2022 at 11:33:53AM +0200, Linux-Fan wrote:
> > Greg Wooledge writes:
> > > unicorn:~$ less /lib/systemd/system/mlocate.timer
> > > [Unit]
> > > Description=Updates mlocate database every day
> > >
> > > [Timer]
> > >
On Sun 10 Apr 2022 at 12:04:05 (-0400), Greg Wooledge wrote:
> On Sun, Apr 10, 2022 at 03:49:02PM +0100, Darac Marjal wrote:
> > Systemd already supports this.
> >
> > * AccuracySec= Specify the accuracy the timer shall elapse with. [...]
> > Within this time window, the expiry time shall be
On Sun, Apr 10, 2022 at 03:49:02PM +0100, Darac Marjal wrote:
> Systemd already supports this.
>
> * AccuracySec= Specify the accuracy the timer shall elapse with. [...]
> Within this time window, the expiry time shall be placed at a host-specific,
> randomized, but stable position.
>
> *
On Saturday 09 April 2022 05:11:39 pm Greg Wooledge wrote:
> On Sat, Apr 09, 2022 at 04:59:04PM -0400, gene heskett wrote:
> > On Saturday, 9 April 2022 16:35:26 EDT Greg Wooledge wrote:
> > > grep daily /etc/crontab
> >
> > Matches mine too Greg, so I expect thats default, but why is Roy's going
On 10/04/2022 15:29, Greg Wooledge wrote:
On Sun, Apr 10, 2022 at 06:03:13AM -0400, gene heskett wrote:
Thats fine, as long as the systemd stuff is disabled by finding an entry
in the presently logged in users ~/.config, but I do not consider that as
a user item. thats (updatedb) sysadmin
On Saturday 09 April 2022 01:22:08 pm Charles Curley wrote:
> On Sat, 9 Apr 2022 11:04:18 -0500
> "Roy J. Tellason, Sr." wrote:
>
> > How do I find out where this is invoked, so I can get rid of it?
>
> You may not want to get rid of it. That's the process that updates the
> database for the
On Saturday 09 April 2022 12:39:45 pm Roberto C. Sánchez wrote:
> On Sat, Apr 09, 2022 at 11:04:18AM -0500, Roy J. Tellason, Sr. wrote:
> > So around midnight I am seeing a burst of activity, which sometimes
> > interferes with whatever else I happen to be doing at the time. Looking at
> > the
On Sun, Apr 10, 2022 at 06:03:13AM -0400, gene heskett wrote:
> Thats fine, as long as the systemd stuff is disabled by finding an entry
> in the presently logged in users ~/.config, but I do not consider that as
> a user item. thats (updatedb) sysadmin stuff, and much of this hoohah
> could be
On Sun, Apr 10, 2022 at 11:33:53AM +0200, Linux-Fan wrote:
> Greg Wooledge writes:
> > unicorn:~$ less /lib/systemd/system/mlocate.timer
> > [Unit]
> > Description=Updates mlocate database every day
> >
> > [Timer]
> > OnCalendar=daily
> > AccuracySec=24h
> > Persistent=true
> >
> > [Install]
>
On Sunday, 10 April 2022 05:33:53 EDT Linux-Fan wrote:
> Greg Wooledge writes:
> > On Sat, Apr 09, 2022 at 09:26:58PM -0600, Charles Curley wrote:
> > > Two of my machines have their database files dated at midnight or
> > > one
> > > minute after.
> > >
> > > Possibly because updatedb is run by
Greg Wooledge writes:
On Sat, Apr 09, 2022 at 09:26:58PM -0600, Charles Curley wrote:
> Two of my machines have their database files dated at midnight or one
> minute after.
>
> Possibly because updatedb is run by a systemd timer, not cron.
[...]
# skip in favour of systemd timer
if [ -d
On Sat, Apr 09, 2022 at 11:59:07PM -0400, Greg Wooledge wrote:
[...]
> Oh well. It clearly isn't bothering me (I'm usually in bed before
> midnight, though not always), so I never had to look into it. I'm sure
> someone felt it was a "good idea" to move things from perfectly normal
> and
On Sat, Apr 09, 2022 at 09:26:58PM -0600, Charles Curley wrote:
> Two of my machines have their database files dated at midnight or one
> minute after.
>
> Possibly because updatedb is run by a systemd timer, not cron.
??
unicorn:~$ ls -l /var/lib/mlocate/mlocate.db
-rw-r- 1 root mlocate
On Sat, 09 Apr 2022 16:59:04 -0400
gene heskett wrote:
> Matches mine too Greg, so I expect thats default, but why is Roy's
> going off at about midnight?
Two of my machines have their database files dated at midnight or one
minute after.
Possibly because updatedb is run by a systemd timer,
On Sat, Apr 09, 2022 at 04:59:04PM -0400, gene heskett wrote:
> On Saturday, 9 April 2022 16:35:26 EDT Greg Wooledge wrote:
> > grep daily /etc/crontab
>
> Matches mine too Greg, so I expect thats default, but why is Roy's going
> off at about midnight?
We'd have to see what his /etc/crontab
On Saturday, 9 April 2022 16:35:26 EDT Greg Wooledge wrote:
> grep daily /etc/crontab
Matches mine too Greg, so I expect thats default, but why is Roy's going
off at about midnight?
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo.
On Sat, Apr 09, 2022 at 03:40:41PM -0400, gene heskett wrote:
> On Saturday, 9 April 2022 12:04:18 EDT Roy J. Tellason, Sr. wrote:
> > So around midnight I am seeing a burst of activity, which sometimes
> > interferes with whatever else I happen to be doing at the time.
> > Looking at the
On Saturday, 9 April 2022 12:04:18 EDT Roy J. Tellason, Sr. wrote:
> So around midnight I am seeing a burst of activity, which sometimes
> interferes with whatever else I happen to be doing at the time.
> Looking at the process list, I see the above-referenced come and go.
> I didn't want
On Sat, 9 Apr 2022 13:59:44 -0400
Greg Wooledge wrote:
Hello Greg,
>This is not the case in Debian 11 (stable).
You're right. I misread the page and muddled the stable and backports
lines.
My apologies for the confusion.
--
Regards _
/ ) "The blindingly obvious is never
On Sat, Apr 09, 2022 at 06:18:31PM +0100, Brad Rogers wrote:
> mlocate is a transitional package in Debian. It installs plocate. Which
> means Roy is likely running plocate anyway. Therefore mlocate can be
> removed.
This is not the case in Debian 11 (stable). It appears to be true in
testing
On Sat 09 Apr 2022 at 18:18:31 +0100, Brad Rogers wrote:
> On Sat, 9 Apr 2022 17:50:03 +0100
> Brian wrote:
>
> Hello Brian,
>
> >Or replace mlocate with plocate, which is reckoned to be better than
>
> mlocate is a transitional package in Debian. It installs plocate. Which
> means Roy is
On Sat, 9 Apr 2022 17:50:03 +0100
Brian wrote:
<
plocate is a locate(1) based on posting lists, giving much faster searches
on a much smaller index. It is a drop-in replacement for mlocate in nearly
all aspects, and is fast on SSDs and non-SSDs alike.
>
Besides this it also handles sshfs mounts
On Sat, 9 Apr 2022 17:50:03 +0100
Brian wrote:
Hello Brian,
>Or replace mlocate with plocate, which is reckoned to be better than
mlocate is a transitional package in Debian. It installs plocate. Which
means Roy is likely running plocate anyway. Therefore mlocate can be
removed.
From info
On Sat, 9 Apr 2022 11:04:18 -0500
"Roy J. Tellason, Sr." wrote:
> How do I find out where this is invoked, so I can get rid of it?
You may not want to get rid of it. That's the process that updates the
database for the locate utility, which is very useful.
I was about to add, think instead
On Sat 09 Apr 2022 at 12:39:45 -0400, Roberto C. Sánchez wrote:
> On Sat, Apr 09, 2022 at 11:04:18AM -0500, Roy J. Tellason, Sr. wrote:
> > So around midnight I am seeing a burst of activity, which sometimes
> > interferes with whatever else I happen to be doing at the time. Looking at
> >
On Sat, Apr 09, 2022 at 11:04:18AM -0500, Roy J. Tellason, Sr. wrote:
> So around midnight I am seeing a burst of activity, which sometimes
> interferes with whatever else I happen to be doing at the time. Looking at
> the process list, I see the above-referenced come and go. I didn't want
So around midnight I am seeing a burst of activity, which sometimes interferes
with whatever else I happen to be doing at the time. Looking at the process
list, I see the above-referenced come and go. I didn't want this, and it's
not apparent to me how to deal with it.
How do I find out
32 matches
Mail list logo
