This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 163784 - /etc/sysctl.conf not read during boot
/etc/sysctl.conf not read during boot
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: initscripts (Show other bugs)
4
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2005-07-20 21:14 EDT by Andrew Kroeger
Modified: 2014-03-16 22:55 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2005-09-12 15:38:52 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrew Kroeger 2005-07-20 21:14:49 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.7.8) Gecko/20050513 Fedora/1.0.4-1.3.1 Firefox/1.0.4

Description of problem:
Added a value for kernel.printk in /etc/sysctl.conf.  Value is not loaded during boot (via /etc/rc.d/init.d/network) but can be successfully loaded after boot using sysctl.

Version-Release number of selected component (if applicable):
selinux-policy-targeted-1.25.2-4

How reproducible:
Always

Steps to Reproduce:
1. Set a custom value for kernel.printk in /etc/sysctl.conf
2. Reboot
3. Verify value not set using cat /proc/sys/kernel/printk
4. Verify valid entry in /etc/sysctl.conf using sysctl -e -p /etc/sysctl.conf
5. Verify value is set using cat /proc/sys/kernel/printk

Additional info:

Did not find any related entries in /var/log/audit/audit.log.  Upon further checking found auditd does not start until after network.  Given that auditd only logs to a local file, is there any reason it should not be started before all else in runlevel 2?
Comment 1 Daniel Walsh 2005-07-21 11:00:43 EDT
Why did you assign this to SELinux policy?  Shouldn't it be a initscripts
problem?  Are you seeing SELinux failures on the console?
Comment 2 Steve Grubb 2005-08-25 16:16:42 EDT
/var/log/audit may not be a local directory. I start it at the first opportunity
that its safe to do so. Also, chkconfig does not allow you to specify the start
order in a level by level way. If kernel cannot log to auditd, the message will
go to syslog. So, there is a safety net.

If you turn off SE Linux & reboot, does the parameter get loaded? Or maybe you
can do setenforce 0, service network restart, and then check for it. This avoids
needing to relabel the file system.

If not, this looks like initscript problem. Not audit or policy.
Comment 3 Steve Grubb 2005-09-10 12:12:31 EDT
Transferring to initscripts this is not an audit problem.
Comment 4 Bill Nottingham 2005-09-12 15:38:52 EDT
The value that's exported through kernel.printk is reset by syslogd/klogd, which
runs after network is started.

Note You need to log in before you can comment on or make changes to this bug.