New version is out. And it's always nice to see that Gentoo patches settle upstream (see last item). Please, bump. What is new in this release (3.1.3) ? ------------------------------------- * Fixed compilation on Solaris 10, and fixed fcrondyn authentication without a password on that platform. * Fixed bug where LONG_MAX could potentially be used in functions like localtime(), which is too big for localtime(). This was unlikely to happen unless there was another problem in the first place. * fcrondyn -x no longer adds null characters at the end of the output. This would cause problems if the output was piped to something as grep. Thanks Dimitri Semitsoglou-Tsiapos for pointing this out. * Fixed minor bug in fcronsighup resulting in log errors about closing the signal file * fcrondyn no longer crashes when receiving an EOF when using readline (thanks Wade Carpenter for the patch) * fcrontab no longer crash if mailto is empty (thanks Olaf for reporting the issue) * Fixed SELinux issue with Linux user being used instead of the SELinux user (thanks Sven Vermeulen for the patch)
3.2.0 is now out as well. From version 3.1.3 to 3.2.0 * Print date as %Y-%m-%d (the ISO 8601 date format), to avoid being ambiguous in international context. Also always use the ':' as hour:minute separator (there was a couple of 'h' instead). * Don't fully disable a <at> -line when something goes wrong (e.g. fcron didn't shut down cleanly). The idea was to prevent infinite loops, but this was overkill. Instead set its next execution to now+frequency.` * Cosmetic changes in the log lines (quote the job shell commands) and fcrondyn (use the pipe char "|" as a column separator). * Fixed file descriptor leak when executing jobs in case of NSS failures (thanks Pavel Stano).
Renaming the fcron-3.1.2-r2.ebuild to fcron-3.2.0.ebuild is all that's required. Possibly unrelated, but also fixed a broken cron job for me.
Any news on that? Because of missing 'Fixed SELinux issue with Linux user being used instead of the SELinux user' fcron is unusable in SELinux environment even in permissive mode.
*** Bug 537434 has been marked as a duplicate of this bug. ***
This was fixed by Anthony G. Basile (blueness) on 2016-01-02 via https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cb3636879e1fe4fec5c92fd166a3ab2b43fe3d1e