[opensuse] why is /etc/crontab almost empty on one of my 11.0 (clean install) systems?
salam, just realized, that crontab is almost empty on one of my clean x86 11.0 systems (all current onlineupdates applied). affected system looks like: SHELL=/bin/sh PATH=/usr/bin:/usr/sbin:/sbin:/bin:/usr/lib/news/bin MAILTO=root # # check scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly # -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1 on some other system i dont have this problem. there are several cron.daily, hourly, monthly and weekly or something lines. who and when do these lines get created, and how can i get them created? also grep for crontab in /var/log/messages only displays lines when cron gets started or restarted. Mar 16 11:29:52 linux /usr/sbin/cron[3479]: (CRON) STARTUP (V5.0) the other system displays all those starts of hourly, daily, weekly and monthly. greetings. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, Mar 26, 2009 at 01:04:11PM +0100, cagsm wrote:
salam,
just realized, that crontab is almost empty on one of my clean x86 11.0 systems (all current onlineupdates applied).
affected system looks like:
SHELL=/bin/sh PATH=/usr/bin:/usr/sbin:/sbin:/bin:/usr/lib/news/bin MAILTO=root # # check scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly # -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1
on some other system i dont have this problem. there are several cron.daily, hourly, monthly and weekly or something lines. who and when do these lines get created, and how can i get them created?
also grep for crontab in /var/log/messages only displays lines when cron gets started or restarted. Mar 16 11:29:52 linux /usr/sbin/cron[3479]: (CRON) STARTUP (V5.0)
the other system displays all those starts of hourly, daily, weekly and monthly.
Well, look at the other crontab entries: $ ls /etc/cron.* /etc/cron.d: novell.com-suse_register seccheck smolt # variable tabs /etc/cron.daily: logrotate suse.de-backup-rc.config suse.de-check-battery suse.de-cron-local suse.de-update-preload suse-texlive suse-clean_catman suse.de-backup-rpmdb suse.de-clean-tmp suse.de-updatedb suse-do_mandb # daily jobs /etc/cron.hourly: # hourly jobs /etc/cron.monthly: # monthly jobs /etc/cron.weekly: # weekly jobs Ciao, Marcus -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, on 03/26/2009 02:31 PM Marcus Meissner wrote:
On Thu, Mar 26, 2009 at 01:04:11PM +0100, cagsm wrote:
salam,
just realized, that crontab is almost empty on one of my clean x86 11.0 systems (all current onlineupdates applied). [...]
Well, look at the other crontab entries: $ ls /etc/cron.*
And then look at the script the only entry in /etc/crontab starts. It tries to be clever about when to best call the stuff in the directories Marcus showed you :) Henne -- Henne Vogelsang, openSUSE. Everybody has a plan, until they get hit. - Mike Tyson -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
cagsm wrote:
salam,
just realized, that crontab is almost empty on one of my clean x86 11.0 systems (all current onlineupdates applied).
affected system looks like:
SHELL=/bin/sh PATH=/usr/bin:/usr/sbin:/sbin:/bin:/usr/lib/news/bin MAILTO=root # # check scripts in cron.hourly, cron.daily, cron.weekly, and cron.monthly # -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1
on some other system i dont have this problem. there are several cron.daily, hourly, monthly and weekly or something lines. who and when do these lines get created, and how can i get them created?
also grep for crontab in /var/log/messages only displays lines when cron gets started or restarted. Mar 16 11:29:52 linux /usr/sbin/cron[3479]: (CRON) STARTUP (V5.0)
the other system displays all those starts of hourly, daily, weekly and monthly.
greetings.
Did you even look at what above even does? What does run-crons do? What does the "-" at the beginning of a crontab line mean to this version of cron? The answers to all your questions are found within the answers to these two. Also, this is not exactly new. Looking around, even my old 10.0 boxes have that same setup. That's at least 6 releases. Though by another reckoning it's only been about 3 1/2 years since oct 2005 which could be called "recent" in all contexts except computers. -- bkw -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
so why is there one system of 11.0 that looks differently from the other clean installed one? also, why dont i see all those daily, monthly, weekly et. al. entries in /var/log/messages that they are being executed on this machine with "empty" crontab? your reasoning cant possibly be true, or where do i fail to understand cron stuff in opensuse? both machines have plenty of opensuse default entries in the cron.daily directory for example. the one machine writes lines about their execution into messages, the other one doesnt. and i doubt that this other machine actually does anything thats in those cron directories. all my logs etc and that basic stuff never got logrotated so far on that machine as an example. thats one of the dailies i think. there has to be some bug here? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday, 2009-03-27 at 10:35 +0100, cagsm wrote:
so why is there one system of 11.0 that looks differently from the other clean installed one?
also, why dont i see all those daily, monthly, weekly et. al. entries in /var/log/messages that they are being executed on this machine with "empty" crontab? your reasoning cant possibly be true, or where do i fail to understand cron stuff in opensuse?
The /etc/crontab in 11.x should have only one active line: - -*/15 * * * * root test -x /usr/lib/cron/run-crons && /usr/lib/cron/run-crons >/dev/null 2>&1 The "-" in front means that it is not logged, which is different from executing. However, you can edit in "/etc/sysconfig/cron" this line: SYSLOG_ON_NO_ERROR="yes" which will produce an entry when each individual cron "task" is executed: Mar 26 22:20:43 nimrodel run-crons[17605]: suse-texlive: OK Mar 26 22:20:45 nimrodel run-crons[17605]: suse.de-backup-rc.config: OK Mar 26 22:21:10 nimrodel run-crons[17605]: suse.de-backup-rpmdb: OK Mar 26 22:21:10 nimrodel run-crons[17605]: suse.de-check-battery: OK Mar 26 22:21:17 nimrodel run-crons[17605]: suse.de-clean-tmp: OK If you have crontabs with more _active_ lines, those machines are incorrect. Or not 11.x, or not properly upgraded, or somebody else has done it.
both machines have plenty of opensuse default entries in the cron.daily directory for example. the one machine writes lines about their execution into messages, the other one doesnt. and i doubt that this other machine actually does anything thats in those cron directories.
all my logs etc and that basic stuff never got logrotated so far on that machine as an example. thats one of the dailies i think. there has to be some bug here?
- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.9 (GNU/Linux) iEYEARECAAYFAknMsiUACgkQtTMYHG2NR9VHJQCggwjWzy9T8zf+H3PqCvSfDSMP +vcAnjj+IqLF3fWiGlHtpgjSZSw+0RKG =0s45 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Brian K. White -
cagsm -
Carlos E. R. -
Henne Vogelsang -
Marcus Meissner