Le 07/12/2014 19:54, Anton Aylward a écrit :
On 12/07/2014 01:04 PM, jdd wrote:
I openned an other thread for it
in /etc/crontab, I read:
# 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
the question is why these logs come in now and never did before?
but it's not snapper related.
No, this is the same tread. You obviously weren't paying attention.
please stop being rude, it's of no use
That is the script that runs the /etc/cron.{hourly,daily}/* scripts, which I've already mentioned, in particular the suse.de-snapper.
but these scripts runs conditional that all ends up doing nothing
So yes it is snapper related.
see the answer http://lists.opensuse.org/opensuse/2014-12/msg00362.html "I also saw these annoying logs, but didn't find a working idea how to avoid or suppress this"
Do note, as we've discussed here before, that the cron jobs are actually run 'niced' down in priority and which records the output of the job.
but there is only one cron job running (the one quoted) every 15 minutes. This is a pretty new install, with nothing cronned by me
While I'm being methodological about it, I'll also pint out that there is the shell variable SYSLOG_ON_NO_ERROR. Unless that is set to "yes" then you are not going to see any details about the cron.{hourly,daily} jobs unless they error.
this is a good idea, done
do check that. Be methodical.
I am, it's because I am that I think I can exclude snapper, having verifyed all the files (thanks to your help) I read root mails. The only one is from mdadm script: "ls: cannot access /dev/md?*: No such file or directory" normal, given I have no lvm. thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org