Bug 453246 – =sys-process/fcron-3.1.1 : stable request

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Francisco Blas Izquierdo Riera (RETIRED) 2013-01-20 21:36:10 UTC]

3.0.6-r5 fixes bug 332901 whilst 3.1.0 fixes bug 375287. Aside with 3.1.1 two more fixes are reported:
"fixed fcrontab edition of *ly lines (hourly, daily, etc)"
"fixed fcron crashes when noticenotrun was triggered"

Can we please get =sys-process/fcron-3.1.1 stabilized to get rid of those once and forever?

I asked Diego on it and he told me he was fine with stabilizing the latest version, though you may want to check that as of this writing it only is 2 weeks old.

Reproducible: Always

[Comment 1 Francisco Blas Izquierdo Riera (RETIRED) 2013-01-20 21:42:01 UTC]

*** Bug 414191 has been marked as a duplicate of this bug. ***

[Comment 2 Agostino Sarubbo 2013-01-24 22:09:10 UTC]

amd64 stable

[Comment 3 Agostino Sarubbo 2013-01-24 22:11:20 UTC]

x86 stable

[Comment 4 Agostino Sarubbo 2013-01-26 11:55:05 UTC]

ppc stable

[Comment 5 Rick Farina (Zero_Chaos) 2013-01-26 17:24:49 UTC]

USE=system-crontab has been emailing me this every ten minutes since the update:

/bin/sh: /usr/sbin/check_system_crontabs: No such file or directory
Job /usr/sbin/check_system_crontabs -s 0 terminated (exit status: 127) (mailing output)

Think we can get that fixed?

[Comment 6 Diego Elio Pettenò (RETIRED) 2013-01-26 17:29:00 UTC]

did you `emerge --config fcron` ?

[Comment 7 Rick Farina (Zero_Chaos) 2013-01-26 17:42:53 UTC]

(In reply to comment #6)
> did you `emerge --config fcron` ?

I tried to:

Nu fcron # emerge --config fcron


Configuring pkg...

 * We're not going to make any change to your systab as long as
 * it contains data; please clear it before proceeding.

[Comment 8 Paolo Pedroni 2013-01-28 13:52:40 UTC]

(In reply to comment #7)
> (In reply to comment #6)
> > did you `emerge --config fcron` ?
> 
> I tried to:
> 
> Nu fcron # emerge --config fcron
> 
> 
> Configuring pkg...
> 
>  * We're not going to make any change to your systab as long as
>  * it contains data; please clear it before proceeding.

This bit me as well.

Old versions of fcron have check-system-crontab in </usr/sbin/>, while newer ones have it in </usr/libexec/>.

Even if you do "dispatch-conf" or "etc-update" and restart fcron with rc-service or calling /etc/init.d/fcron directly, the old instance is never stopped and the new one does not start, despite the program telling you so.

You have to kill the old instance with 'sudo killall fcron' and then restarting the new one with 'sudo rc-server fcron restart'.

[Comment 9 Agostino Sarubbo 2013-01-29 11:37:39 UTC]

ia64 stable

[Comment 10 jens w 2013-01-30 05:19:28 UTC]

please make a change notice of the new file /etc/crontab, 've wondered that the daily loop is running 2 times

[Comment 11 jens w 2013-01-31 01:26:20 UTC]

one hint would be good, if the new system-crontab used,
the use of fcrontab -systab do not read /etc/crontab.
the message of portage is not clear.

[Comment 12 Agostino Sarubbo 2013-02-03 19:41:38 UTC]

arm stable

[Comment 13 Agostino Sarubbo 2013-02-06 19:49:37 UTC]

sparc stable

[Comment 14 Jeroen Roovers (RETIRED) 2013-02-08 14:54:05 UTC]

Stable for HPPA.

[Comment 15 Pacho Ramos 2013-08-07 12:54:29 UTC]

looks like all was done