Hello,
In my mailbox, I receive emails: Anacron job 'cron.weekly' on While I do not receive any amail: Anacron job 'cron.daily' on
while it should run daily: logrotate certwatch
It even more strange, on a fc22 machine I had Anacron job 'cron.daily' on until July 14. and then not anymore !
Is anacrontab controlled by /etc/crontab or by /etc/anacrontab ?
In addition, in fc22 I had: /etc/cron.daily/mlocate
while in fc24, I do not have such a file. How mlocate is now managed ?
Thank.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
On 09/17/2016 07:51 AM, Patrick Dupre wrote:
Hello,
In my mailbox, I receive emails: Anacron job 'cron.weekly' on While I do not receive any amail: Anacron job 'cron.daily' on
while it should run daily: logrotate certwatch
It even more strange, on a fc22 machine I had Anacron job 'cron.daily' on until July 14. and then not anymore !
Is anacrontab controlled by /etc/crontab or by /etc/anacrontab ?
In addition, in fc22 I had: /etc/cron.daily/mlocate
while in fc24, I do not have such a file. How mlocate is now managed ?
Thank.
Anacron is what's used and that uses /etc/anacrontab. The last few lines of the file: #period in days delay in minutes job-identifier command 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly
I can't say if /etc/crontab is still used. It has no lines like what's above to do anything.
As for mlocate it's now a (or part of a) service: [mcallman@draco ~]$ systemctl | grep -i locate mlocate-updatedb.timer loaded active waiting Updates mlocate database every day
Mark C. Allman, PMP, CSM Founder, See How You Ski, www.seehowyouski.com Sr. Project Manager, Allman Professional Consulting, Inc., www.allmanpc.com 617-947-4263, Twitter: @allmanpc
Hello,
1) In fc22, anacron (and crond) sent mail to root every time that it was running. How can I recover this function with fc24 ?
2) Now, anacron and cron work. However, I have in /etc/crontab 22 23 * * * root run-parts /etc/cron.daily 06 13 * * 6 root run-parts /etc/cron.weekly and in /ect/anacrontab 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly
But crond.weekly runs on the Monday while it must have run on Saturday !
Sep 19 10:01:01 teucidide anacron[4820]: Will run job `cron.weekly' in 54 min. Sep 19 10:01:01 teucidide anacron[4820]: Jobs will be executed sequentially Sep 19 10:35:01 teucidide anacron[4820]: Job `cron.daily' started Sep 19 10:35:02 teucidide run-parts[6320]: (/etc/cron.daily) finished certwatch Sep 19 10:35:03 teucidide run-parts[6327]: (/etc/cron.daily) finished logrotate Sep 19 10:35:03 teucidide anacron[4820]: Job `cron.daily' terminated Sep 19 10:55:01 teucidide anacron[4820]: Job `cron.weekly' started
3) systemctl | grep -i locate provides not answer. How can I check that mlocate run properly ? There is not service locate or mlocate
Thank for your help.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
On 09/17/2016 07:51 AM, Patrick Dupre wrote:
Hello,
In my mailbox, I receive emails: Anacron job 'cron.weekly' on While I do not receive any amail: Anacron job 'cron.daily' on
while it should run daily: logrotate certwatch
It even more strange, on a fc22 machine I had Anacron job 'cron.daily' on until July 14. and then not anymore !
Is anacrontab controlled by /etc/crontab or by /etc/anacrontab ?
In addition, in fc22 I had: /etc/cron.daily/mlocate
while in fc24, I do not have such a file. How mlocate is now managed ?
Thank.
Anacron is what's used and that uses /etc/anacrontab. The last few lines of the file: #period in days delay in minutes job-identifier command 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly
I can't say if /etc/crontab is still used. It has no lines like what's above to do anything.
As for mlocate it's now a (or part of a) service: [mcallman@draco ~]$ systemctl | grep -i locate mlocate-updatedb.timer loaded active waiting Updates mlocate database every day
Mark C. Allman, PMP, CSM Founder, See How You Ski, www.seehowyouski.com Sr. Project Manager, Allman Professional Consulting, Inc., www.allmanpc.com 617-947-4263, Twitter: @allmanpc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
Install cronie-noanacron then remove cronie-anacron.
Anacron should not be setup for servers, but is good for a laptop.
On Mon, 2016-09-19 at 11:42 +0200, Patrick Dupre wrote:
Hello,
- In fc22, anacron (and crond) sent mail to root every time that it
was running. How can I recover this function with fc24 ?
- Now, anacron and cron work. However, I have
in /etc/crontab 22 23 * * * root run-parts /etc/cron.daily 06 13 * * 6 root run-parts /etc/cron.weekly and in /ect/anacrontab
1 5 cron.daily nice run-parts
/etc/cron.daily
7 25 cron.weekly nice run-parts
/etc/cron.weekly
@monthly 45 cron.monthly nice run-parts
/etc/cron.monthly
But crond.weekly runs on the Monday while it must have run on
Saturday !
Sep 19 10:01:01 teucidide anacron[4820]: Will run job `cron.weekly'
in 54 min.
Sep 19 10:01:01 teucidide anacron[4820]: Jobs will be executed
sequentially
Sep 19 10:35:01 teucidide anacron[4820]: Job `cron.daily' started
Sep 19 10:35:02 teucidide run-parts[6320]: (/etc/cron.daily) finished
certwatch
Sep 19 10:35:03 teucidide run-parts[6327]: (/etc/cron.daily) finished
logrotate
Sep 19 10:35:03 teucidide anacron[4820]: Job `cron.daily' terminated Sep 19 10:55:01 teucidide anacron[4820]: Job `cron.weekly' started
- systemctl | grep -i locate
provides not answer. How can I check that mlocate run properly ? There is not service locate or mlocate
Thank for your help.
=====================================================================
======
Patrick DUPRÉ | | email: pdupre@gmx.
com
Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | |
Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82
44
189A, avenue Maurice Schumann | | 59140 Dunkerque,
France
=====================================================================
======
On 09/17/2016 07:51 AM, Patrick Dupre wrote:
Hello,
In my mailbox, I receive emails: Anacron job 'cron.weekly' on While I do not receive any amail: Anacron job 'cron.daily' on
while it should run daily: logrotate certwatch
It even more strange, on a fc22 machine I had Anacron job
'cron.daily' on
until July 14. and then not anymore !
Is anacrontab controlled by /etc/crontab or by /etc/anacrontab ?
In addition, in fc22 I had: /etc/cron.daily/mlocate
while in fc24, I do not have such a file. How mlocate is now managed ?
Thank.
Anacron is what's used and that uses /etc/anacrontab. The last few lines of the file: #period in days delay in minutes job-identifier command 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly
@monthly 45 cron.monthly nice run-parts
/etc/cron.monthly
I can't say if /etc/crontab is still used. It has no lines like
what's
above to do anything.
As for mlocate it's now a (or part of a) service:
[mcallman@draco ~]$ systemctl | grep -i locate
mlocate-updatedb.timer loaded active waiting Updates mlocate database every day
Mark C. Allman, PMP, CSM Founder, See How You Ski, www.seehowyouski.com
Sr. Project Manager, Allman Professional Consulting, Inc., www.allm
anpc.com
617-947-4263, Twitter: @allmanpc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
-- Brian Millett "Gentlemen, of all things in life, are females not the finest?" 'On that, Mollari, we can at least agree.' -- [ Londo and G'Kar, "Born to the Purple"]
On 09/19/2016 05:42 AM, Patrick Dupre wrote:
Hello,
- In fc22, anacron (and crond) sent mail to root every time that it
was running. How can I recover this function with fc24 ?
- Now, anacron and cron work. However, I have
in /etc/crontab 22 23 * * * root run-parts /etc/cron.daily 06 13 * * 6 root run-parts /etc/cron.weekly and in /ect/anacrontab 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly
But crond.weekly runs on the Monday while it must have run on Saturday !
Sep 19 10:01:01 teucidide anacron[4820]: Will run job `cron.weekly' in 54 min. Sep 19 10:01:01 teucidide anacron[4820]: Jobs will be executed sequentially Sep 19 10:35:01 teucidide anacron[4820]: Job `cron.daily' started Sep 19 10:35:02 teucidide run-parts[6320]: (/etc/cron.daily) finished certwatch Sep 19 10:35:03 teucidide run-parts[6327]: (/etc/cron.daily) finished logrotate Sep 19 10:35:03 teucidide anacron[4820]: Job `cron.daily' terminated Sep 19 10:55:01 teucidide anacron[4820]: Job `cron.weekly' started
- systemctl | grep -i locate
provides not answer. How can I check that mlocate run properly ? There is not service locate or mlocate
Thank for your help.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
On 09/17/2016 07:51 AM, Patrick Dupre wrote:
Hello,
In my mailbox, I receive emails: Anacron job 'cron.weekly' on While I do not receive any amail: Anacron job 'cron.daily' on
while it should run daily: logrotate certwatch
It even more strange, on a fc22 machine I had Anacron job 'cron.daily' on until July 14. and then not anymore !
Is anacrontab controlled by /etc/crontab or by /etc/anacrontab ?
In addition, in fc22 I had: /etc/cron.daily/mlocate
while in fc24, I do not have such a file. How mlocate is now managed ?
Thank.
Anacron is what's used and that uses /etc/anacrontab. The last few lines of the file: #period in days delay in minutes job-identifier command 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly
I can't say if /etc/crontab is still used. It has no lines like what's above to do anything.
As for mlocate it's now a (or part of a) service: [mcallman@draco ~]$ systemctl | grep -i locate mlocate-updatedb.timer loaded active waiting Updates mlocate database every day
Mark C. Allman, PMP, CSM Founder, See How You Ski, www.seehowyouski.com Sr. Project Manager, Allman Professional Consulting, Inc., www.allmanpc.com 617-947-4263, Twitter: @allmanpc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.or
I'm running F24 so it's not straightforward to say what to do for F22. Do you have the mlocate package installed? On F24: [mcallman@draco etc]$ rpm -q mlocate mlocate-0.26-14.fc24.x86_64
I don't think anacron or cron by themselves send mail unless a job they're running sends output to STDOUT or STDERR. Anacron/cron won't send me a daily logwatch report -- that's configured in logwatch. Anacron just runs the job. You might also need to have something such as sendmail installed that will do the mail delivery work. There was something in recent release notes about not needing sendmail any longer but I don't remember the details.
/etc/crontab should be empty. The crond.service I believe runs what users set up in their respective crontab files, what's in /etc/crontab and also what's in /etc/cron.d. The file "0hourly" in /etc/cron.d has an entry to run each hour what's in /etc/cron.hourly. That has the file "0anacron" which has some checks in it and then runs anacron, which then runs everything listed in anacrontab. Look at "0anacron" and you'll see checks for /etc/cron.daily. These checks might prevent daily jobs being run twice if /etc/cron.daily is listed in both anacrontab and crontab but it looks like it's an error to list /etc/cron.daily in both. Same for /etc/cron.weekly and the others.
Mark C. Allman, PMP, CSM Founder, See How You Ski, www.seehowyouski.com Sr. Project Manager, Allman Professional Consulting, Inc., www.allmanpc.com 617-947-4263, Twitter: @allmanpc
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
On 09/19/2016 05:42 AM, Patrick Dupre wrote:
Hello,
- In fc22, anacron (and crond) sent mail to root every time that it
was running. How can I recover this function with fc24 ?
- Now, anacron and cron work. However, I have
in /etc/crontab 22 23 * * * root run-parts /etc/cron.daily 06 13 * * 6 root run-parts /etc/cron.weekly and in /ect/anacrontab 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly
But crond.weekly runs on the Monday while it must have run on Saturday !
Sep 19 10:01:01 teucidide anacron[4820]: Will run job `cron.weekly' in 54 min. Sep 19 10:01:01 teucidide anacron[4820]: Jobs will be executed sequentially Sep 19 10:35:01 teucidide anacron[4820]: Job `cron.daily' started Sep 19 10:35:02 teucidide run-parts[6320]: (/etc/cron.daily) finished certwatch Sep 19 10:35:03 teucidide run-parts[6327]: (/etc/cron.daily) finished logrotate Sep 19 10:35:03 teucidide anacron[4820]: Job `cron.daily' terminated Sep 19 10:55:01 teucidide anacron[4820]: Job `cron.weekly' started
- systemctl | grep -i locate
provides not answer. How can I check that mlocate run properly ? There is not service locate or mlocate
Thank for your help.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
On 09/17/2016 07:51 AM, Patrick Dupre wrote:
Hello,
In my mailbox, I receive emails: Anacron job 'cron.weekly' on While I do not receive any amail: Anacron job 'cron.daily' on
while it should run daily: logrotate certwatch
It even more strange, on a fc22 machine I had Anacron job 'cron.daily' on until July 14. and then not anymore !
Is anacrontab controlled by /etc/crontab or by /etc/anacrontab ?
In addition, in fc22 I had: /etc/cron.daily/mlocate
while in fc24, I do not have such a file. How mlocate is now managed ?
Thank.
Anacron is what's used and that uses /etc/anacrontab. The last few lines of the file: #period in days delay in minutes job-identifier command 1 5 cron.daily nice run-parts /etc/cron.daily 7 25 cron.weekly nice run-parts /etc/cron.weekly @monthly 45 cron.monthly nice run-parts /etc/cron.monthly
I can't say if /etc/crontab is still used. It has no lines like what's above to do anything.
As for mlocate it's now a (or part of a) service: [mcallman@draco ~]$ systemctl | grep -i locate mlocate-updatedb.timer loaded active waiting Updates mlocate database every day
Mark C. Allman, PMP, CSM Founder, See How You Ski, www.seehowyouski.com Sr. Project Manager, Allman Professional Consulting, Inc., www.allmanpc.com 617-947-4263, Twitter: @allmanpc _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.or
I'm running F24 so it's not straightforward to say what to do for F22. Do you have the mlocate package installed? On F24: [mcallman@draco etc]$ rpm -q mlocate mlocate-0.26-14.fc24.x86_64
Yes this version of mlocate is installed
I don't think anacron or cron by themselves send mail unless a job they're running sends output to STDOUT or STDERR. Anacron/cron won't send me a daily logwatch report -- that's configured in logwatch. Anacron just runs the job. You might also need to have something such as sendmail installed that will do the mail delivery work. There was something in recent release notes about not needing sendmail any longer but I don't remember the details.
Yes I have sendmail is installed: This is what I got in the roor mailbox with fc22
N 3 Jun 25 Anacron (2K) Anacron job 'cron.weekly' on teucidi N 4 Jun 25 (Cron Daemon) (1K) Cron root@teucidide run-parts /etc N 5 Jun 26 Anacron (735) Anacron job 'cron.daily' on teucidid N 6 Jun 26 (Cron Daemon) (1K) Cron root@teucidide run-parts /etc N 7 Jun 27 Anacron (735) Anacron job 'cron.daily' on teucidid
/etc/crontab should be empty.
In fc24, it seems that /etc/crontab is ignored How can I control cron.daily and cron.weekly ,
The crond.service I believe runs what
users set up in their respective crontab files, what's in /etc/crontab and also what's in /etc/cron.d. The file "0hourly" in /etc/cron.d has an entry to run each hour what's in /etc/cron.hourly. That has the file "0anacron" which has some checks in it and then runs anacron, which then runs everything listed in anacrontab. Look at "0anacron" and you'll see checks for /etc/cron.daily. These checks might prevent daily jobs being run twice if /etc/cron.daily is listed in both anacrontab and crontab but it looks like it's an error to list /etc/cron.daily in both. Same for /etc/cron.weekly and the others.
Mark C. Allman, PMP, CSM Founder, See How You Ski, www.seehowyouski.com Sr. Project Manager, Allman Professional Consulting, Inc., www.allmanpc.com 617-947-4263, Twitter: @allmanpc
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Mon, Sep 19, 2016 at 11:42:42AM +0200, Patrick Dupre wrote:
Hello,
...
- systemctl | grep -i locate
provides not answer. How can I check that mlocate run properly ? There is not service locate or mlocate
locate does not run as a service.
locate's database is updated daily via
/etc/cron.daily/mlocate.cron
jon
Sorry, but I do not have /etc/cron.daily/mlocate.cron
ls -l /etc/cron.daily -rwxr-xr-x. 1 root root 2239 Feb 11 2016 certwatch -rwxr-xr-x. 1 root root 219 Jul 20 15:57 logrotate
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 8:37 PM From: "Jon LaBadie" jonfu@jgcomp.com To: users@lists.fedoraproject.org Subject: Re: anacron/cron
On Mon, Sep 19, 2016 at 11:42:42AM +0200, Patrick Dupre wrote:
Hello,
...
- systemctl | grep -i locate
provides not answer. How can I check that mlocate run properly ? There is not service locate or mlocate
locate does not run as a service.
locate's database is updated daily via
/etc/cron.daily/mlocate.cron
jon
Jon H. LaBadie jonfu@jgcomp.com _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Mon, 19 Sep 2016 20:47:20 +0200 Patrick Dupre wrote:
Sorry, but I do not have /etc/cron.daily/mlocate.cron
This is all part of the systemd fungus experience as it attempts to engulph all of linux.
An rpm -q --list mlocate shows these files on my fedora 24 system:
/usr/lib/systemd/system/mlocate-updatedb.service /usr/lib/systemd/system/mlocate-updatedb.timer
So it is now running on a systemd timer, not in cron (this helps make sure no one has any idea what the heck is going on).
The point is that I am not sure that mlocate (or updatedb) runs properly because locate does not find my new files !
How can I be sure that mlocate runs properly ?
Thank.
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 9:15 PM From: "Tom Horsley" horsley1953@gmail.com To: "Patrick Dupre" pdupre@gmx.com Cc: users@lists.fedoraproject.org Subject: Re: anacron/cron
On Mon, 19 Sep 2016 20:47:20 +0200 Patrick Dupre wrote:
Sorry, but I do not have /etc/cron.daily/mlocate.cron
This is all part of the systemd fungus experience as it attempts to engulph all of linux.
An rpm -q --list mlocate shows these files on my fedora 24 system:
/usr/lib/systemd/system/mlocate-updatedb.service /usr/lib/systemd/system/mlocate-updatedb.timer
So it is now running on a systemd timer, not in cron (this helps make sure no one has any idea what the heck is going on).
-rw-r-----. 1 root slocate 30573186 Sep 12 15:40 /var/lib/mlocate/mlocate.db
This what I anticipated, The database has not been updated for a week !
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 10:11 PM From: "Joe Zeff" joe@zeff.us To: "Community support for Fedora users" users@lists.fedoraproject.org Subject: Re: anacron/cron
On 09/19/2016 01:04 PM, Patrick Dupre wrote:
How can I be sure that mlocate runs properly ?
If all else fails, run this as root:
ls -l /var/lib/mlocate/mlocate.db
and see when it was last updated. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
It *should* be running every day, but just checked my system and it's not enabled either and hasn't run for a week as well - possible bug? Anyway, to fix it, run the following commands (as root or via sudo):
systemctl list-timers --all
That *should* list a UNIT called "mlocate-updatedb.timer", but on my system it did not. To enable it, use the following command:
systemctl enable mlocate-updatedb.timer
You can also update the DB manually by running the script that calls:
/usr/libexec/mlocate-run-updatedb
Getting back to that "list-timers" command, all of systemd's timers are in "/usr/lib/systemd/system/" and have the extenstion "timer". Might be worth having a look and seeing what else you think should be running, but isn't...
Andy
On 19 September 2016 at 21:16, Patrick Dupre pdupre@gmx.com wrote:
-rw-r-----. 1 root slocate 30573186 Sep 12 15:40 /var/lib/mlocate/mlocate.db
This what I anticipated, The database has not been updated for a week !
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 10:11 PM From: "Joe Zeff" joe@zeff.us To: "Community support for Fedora users" users@lists.fedoraproject.org Subject: Re: anacron/cron
On 09/19/2016 01:04 PM, Patrick Dupre wrote:
How can I be sure that mlocate runs properly ?
If all else fails, run this as root:
ls -l /var/lib/mlocate/mlocate.db
and see when it was last updated. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
I did: systemctl enable mlocate-updatedb.service (no error) but it still does not seem to be enabled: ● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disable Active: inactive (dead)
Sep 19 23:15:02 teucidide systemd[1]: Stopped Update a database for mlocate. Sep 19 23:15:03 teucidide systemd[1]: Started Update a database for mlocate.
systemctl is-enabled mlocate-updatedb.service static
Is it OK ?
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 10:30 PM From: "Andy Blanchard" zocalo@gmail.com To: "Community support for Fedora users" users@lists.fedoraproject.org Subject: Re: anacron/cron
It *should* be running every day, but just checked my system and it's not enabled either and hasn't run for a week as well - possible bug? Anyway, to fix it, run the following commands (as root or via sudo):
systemctl list-timers --all
That *should* list a UNIT called "mlocate-updatedb.timer", but on my system it did not. To enable it, use the following command:
systemctl enable mlocate-updatedb.timer
You can also update the DB manually by running the script that calls:
/usr/libexec/mlocate-run-updatedb
Getting back to that "list-timers" command, all of systemd's timers are in "/usr/lib/systemd/system/" and have the extenstion "timer". Might be worth having a look and seeing what else you think should be running, but isn't...
Andy
On 19 September 2016 at 21:16, Patrick Dupre pdupre@gmx.com wrote:
-rw-r-----. 1 root slocate 30573186 Sep 12 15:40 /var/lib/mlocate/mlocate.db
This what I anticipated, The database has not been updated for a week !
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 10:11 PM From: "Joe Zeff" joe@zeff.us To: "Community support for Fedora users" users@lists.fedoraproject.org Subject: Re: anacron/cron
On 09/19/2016 01:04 PM, Patrick Dupre wrote:
How can I be sure that mlocate runs properly ?
If all else fails, run this as root:
ls -l /var/lib/mlocate/mlocate.db
and see when it was last updated. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
-- Andy
The only person to have all his work done by Friday was Robinson Crusoe _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On 19 September 2016 at 22:38, Patrick Dupre pdupre@gmx.com wrote:
I did: systemctl enable mlocate-updatedb.service (no error) but it still does not seem to be enabled: ● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disable Active: inactive (dead)
Sep 19 23:15:02 teucidide systemd[1]: Stopped Update a database for mlocate. Sep 19 23:15:03 teucidide systemd[1]: Started Update a database for mlocate.
systemctl is-enabled mlocate-updatedb.service static
Is it OK ?
AFAICT the service only runs the mlocate update once on boot. What you need for regular mlocate DB updates is the systemd timer, which will run the necessary script at midnight every day by default:
systemctl enable mlocate-updatedb.timer
Note that last bit reads "timer" not "service". You can check if it's enabled by running:
systemctl list-timers
and looking for "mlocate-updatedb.timer" in the fifth ("UNIT") column - the entry in the first column is when it's next scheduled to run.
On 09/19/2016 02:57 PM, Andy Blanchard wrote:
On 19 September 2016 at 22:38, Patrick Dupre pdupre@gmx.com wrote:
I did: systemctl enable mlocate-updatedb.service (no error) but it still does not seem to be enabled: ● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disable Active: inactive (dead)
Sep 19 23:15:02 teucidide systemd[1]: Stopped Update a database for mlocate. Sep 19 23:15:03 teucidide systemd[1]: Started Update a database for mlocate.
systemctl is-enabled mlocate-updatedb.service static
Is it OK ?
AFAICT the service only runs the mlocate update once on boot. What you need for regular mlocate DB updates is the systemd timer, which will run the necessary script at midnight every day by default:
systemctl enable mlocate-updatedb.timer
Note that last bit reads "timer" not "service". You can check if it's enabled by running:
systemctl list-timers
and looking for "mlocate-updatedb.timer" in the fifth ("UNIT") column
- the entry in the first column is when it's next scheduled to run.
Well, lovely. I've found that "systemctl --full list-timers" truncates the display if your terminal isn't wide enough (at least it truncates using xfce-terminal) and gives you no indication it has done so. Isn't "--full" supposed to wrap the display so that doesn't happen? That's what the man page says it does.
Yet another reason I absolutely deplore this systemd/systemctl crap. ---------------------------------------------------------------------- - Rick Stevens, Systems Engineer, AllDigital ricks@alldigital.com - - AIM/Skype: therps2 ICQ: 226437340 Yahoo: origrps2 - - - - Political Correctness: The insane doctrine that postulates that it - - is entirely possible to pick up a turd by the clean end. - ----------------------------------------------------------------------
On Mon, Sep 19, 2016 at 03:09:39PM -0700, Rick Stevens wrote:
Well, lovely. I've found that "systemctl --full list-timers" truncates the display if your terminal isn't wide enough (at least it truncates using xfce-terminal) and gives you no indication it has done so. Isn't "--full" supposed to wrap the display so that doesn't happen? That's what the man page says it does.
Yet another reason I absolutely deplore this systemd/systemctl crap.
It may be like journalctl output. You can shift the display right and left by using your arrow keys.
jl
Well, lovely. I've found that "systemctl --full list-timers" truncates the display if your terminal isn't wide enough (at least it truncates using xfce-terminal) and gives you no indication it has done so. Isn't "--full" supposed to wrap the display so that doesn't happen? That's what the man page says it does.
The same thing happens with the Mate desktop
On Mon, Sep 19, 2016 at 10:57:01PM +0100, Andy Blanchard wrote:
On 19 September 2016 at 22:38, Patrick Dupre pdupre@gmx.com wrote:
I did: systemctl enable mlocate-updatedb.service (no error) but it still does not seem to be enabled: ● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disable Active: inactive (dead)
^^^^^^^^
From what I can tell, static services are not intended to be enabled. They are things that will be executed on an as needed basis from other things. In this case it is mlocate-updatedb.timer (timer not service).
Sep 19 23:15:02 teucidide systemd[1]: Stopped Update a database for mlocate. Sep 19 23:15:03 teucidide systemd[1]: Started Update a database for mlocate.
systemctl is-enabled mlocate-updatedb.service static
Is it OK ?
AFAICT the service only runs the mlocate update once on boot. What you need for regular mlocate DB updates is the systemd timer, which will run the necessary script at midnight every day by default:
systemctl enable mlocate-updatedb.timer
Note that last bit reads "timer" not "service". You can check if it's enabled by running:
systemctl list-timers
and looking for "mlocate-updatedb.timer" in the fifth ("UNIT") column
- the entry in the first column is when it's next scheduled to run.
If .timer units are like .service units, enabling will only affect its startup at the next boot. You will have to "systemctl start" or restart the unit to have it available during the current boot.
Jon
On 09/20/16 05:38, Patrick Dupre wrote:
I did: systemctl enable mlocate-updatedb.service (no error) but it still does not seem to be enabled:
Re-Read what is below....
You want...
systemctl enable mlocate-updatedb.timer ^ ^ ^
● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disable Active: inactive (dead)
Sep 19 23:15:02 teucidide systemd[1]: Stopped Update a database for mlocate. Sep 19 23:15:03 teucidide systemd[1]: Started Update a database for mlocate.
systemctl is-enabled mlocate-updatedb.service static
Is it OK ?
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 10:30 PM From: "Andy Blanchard" zocalo@gmail.com To: "Community support for Fedora users" users@lists.fedoraproject.org Subject: Re: anacron/cron
It *should* be running every day, but just checked my system and it's not enabled either and hasn't run for a week as well - possible bug? Anyway, to fix it, run the following commands (as root or via sudo):
systemctl list-timers --all
That *should* list a UNIT called "mlocate-updatedb.timer", but on my system it did not. To enable it, use the following command:
systemctl enable mlocate-updatedb.timer
You can also update the DB manually by running the script that calls:
/usr/libexec/mlocate-run-updatedb
Getting back to that "list-timers" command, all of systemd's timers are in "/usr/lib/systemd/system/" and have the extenstion "timer". Might be worth having a look and seeing what else you think should be running, but isn't...
Andy
On 19 September 2016 at 21:16, Patrick Dupre pdupre@gmx.com wrote:
-rw-r-----. 1 root slocate 30573186 Sep 12 15:40 /var/lib/mlocate/mlocate.db
This what I anticipated, The database has not been updated for a week !
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 10:11 PM From: "Joe Zeff" joe@zeff.us To: "Community support for Fedora users" users@lists.fedoraproject.org Subject: Re: anacron/cron
On 09/19/2016 01:04 PM, Patrick Dupre wrote:
How can I be sure that mlocate runs properly ?
If all else fails, run this as root:
ls -l /var/lib/mlocate/mlocate.db
and see when it was last updated. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
-- Andy
The only person to have all his work done by Friday was Robinson Crusoe _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Mon, Sep 19, 2016 at 10:04:21PM +0200, Patrick Dupre wrote:
The point is that I am not sure that mlocate (or updatedb) runs properly because locate does not find my new files !
How can I be sure that mlocate runs properly ?
Sorry for the erroneous post. Turns out the cron file I have is a leftover from F22 and earlier. With F23 it went with to the systemd service Tom mentions. My cron file was left behind because I had modified it and renamed it mlocate.cron.local.
As to locate not finding new files, two possibilities even if things are running properly.
The db is only automatically updated daily. So if you create a file and try to locate it before the auto-update, it will not find it.
The other possibility is a permissions situation. mlocate will not show you the names of files you are not allowed to access. So if you create new files as a different user, or under a permission protected directory, mlocate will not show them to you.
Jon
Sent: Monday, September 19, 2016 at 9:15 PM From: "Tom Horsley" horsley1953@gmail.com To: "Patrick Dupre" pdupre@gmx.com Cc: users@lists.fedoraproject.org Subject: Re: anacron/cron
On Mon, 19 Sep 2016 20:47:20 +0200 Patrick Dupre wrote:
Sorry, but I do not have /etc/cron.daily/mlocate.cron
This is all part of the systemd fungus experience as it attempts to engulph all of linux.
An rpm -q --list mlocate shows these files on my fedora 24 system:
/usr/lib/systemd/system/mlocate-updatedb.service /usr/lib/systemd/system/mlocate-updatedb.timer
So it is now running on a systemd timer, not in cron (this helps make sure no one has any idea what the heck is going on).
users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
End of included message <<<
On Mon, Sep 19, 2016 at 04:28:15PM -0400, Jon LaBadie wrote:
On Mon, Sep 19, 2016 at 10:04:21PM +0200, Patrick Dupre wrote:
The point is that I am not sure that mlocate (or updatedb) runs properly because locate does not find my new files !
How can I be sure that mlocate runs properly ?
..
As to locate not finding new files, two possibilities even if things are running properly.
The db is only automatically updated daily. So if you create a file and try to locate it before the auto-update, it will not find it.
The other possibility is a permissions situation. mlocate will not show you the names of files you are not allowed to access. So if you create new files as a different user, or under a permission protected directory, mlocate will not show them to you.
Thought of a 3rd possibility, updatedb consults a config file, /etc/updatedb.conf. It specifies lots of things that updatedb is to skip. Certain directories, filename extensions, and filesystem types.
On Mon, 19 Sep 2016 22:04:21 +0200 "Patrick Dupre" pdupre@gmx.com wrote:
The point is that I am not sure that mlocate (or updatedb) runs properly because locate does not find my new files !
How can I be sure that mlocate runs properly ?
$ systemctl status mlocate-updatedb.service ● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disabled) Active: inactive (dead) since Mon 2016-09-19 09:14:14 MST; 4h 7min ago Process: 1046 ExecStart=/usr/libexec/mlocate-run-updatedb (code=exited, status=0/SUCCESS) Main PID: 1046 (code=exited, status=0/SUCCESS)
This looks like it runs at start, and that's it. You could try running systemctl restart mlocate-updatedb.service and see if that updates your database.
The man pages for updatedb.conf and updatedb seem to suggest that it is possible to run updatedb from the command line, and to create your own local version of updatedb as a user.
OK, Thank.
It was inactive, Then I restart it and now: ● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disable Active: active (running) since Mon 2016-09-19 23:15:03 CEST; 1min 17s ago Main PID: 1357 (mlocate-run-upd) Tasks: 2 (limit: 512) CGroup: /system.slice/mlocate-updatedb.service ├─1357 /bin/sh /usr/libexec/mlocate-run-updatedb └─1377 /usr/bin/updatedb -f sysfs ramfs bdev proc cpuset cgroup cgroup2 tmpfs devtmpfs c
Sep 19 23:15:02 teucidide systemd[1]: Stopped Update a database for mlocate. Sep 19 23:15:03 teucidide systemd[1]: Started Update a database for mlocate.
I guess that I need to enable it
=========================================================================== Patrick DUPRÉ | | email: pdupre@gmx.com Laboratoire de Physico-Chimie de l'Atmosphère | | Université du Littoral-Côte d'Opale | | Tel. (33)-(0)3 28 23 76 12 | | Fax: 03 28 65 82 44 189A, avenue Maurice Schumann | | 59140 Dunkerque, France ===========================================================================
Sent: Monday, September 19, 2016 at 10:29 PM From: stan stanl-fedorauser@vfemail.net To: users@lists.fedoraproject.org Subject: Re: anacron/cron
On Mon, 19 Sep 2016 22:04:21 +0200 "Patrick Dupre" pdupre@gmx.com wrote:
The point is that I am not sure that mlocate (or updatedb) runs properly because locate does not find my new files !
How can I be sure that mlocate runs properly ?
$ systemctl status mlocate-updatedb.service ● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disabled) Active: inactive (dead) since Mon 2016-09-19 09:14:14 MST; 4h 7min ago Process: 1046 ExecStart=/usr/libexec/mlocate-run-updatedb (code=exited, status=0/SUCCESS) Main PID: 1046 (code=exited, status=0/SUCCESS)
This looks like it runs at start, and that's it. You could try running systemctl restart mlocate-updatedb.service and see if that updates your database.
The man pages for updatedb.conf and updatedb seem to suggest that it is possible to run updatedb from the command line, and to create your own local version of updatedb as a user. _______________________________________________ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-leave@lists.fedoraproject.org
On Mon, 19 Sep 2016 23:19:16 +0200 "Patrick Dupre" pdupre@gmx.com wrote:
OK, Thank.
It was inactive, Then I restart it and now: ● mlocate-updatedb.service - Update a database for mlocate Loaded: loaded (/usr/lib/systemd/system/mlocate-updatedb.service; static; vendor preset: disable Active: active (running) since Mon 2016-09-19 23:15:03 CEST; 1min 17s ago Main PID: 1357 (mlocate-run-upd) Tasks: 2 (limit: 512) CGroup: /system.slice/mlocate-updatedb.service ├─1357 /bin/sh /usr/libexec/mlocate-run-updatedb └─1377 /usr/bin/updatedb -f sysfs ramfs bdev proc cpuset cgroup cgroup2 tmpfs devtmpfs c
Sep 19 23:15:02 teucidide systemd[1]: Stopped Update a database for mlocate. Sep 19 23:15:03 teucidide systemd[1]: Started Update a database for mlocate.
I guess that I need to enable it
No, it's running here from the restart. It's in the process of updating its database.
On Mon, Sep 19, 2016 at 03:15:58PM -0400, Tom Horsley wrote:
On Mon, 19 Sep 2016 20:47:20 +0200 Patrick Dupre wrote:
Sorry, but I do not have /etc/cron.daily/mlocate.cron
This is all part of the systemd fungus experience as it attempts to engulph all of linux.
An rpm -q --list mlocate shows these files on my fedora 24 system:
/usr/lib/systemd/system/mlocate-updatedb.service /usr/lib/systemd/system/mlocate-updatedb.timer
So it is now running on a systemd timer, not in cron (this helps make sure no one has any idea what the heck is going on).
You left out one of the systemd unit files for mlocate:
/var/lib/systemd/timers/stamp-mlocate-updatedb.timer
That might tell you all you need to know. Oh, wait, that's an empty file.
jl
-
Andy Blanchard -
Brian Millett -
Ed Greshko -
Fred -
Joe Zeff -
Jon LaBadie -
Mark C. Allman -
Patrick Dupre -
Rick Stevens -
stan -
Tom Horsley