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