Latest upstream release: 10.3.1 Current version/release in Fedora Rawhide: 10.2.1-1.fc21 URL: http://sebastien.godard.pagesperso-orange.fr/download.html Please consult the package updates policy before you issue an update to a stable branch: https://fedoraproject.org/wiki/Updates_Policy More information about the service that created this bug can be found at: https://fedoraproject.org/wiki/Upstream_release_monitoring
In Rawhide, please drop cronjobs and use upstream timer units.
(In reply to Upstream Release Monitoring from comment #0) > Latest upstream release: 10.3.1 info from upstream: Sysstat 10.3.1 released (development version). I had to switch back to a development version because of a change of sar's datafiles format. But this is (really) for a good cause... After a period of hard work, this version of sysstat includes a long awaited feature: sar can now take into account a change of CPU count in its datafiles. On virtual machine, after CPU change (e.g. power off machine -> add 1 CPU -> power on machine), you will no longer lose data (from today) from the current saXX file. The restart mark (this is the LINUX RESTART message inserted when sadc is called without any parameters) will be used by sar to know that CPU count has changed. Note that I plan to go back to a stable series for next sysstat version (which will be 11.0.0).
(In reply to Tomasz Torcz from comment #1) > In Rawhide, please drop cronjobs and use upstream timer units. No this timer unit should be dropped... For component to be applicable for timer migration it's simple really . Is it part of the bootup process ( yes ) ( no ) Is it dependent or part of something that is depended on the bootup process ( yes ) ( no ) Does that component already depend on systemd ( yes ) ( no ) If the answer is yes in any it will be looked at for migration to see to what extend and if and only if it brings any benefit migrating it. if the answer is no in all then that component that contains a cron job is not applicable for systemd timer migration. Removing dependency on cron-to-time migration feature and I'll ask the maintainer to drop the timer unit or do what needs to be done if that's not the case and add an hard dependency on systemd for a component that has absolutely nothing to do with initramfs/init/udev/daemon/service etc.
sysstat already depends on systemd
If that's the case I have to apologise for my hastiness and I've added it to the correct blocker bug. I'm being extremely conservative of what get's migrated so we dont wind up getting unwanted dependency's on the init system for the future. It's been hard enough overseeing the systemd integration and initsystem replacement with gazillion components just assuming the initsystem and other core/baseOS components exist when they are being installed indefinitely as well as other components dependending on components I did put on ice migrating the legacy sysv init script at the time due to the fact that /etc/sysconfig/foo files will be or atleast should be dropped hence that script that the initscript was just calling needed to be rewritten but since it already depends on systemd that means someone migrated that initscript to a service unit and or has been fully integrated sysstat to journal already and is collecting the statistics from there. In anycase for each daemon/service that is started on bootup regardless if it's via the traditional method as in via "enable" or via hardware/udev rule the cron job being migrated to timer unit should be bound to that service unit so when you stop the service and or disable it the timer units will be stopped as well. If the service units sole existence is to start collecting at boot ( making it Type=oneshot unit ) it arguable should be migrated to timer unit instead and that timer unit triggered via OnBootSec=, OnStartupSec=.
fixed in: sysstat-10.3.1-1.fc21 http://koji.fedoraproject.org/koji/buildinfo?buildID=519558 Sysstat was migrated to the systemd timer units. Bug for enabling these timer units by default is bug #1101621