Hi all, Who takes care of cronjob in /etc/cron.d ? Should we tell crond to run it?
/etc/crontab only mentions hourly, daily, weekly, monthly
You can put a crontab file in there. Just don't alter any of the others. Crond automatically runs everything in /etc/cron.d, in /etc/crontab, and in user crontabs.
Cheers,
Cliff
On Thu, Dec 8, 2011 at 8:23 PM, Fajar Priyanto fajarpri@arinet.org wrote:
Hi all, Who takes care of cronjob in /etc/cron.d ? Should we tell crond to run it?
/etc/crontab only mentions hourly, daily, weekly, monthly
-- Thanks Fajar _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Thu, Dec 8, 2011 at 4:27 PM, Cliff Pratt enkiduonthenet@gmail.com wrote:
You can put a crontab file in there. Just don't alter any of the others. Crond automatically runs everything in /etc/cron.d, in /etc/crontab, and in user crontabs.
That's what I thought, but /etc/crontab only mention this: # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly
No /etc/cron.d
From man 8 cron
Cron searches /var/spool/cron for crontab files which are named after accounts ... Cron also searches for /etc/crontab and the files in the directory, which are in a different format (see crontab(5) ).
So cron itself knows about /etc/cron.d and checks it. No need to have an entry in /etc/crontab
Martin Rushton HPC System Manager, Weapons Technologies Tel: 01959 514777, Mobile: 07939 219057 email: jmrushton@QinetiQ.com www.QinetiQ.com QinetiQ - Delivering customer-focused solutions
Please consider the environment before printing this email. -----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Fajar Priyanto Sent: 08 December 2011 08:31 To: CentOS mailing list Subject: Re: [CentOS] /etc/cron.d
On Thu, Dec 8, 2011 at 4:27 PM, Cliff Pratt enkiduonthenet@gmail.com wrote:
You can put a crontab file in there. Just don't alter any of the others. Crond automatically runs everything in /etc/cron.d, in /etc/crontab, and in user crontabs.
That's what I thought, but /etc/crontab only mention this: # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly
No /etc/cron.d _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. QinetiQ may monitor email traffic data and also the content of email for the purposes of security. QinetiQ Limited (Registered in England & Wales: Company Number: 3796233) Registered office: Cody Technology Park, Ively Road, Farnborough, Hampshire, GU14 0LX http://www.qinetiq.com.
It's a good idea NOT to put stuff in /etc/crontab and NOT to change the existing members of /etc/cron.d. It is a good idea NOT to change root's crontab. Any of these may get overwritten by maintenance.
We generally put cron stuff in a locally named and created member in /etc/cron.d.
Cheers,
Cliff
On Thu, Dec 8, 2011 at 11:01 PM, Rushton Martin JMRUSHTON@qinetiq.com wrote:
From man 8 cron
Cron searches /var/spool/cron for crontab files which are named after accounts ... Cron also searches for /etc/crontab and the files in the directory, which are in a different format (see crontab(5) ).
So cron itself knows about /etc/cron.d and checks it. No need to have an entry in /etc/crontab
Martin Rushton HPC System Manager, Weapons Technologies Tel: 01959 514777, Mobile: 07939 219057 email: jmrushton@QinetiQ.com www.QinetiQ.com QinetiQ - Delivering customer-focused solutions
Please consider the environment before printing this email. -----Original Message----- From: centos-bounces@centos.org [mailto:centos-bounces@centos.org] On Behalf Of Fajar Priyanto Sent: 08 December 2011 08:31 To: CentOS mailing list Subject: Re: [CentOS] /etc/cron.d
On Thu, Dec 8, 2011 at 4:27 PM, Cliff Pratt enkiduonthenet@gmail.com wrote:
You can put a crontab file in there. Just don't alter any of the others. Crond automatically runs everything in /etc/cron.d, in /etc/crontab, and in user crontabs.
That's what I thought, but /etc/crontab only mention this: # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly
No /etc/cron.d _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos This email and any attachments to it may be confidential and are intended solely for the use of the individual to whom it is addressed. If you are not the intended recipient of this email, you must neither take any action based upon its contents, nor copy or show it to anyone. Please contact the sender if you believe you have received this email in error. QinetiQ may monitor email traffic data and also the content of email for the purposes of security. QinetiQ Limited (Registered in England & Wales: Company Number: 3796233) Registered office: Cody Technology Park, Ively Road, Farnborough, Hampshire, GU14 0LX http://www.qinetiq.com. _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Am 08.12.2011 21:08, schrieb Cliff Pratt:
It's a good idea NOT to put stuff in /etc/crontab and NOT to change the existing members of /etc/cron.d. It is a good idea NOT to change root's crontab. Any of these may get overwritten by maintenance.
/etc/crontab will NEVER get overwritten to make it clear: NEVER EVER
fedora did not overwrite any crontab from FC5 to F15 now because rpm-packages mark such configurations so the new versions get installed as .rpmnew
On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 21:08, schrieb Cliff Pratt:
It's a good idea NOT to put stuff in /etc/crontab and NOT to change the existing members of /etc/cron.d. It is a good idea NOT to change root's crontab. Any of these may get overwritten by maintenance.
/etc/crontab will NEVER get overwritten to make it clear: NEVER EVER
fedora did not overwrite any crontab from FC5 to F15 now because rpm-packages mark such configurations so the new versions get installed as .rpmnew
Which means the changes those versions would like to have made won't take effect. So it is still best to avoid editing it yourself if you can put your local jobs in one of the other possible places.
Am 08.12.2011 22:04, schrieb Les Mikesell:
On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 21:08, schrieb Cliff Pratt:
It's a good idea NOT to put stuff in /etc/crontab and NOT to change the existing members of /etc/cron.d. It is a good idea NOT to change root's crontab. Any of these may get overwritten by maintenance.
/etc/crontab will NEVER get overwritten to make it clear: NEVER EVER
fedora did not overwrite any crontab from FC5 to F15 now because rpm-packages mark such configurations so the new versions get installed as .rpmnew
Which means the changes those versions would like to have made won't take effect. So it is still best to avoid editing it yourself if you can put your local jobs in one of the other possible places.
which means updates do not randomly change configurations and this is good so since it is your job as admin to look if the rpmnew contains anything which is interesting for you and if not let your working configuration in peace
On Thu, Dec 8, 2011 at 3:07 PM, Reindl Harald h.reindl@thelounge.net wrote:
fedora did not overwrite any crontab from FC5 to F15 now because rpm-packages mark such configurations so the new versions get installed as .rpmnew
Which means the changes those versions would like to have made won't take effect. So it is still best to avoid editing it yourself if you can put your local jobs in one of the other possible places.
which means updates do not randomly change configurations and this is good so since it is your job as admin to look if the rpmnew contains anything which is interesting for you and if not let your working configuration in peace
But you've done an even better job as an admin if you don't mess with rpm managed files in the first place, and the packagers have done a better job if they abstract out all the things that are likely to need local changes - like the stuff generally under /etc/sysconfig to make that possible.
On Fri, Dec 9, 2011 at 10:07 AM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 22:04, schrieb Les Mikesell:
On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 21:08, schrieb Cliff Pratt:
It's a good idea NOT to put stuff in /etc/crontab and NOT to change the existing members of /etc/cron.d. It is a good idea NOT to change root's crontab. Any of these may get overwritten by maintenance.
/etc/crontab will NEVER get overwritten to make it clear: NEVER EVER
fedora did not overwrite any crontab from FC5 to F15 now because rpm-packages mark such configurations so the new versions get installed as .rpmnew
Which means the changes those versions would like to have made won't take effect. So it is still best to avoid editing it yourself if you can put your local jobs in one of the other possible places.
which means updates do not randomly change configurations and this is good so since it is your job as admin to look if the rpmnew contains anything which is interesting for you and if not let your working configuration in peace
There should be no need to look at the .rpmnew files if you have done your job as admin properly.
Cheers,
Cliff
Am 09.12.2011 00:53, schrieb Cliff Pratt:
On Fri, Dec 9, 2011 at 10:07 AM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 22:04, schrieb Les Mikesell:
On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 21:08, schrieb Cliff Pratt:
It's a good idea NOT to put stuff in /etc/crontab and NOT to change the existing members of /etc/cron.d. It is a good idea NOT to change root's crontab. Any of these may get overwritten by maintenance.
/etc/crontab will NEVER get overwritten to make it clear: NEVER EVER
fedora did not overwrite any crontab from FC5 to F15 now because rpm-packages mark such configurations so the new versions get installed as .rpmnew
Which means the changes those versions would like to have made won't take effect. So it is still best to avoid editing it yourself if you can put your local jobs in one of the other possible places.
which means updates do not randomly change configurations and this is good so since it is your job as admin to look if the rpmnew contains anything which is interesting for you and if not let your working configuration in peace
There should be no need to look at the .rpmnew files if you have done your job as admin properly.
why are radnom people try to tell me how i have to do my job without knowing anyting about how i work?
no there is no need on the production machine becuase all preparing happens on a dedicated environment with where local and caching repos and build-environment is available and from where all TESTED updates are deployed
i do my job properly in making sure that no dumb change of any upstream maintainer is touching a configuration of relevant services
so what will you tell me after > 200 ONLINE-dist-upgrades in the last view years on all sort of servers?
On Fri, Dec 9, 2011 at 1:03 PM, Reindl Harald h.reindl@thelounge.net wrote:
Am 09.12.2011 00:53, schrieb Cliff Pratt:
On Fri, Dec 9, 2011 at 10:07 AM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 22:04, schrieb Les Mikesell:
On Thu, Dec 8, 2011 at 2:25 PM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 21:08, schrieb Cliff Pratt:
It's a good idea NOT to put stuff in /etc/crontab and NOT to change the existing members of /etc/cron.d. It is a good idea NOT to change root's crontab. Any of these may get overwritten by maintenance.
/etc/crontab will NEVER get overwritten to make it clear: NEVER EVER
fedora did not overwrite any crontab from FC5 to F15 now because rpm-packages mark such configurations so the new versions get installed as .rpmnew
Which means the changes those versions would like to have made won't take effect. So it is still best to avoid editing it yourself if you can put your local jobs in one of the other possible places.
which means updates do not randomly change configurations and this is good so since it is your job as admin to look if the rpmnew contains anything which is interesting for you and if not let your working configuration in peace
There should be no need to look at the .rpmnew files if you have done your job as admin properly.
why are radnom people try to tell me how i have to do my job without knowing anyting about how i work?
Touchy.
no there is no need on the production machine becuase all preparing happens on a dedicated environment with where local and caching repos and build-environment is available and from where all TESTED updates are deployed
Good for you.
i do my job properly in making sure that no dumb change of any upstream maintainer is touching a configuration of relevant services
Good.
so what will you tell me after > 200 ONLINE-dist-upgrades in the last view years on all sort of servers?
I'd say that I been in the business for a long long time and I can still learn from other people.
Cheers,
Cliff
Am 09.12.2011 01:03, schrieb Reindl Harald:
why are radnom people try to tell me how i have to do my job without knowing anyting about how i work?
no there is no need on the production machine becuase all preparing happens on a dedicated environment with where local and caching repos and build-environment is available and from where all TESTED updates are deployed
i do my job properly in making sure that no dumb change of any upstream maintainer is touching a configuration of relevant services
so what will you tell me after > 200 ONLINE-dist-upgrades in the last view years on all sort of servers?
Harald,
please stop acting like this. The way you are contributing on this list is pretty harsh, even abusive.
Why do you rant against Cliff he would tell you how you would have to do your job? It was exactly you starting with that kind of dictation when replying to Les. So please be fair and reflect your own behaviour.
And please, do not play the game about others being fools and only you know how all things should go. A healthy self-assurance is fine, but talking about "dumb [...] upstream maintainer" combined with your statements about your experience makes you look like a person, not many people like to deal with.
I do not like to get personal. It is just meant as a hint that you should care about the way you interact on this list.
Regards
Alexander
Am 09.12.2011 09:59, schrieb Alexander Dalloz:
Am 09.12.2011 01:03, schrieb Reindl Harald:
why are radnom people try to tell me how i have to do my job without knowing anyting about how i work?
no there is no need on the production machine becuase all preparing happens on a dedicated environment with where local and caching repos and build-environment is available and from where all TESTED updates are deployed
i do my job properly in making sure that no dumb change of any upstream maintainer is touching a configuration of relevant services
so what will you tell me after > 200 ONLINE-dist-upgrades in the last view years on all sort of servers?
Harald,
Why do you rant against Cliff he would tell you how you would have to do your job? It was exactly you starting with that kind of dictation when replying to Les. So please be fair and reflect your own behaviour.
my only point was "/etc/crontab will NEVER get overwritten" because he gave bad advise that it would randomly
no idea why everytime random peopole make a major-topic after a simple correction and starting advise what why are not getting changed with updates because you touch a config-file which gets no longer overwritten with new maintainer versions
that is why config-files exists and that is why the are flagged not to be overwritten - so what do we discuss here?
On Dec 9, 2011, at 1:59 AM, Alexander Dalloz wrote:
Am 09.12.2011 01:03, schrieb Reindl Harald:
why are radnom people try to tell me how i have to do my job without knowing anyting about how i work?
no there is no need on the production machine becuase all preparing happens on a dedicated environment with where local and caching repos and build-environment is available and from where all TESTED updates are deployed
i do my job properly in making sure that no dumb change of any upstream maintainer is touching a configuration of relevant services
so what will you tell me after > 200 ONLINE-dist-upgrades in the last view years on all sort of servers?
Harald,
please stop acting like this. The way you are contributing on this list is pretty harsh, even abusive.
Why do you rant against Cliff he would tell you how you would have to do your job? It was exactly you starting with that kind of dictation when replying to Les. So please be fair and reflect your own behaviour.
And please, do not play the game about others being fools and only you know how all things should go. A healthy self-assurance is fine, but talking about "dumb [...] upstream maintainer" combined with your statements about your experience makes you look like a person, not many people like to deal with.
I do not like to get personal. It is just meant as a hint that you should care about the way you interact on this list.
---- not just this list - his abusiveness is so over the top that I have specifically asked him never to respond to my posts on fedora-list
Craig
On Fri, Dec 9, 2011 at 9:25 AM, Reindl Harald h.reindl@thelounge.net wrote:
Am 08.12.2011 21:08, schrieb Cliff Pratt:
It's a good idea NOT to put stuff in /etc/crontab and NOT to change the existing members of /etc/cron.d. It is a good idea NOT to change root's crontab. Any of these may get overwritten by maintenance.
/etc/crontab will NEVER get overwritten to make it clear: NEVER EVER
fedora did not overwrite any crontab from FC5 to F15 now because rpm-packages mark such configurations so the new versions get installed as .rpmnew
Fair enough.
Cheers,
Cliff
Am 08.12.2011 09:30, schrieb Fajar Priyanto:
On Thu, Dec 8, 2011 at 4:27 PM, Cliff Pratt enkiduonthenet@gmail.com wrote:
You can put a crontab file in there. Just don't alter any of the others. Crond automatically runs everything in /etc/cron.d, in /etc/crontab, and in user crontabs.
That's what I thought, but /etc/crontab only mention this: # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly
No /etc/cron.d
jesus christ crond does not need a hint in the crontab to know that he has to enumerate /etc/cron.d
the same all other software working with /etc/anything.d/ does not need to ne configured to do that
On Thu, 8 Dec 2011, Reindl Harald wrote:
jesus christ crond does not need a hint in the crontab to know that he has to enumerate /etc/cron.d
If you're in a bad mood, don't take it out on people on the list.
the same all other software working with /etc/anything.d/ does not need to ne configured to do that
This isn't true in the slightest. In fact, I think on balance more tools have it configured than have it hard coded.
xinetd.conf: includedir /etc/xinetd.d httpd.conf: Include conf.d/*.conf ld.so.conf: include ld.so.conf.d/*.conf logrotate.conf: include /etc/logrotate.d oddjobd.conf: <include ignore_missing="yes">/etc/oddjobd.conf.d/*.conf</include> prelink.conf: -c /etc/prelink.conf.d/*.conf profile.conf: for i in /etc/profile.d/*.sh ; do
If you're going to act like an all knowing authority, be one.
jh
On Fri, Dec 09, 2011 at 10:38:08AM +0000, John Hodrien wrote:
If you're going to act like an all knowing authority, be one.
Perhaps not feeding the troll would also help?
John
Am 09.12.2011 11:42, schrieb John R. Dennison:
On Fri, Dec 09, 2011 at 10:38:08AM +0000, John Hodrien wrote:
If you're going to act like an all knowing authority, be one.
Perhaps not feeding the troll would also help?
all people have not your opinion are trolls? laughable attitude!
On Fri, Dec 09, 2011 at 11:44:26AM +0100, Reindl Harald wrote:
all people have not your opinion are trolls? laughable attitude!
Not at all. Only those that have a penchant for needing to have the last word in, no matter if they are right or wrong. Your behavior on other mailing lists is quite well documented and I'm hoping that behavior doesn't carry over to this one.
Can we please stop the needless bickering?
John
On Thu, Dec 8, 2011 at 9:30 PM, Fajar Priyanto fajarpri@arinet.org wrote:
On Thu, Dec 8, 2011 at 4:27 PM, Cliff Pratt enkiduonthenet@gmail.com wrote:
You can put a crontab file in there. Just don't alter any of the others. Crond automatically runs everything in /etc/cron.d, in /etc/crontab, and in user crontabs.
That's what I thought, but /etc/crontab only mention this: # run-parts 01 * * * * root run-parts /etc/cron.hourly 02 4 * * * root run-parts /etc/cron.daily 22 4 * * 0 root run-parts /etc/cron.weekly 42 4 1 * * root run-parts /etc/cron.monthly
No /etc/cron.d
That's because crond already knows to look at /etc/crontab, /etc/cron.d and user cron tabs. It's hard coded.
Cheers,
Cliff
-
Alexander Dalloz -
Cliff Pratt -
Craig White -
Fajar Priyanto -
John Hodrien -
John R. Dennison -
Les Mikesell -
Reindl Harald -
Rushton Martin