----- Original Message ----- > From: "Sven Kieske" <[email protected]> > To: [email protected] > Sent: Friday, November 29, 2013 12:12:31 PM > Subject: [Users] Bug cron 3.3.1-2 ? > > Hi, > > It seems, the ovirt-cron does something which does not work > out of the box: > > From: Anacron <[email protected]> > To: [email protected] > Content-Type: text/plain; charset="ANSI_X3.4-1968" > Subject: Anacron job 'cron.daily' on management.test > Message-Id: <[email protected]> > Date: Fri, 25 Oct 2013 03:07:02 +0200 (CEST) > > /etc/cron.daily/ovirt-cron: > > ls: cannot access /var/log/ovirt-engine/server.log.*: No such file or > directory > ls: cannot access /var/log/ovirt-engine/jasperserver.log.*: No such file > or directory > ls: cannot access /var/log/ovirt-engine/server.log.*.gz: No such file or > directory > ls: cannot access /var/log/ovirt-engine/jasperserver.log.*.gz: No such > file or directory > > Is this intended behaviour?
No. In 3.3 we removed the proprietary log rotation in favor of standard logrotate. > > ovirt-engine 3.3.1-2 on CentOS 6.4. > > > -- > Mit freundlichen Grüßen / Regards > > Sven Kieske > > Systemadministrator > Mittwald CM Service GmbH & Co. KG > Königsberger Straße 6 > 32339 Espelkamp > T: +49-5772-293-100 > F: +49-5772-293-333 > https://www.mittwald.de > Geschäftsführer: Robert Meyer > St.Nr.: 331/5721/1033, USt-IdNr.: DE814773217, HRA 6640, AG Bad Oeynhausen > Komplementärin: Robert Meyer Verwaltungs GmbH, HRB 13260, AG Bad Oeynhausen > _______________________________________________ > Users mailing list > [email protected] > http://lists.ovirt.org/mailman/listinfo/users > _______________________________________________ Users mailing list [email protected] http://lists.ovirt.org/mailman/listinfo/users
