View previous topic :: View next topic |
Author |
Message |
Conditional_Zenith Apprentice
Joined: 22 Sep 2004 Posts: 157 Location: Australia
|
Posted: Fri Oct 14, 2005 11:33 am Post subject: fcron: could not set nice value: Success |
|
|
I am getting lots of log messages saying:
Quote: |
<some-date/time> <hostname> fcron[<somePID>]: could not set nice value: Success
|
These messages always correspond to a message at the same time with the same PID which says "Job <jobname> started for user <username> (pid <some differentPID>)".
These messages about not being able to set the nice value happen almost everytime a job is run, and I can confirm that the jobs are run at nice 0 (they should be running at nice 10).
I can set nice values manually and portage works with is nice variable, and fcron seems to be working fine in all other ways.
Is this a known problem? Have I likely screwed up my config? Is the problem with fcron or somewhere else? |
|
Back to top |
|
|
Jylppy n00b
Joined: 10 May 2004 Posts: 17 Location: Finland
|
Posted: Mon Nov 14, 2005 8:22 pm Post subject: Same problem here |
|
|
Same problem but no idea how to fix it. J |
|
Back to top |
|
|
Conditional_Zenith Apprentice
Joined: 22 Sep 2004 Posts: 157 Location: Australia
|
Posted: Thu Dec 01, 2005 1:17 am Post subject: |
|
|
I got around to looking at it more closely today. It seems that the jobs do run with the correct nice value, it is just that this version of fcron mis-interprets the return value of the nice system call and therefore complains even if nothing is wrong (and ironically, sometimes doesn't complain when things do go wrong). I had a look at fcron-2.9.5.1 (currently ~x86 in portage) and they have fixed the problem there. |
|
Back to top |
|
|
|