View previous topic :: View next topic |
Author |
Message |
triquetra Tux's lil' helper
Joined: 09 Apr 2012 Posts: 93 Location: Kansas, USA
|
Posted: Sat Mar 21, 2015 2:04 am Post subject: [solved] fcron fails to run emerge |
|
|
"cat /var/log/messages | grep cron" shows lots of fcron entries
"cat /var/log/messages | grep system_update" shows entries for my daily update script, but I know it hasn't actually run because, for example, the portage database has not been updated in over a week
I can manually run "/etc/cron.daily/system_update" and it works just fine. Fcron just won't run it, even though the log says it has run. Help!
Last edited by triquetra on Sat May 09, 2015 3:29 pm; edited 2 times in total |
|
Back to top |
|
|
triquetra Tux's lil' helper
Joined: 09 Apr 2012 Posts: 93 Location: Kansas, USA
|
Posted: Mon Mar 30, 2015 3:58 pm Post subject: |
|
|
Does anyone know how to get fcron working properly? |
|
Back to top |
|
|
triquetra Tux's lil' helper
Joined: 09 Apr 2012 Posts: 93 Location: Kansas, USA
|
Posted: Wed Apr 08, 2015 8:01 pm Post subject: |
|
|
Help! |
|
Back to top |
|
|
triquetra Tux's lil' helper
Joined: 09 Apr 2012 Posts: 93 Location: Kansas, USA
|
Posted: Sat May 09, 2015 3:33 pm Post subject: |
|
|
Here's the solution. In summary, my emerge defaults in make.conf included the "--ask" option, which caused emerge to terminate if not run in an interactive shell. I added the "--ask=n" option to the emerge invocation in my fcron script, and that solved the issue. |
|
Back to top |
|
|
|