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. That is the script that runs the /etc/cron.{hourly,daily}/* scripts, which I've already mentioned, in particular the suse.de-snapper. So yes it is snapper related. Its also related to making backups, going out to the network for spamassassin updates, and other things, any of which might, if configured the right way, cause your system to hang while they are working, even if they don't error. 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. 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. So the absence of details on your log reports other than the privilege escalation makes perfect sense. There's also the samell matter of who the result gets sent to. How this works depends on how you have your system setup. If, for example, you read your mail via Thunderbird or Kmail then make sure its set up to read local mail in /var/spool/mail. And make sure that you have Postscript or Exim or Sendmail doing the aliasing properly so system mail, mail to root, gets sent to an account your ARE monitoring. This might have been set up when you did your install, but do check that. Be methodical. -- /"\ \ / ASCII Ribbon Campaign X Against HTML Mail / \ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org