[gentoo-amd64] local not started?

[gentoo-amd64] local not started?

[Raffaele BELARDI]

I use the 'local' service to force the ignore_nice_load parameter to 0:

# cat /etc/conf.d/local.start
echo 0 > /sys/devices/system/cpu/cpu0/odemand/ignore_nice_load
(not sure about the path, I am on another pc now)

Recently I noticed that ignore_nice_load is still set to default 1
value, although the 'local' service apparently was started:
# /etc/init.d/local start
* WARNING:  local has already been started.

If I source the local.start from the shell, the value is correctly set.
Any ideas why the the ignore_nice_load is not set to the value I want at
boot?

thanks,

raffaele

Re: [gentoo-amd64] local not started?

[Christoph Mende]

[-- Attachment #1: Type: text/plain, Size: 417 bytes --]

On Thu, 06 Nov 2008 17:37:53 +0100
Raffaele BELARDI <raffaele.belardi@st.com> wrote:

> # /etc/init.d/local start
> * WARNING:  local has already been started.

try /etc/init.d/local restart and look for errors
just note that this will also run /etc/conf.d/local.stop iirc

-- 
Christoph Mende
Gentoo/AMD64 Operational Lead and Release Engineering
GPG: EE2A 454A 6A3B A2D8 E43B  FF45 2A19 C3B3 6DA0 C1AF

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

Re: [gentoo-amd64] local not started?

[Raffaele BELARDI]

Christoph Mende wrote:
> On Thu, 06 Nov 2008 17:37:53 +0100
> Raffaele BELARDI <raffaele.belardi@st.com> wrote:
> 
>> # /etc/init.d/local start
>> * WARNING:  local has already been started.
> 
> try /etc/init.d/local restart and look for errors
> just note that this will also run /etc/conf.d/local.stop iirc
> 

No errors are reported.

raf

Re: [gentoo-amd64] local not started?

[Beso]

2008/11/7 Raffaele BELARDI <raffaele.belardi@st.com>:
> Christoph Mende wrote:
>> On Thu, 06 Nov 2008 17:37:53 +0100
>> Raffaele BELARDI <raffaele.belardi@st.com> wrote:
>>
>>> # /etc/init.d/local start
>>> * WARNING:  local has already been started.
>>
>> try /etc/init.d/local restart and look for errors
>> just note that this will also run /etc/conf.d/local.stop iirc
>>
>
> No errors are reported.
>
> raf


rc-update show. see that you have local in the default profile.

-- 
dott. ing. beso

Re: [gentoo-amd64] local not started?

[Raffaele BELARDI]

Beso wrote:
> 2008/11/7 Raffaele BELARDI <raffaele.belardi@st.com>:
>> Christoph Mende wrote:
>>> On Thu, 06 Nov 2008 17:37:53 +0100
>>> Raffaele BELARDI <raffaele.belardi@st.com> wrote:
>>>
>>>> # /etc/init.d/local start
>>>> * WARNING:  local has already been started.
>>> try /etc/init.d/local restart and look for errors
>>> just note that this will also run /etc/conf.d/local.stop iirc
>>>
>> No errors are reported.
>>
>> raf
> 
> 
> rc-update show. see that you have local in the default profile.
> 

It is in default and nonetwork.

Could it be that the service is executed but some other service
indirectly resets the ignore_nice_load to 1?

raf

Re: [gentoo-amd64] local not started?

[Beso]

2008/11/7 Raffaele BELARDI <raffaele.belardi@st.com>:
> Beso wrote:
>> 2008/11/7 Raffaele BELARDI <raffaele.belardi@st.com>:
>>> Christoph Mende wrote:
>>>> On Thu, 06 Nov 2008 17:37:53 +0100
>>>> Raffaele BELARDI <raffaele.belardi@st.com> wrote:
>>>>
>>>>> # /etc/init.d/local start
>>>>> * WARNING:  local has already been started.
>>>> try /etc/init.d/local restart and look for errors
>>>> just note that this will also run /etc/conf.d/local.stop iirc
>>>>
>>> No errors are reported.
>>>
>>> raf
>>
>>
>> rc-update show. see that you have local in the default profile.
>>
>
> It is in default and nonetwork.
>
> Could it be that the service is executed but some other service
> indirectly resets the ignore_nice_load to 1?
>

try grepping on the files in /etc/init.d/ searching for
ignore_nice_load and see if some other service is doing something
similar.
there should surely be one other service that does something on that:
cpufreqd or something similar depending on the frequency scaler you're
using.

-- 
dott. ing. beso

[gentoo-amd64] Re: local not started?

[Duncan]

Raffaele BELARDI <raffaele.belardi@st.com> posted 49140BC6.2070701@st.com,
excerpted below, on  Fri, 07 Nov 2008 10:35:02 +0100:

> It is in default and nonetwork.
> 
> Could it be that the service is executed but some other service
> indirectly resets the ignore_nice_load to 1?

One easy thing to try, for debugging, is to cat the sys file immediately 
before and after the echo/write.  Of course, you'll want the system set 
so no fancy splash screens (or an immediate boot to X) hide the output, 
but that should really be the default for someone hardcore enough to have 
chosen Gentoo.  I seem to also remember a "quiet-boot" parameter of some 
sort in /etc/rc.conf or /etc/conf.d/rc, that you may need to turn off if 
it interferes with debugging.  However, it's off by default so unless you 
turned it on you should be fine.

You can also try set -x (or -v) before, and set +x (or +v) after.  Those 
tend to be useful debugging tricks on anything bash script based, as the 
initscripts are.

I generally run the newer baselayout/openrc stuff (and am running it now, 
thus I don't remember and can't easily check settings like that quite-
boot option I mentioned), often while it's still somewhat buggy, and have 
traced and filed several bugs using tricks like the above to let me know 
what's going on.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

Re: [gentoo-amd64] Re: local not started?

[Raffaele BELARDI]

Duncan wrote:
> Raffaele BELARDI <raffaele.belardi@st.com> posted 49140BC6.2070701@st.com,
> excerpted below, on  Fri, 07 Nov 2008 10:35:02 +0100:
> 
>> It is in default and nonetwork.
>>
>> Could it be that the service is executed but some other service
>> indirectly resets the ignore_nice_load to 1?
> 
> One easy thing to try, for debugging, is to cat the sys file immediately 
(snip)

> You can also try set -x (or -v) before, and set +x (or +v) after.  Those 
> tend to be useful debugging tricks on anything bash script based, as the 
> initscripts are.
> 

I will try those this evening, thanks. BTW, there is no other service
resetting ignore_nice_load in /etc.

raf

Re: [gentoo-amd64] Re: local not started?

[Raffaele BELARDI]

Duncan wrote:
> One easy thing to try, for debugging, is to cat the sys file immediately 
> before and after the echo/write.  Of course, you'll want the system set 
(snip)
> You can also try set -x (or -v) before, and set +x (or +v) after.  Those 
> tend to be useful debugging tricks on anything bash script based, as the 
> initscripts are.

I tried both, no hints. I also tried to turn off parallel startup, no
change. I give up, I'll try to move the statement to the user startup
script.

raffaele

[gentoo-amd64] Re: local not started?

[Raffaele BELARDI]

Raffaele Belardi wrote:
> I use the 'local' service to force the ignore_nice_load parameter to 0:
> 
> # cat /etc/conf.d/local.start
> echo 0 > /sys/devices/system/cpu/cpu0/odemand/ignore_nice_load
> (not sure about the path, I am on another pc now)
> 
> Recently I noticed that ignore_nice_load is still set to default 1
> value, although the 'local' service apparently was started:
> # /etc/init.d/local start
> * WARNING:  local has already been started.
> 
> If I source the local.start from the shell, the value is correctly set.
> Any ideas why the the ignore_nice_load is not set to the value I want at
> boot?

I found the reason for this behavior: gnome-power-manager was resetting
that parameter, there is one field "consider_nice" under the "cpufreq"
options that overrides the setting defined by 'local' service. Not very
nice way to proceed, in my opinion.

Too bad now I have a similar problem with hdparm service, I set two out
of three disks to standby mode (-S 12) with 'hdparm' service, but as
soon as Gnome starts the setting is ignored or overwritten. I have to
issue again the hdparm command from a root shell to make it effective
within Gnome. I've not yet found which Gnome option could influence this
behavior.

raf