Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 76619 - freevo needs RTC support in kernel
Summary: freevo needs RTC support in kernel
Status: VERIFIED NEEDINFO
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: New packages (show other bugs)
Hardware: x86 Linux
: High minor (vote)
Assignee: No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-01-04 03:48 UTC by Pasi Sakala
Modified: 2009-03-30 07:09 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pasi Sakala 2005-01-04 03:48:35 UTC
/etc/init.d/freevo -script assumes that kernel does have rtc-module loaded. If it's not loaded script will stop working without any error messages in check-part. Some sort of information to add rtc to kernel would be better than nothing.

Reproducible: Always
Steps to Reproduce:
1. run /etc/init.d/freevo webserver start or any other commands
2.
3.

Actual Results:  
Script didn't start any services-

Expected Results:  
Start services that I requested.
Comment 1 Steve Dibb (RETIRED) gentoo-dev 2006-07-30 21:09:48 UTC
Is this still an issue in the latest version of freevo?
Comment 2 Robert Buchholz (RETIRED) gentoo-dev 2006-09-02 11:41:16 UTC
This(In reply to comment #1)
> Is this still an issue in the latest version of freevo?

Yes, since this is not an issue of freevo, but of the init-script.
As Pasi pointed out, the problem is the file /etc/init.d/freevo (line 19):
sysctl -w dev.rtc.max-user-freq=1024 &> /dev/null

When you do not have RTC compiled into your kernel, the sysctl fails:
# sysctl -w dev.rtc.max-user-freq=1024
error: "dev.rtc.max-user-freq" is an unknown key

I do not know why the script wants to set this value anyway, but freevo *does* work without RTC support (I do this for years) and it is a pretty easy bugfix since (my) sysctl has an option -e to ignore unknown keys. Changing the above line as follows fixes the bug for me:

sysctl -e -w dev.rtc.max-user-freq=1024 &> /dev/null