Red Hat Bugzilla – Bug 3765
Problems with initscripts 4.23
Last modified: 2014-03-16 22:09:37 EDT
I get two errors during startup, and I believe I know what's
causing both of them.
Error #1: "/etc/sysconfig/i18n: file not found"
I don't have this file. It's not included in initscripts.
What package has it, and why isn't this package in the
Requires field for initscripts?
Error #2: "tty: file not found"
I think this comes from the line
if [ "`tty`" = "not a tty" ]; then
running in /etc/rc.d/init.d/functions before the /usr
partition has been mounted (tty is in /usr/bin).
I'm bumping this to higher priority because 4.23 also seems to cause
the root partition to not get cleanly unmounted on shutdown, which
could cause fs problems.
First two have been fixed, will be in next rawhide release.
What's the problem with getting the fs unmounted? Are there
earlier errors that shouw up?
The error, as I remember it, said that the partition was "busy."
I'll try and get the exact error later today.
You can go ahead and close this bug report. I can't reproduce this,
so I don't think it's related to initscripts. Probably a process that
wouldn't die or something similar.
I get the problem with the file system on both of my computers
running rawhide, and have been for not only the last couple versions
of initscripts but almost since I started using it. The first has a
custom kernel and is running tons of security programs running and
watching everything all the time, but the other one is a stock
rawhide computer that only has a few non-rawhide packages installed
on it that I use for network troubleshooting, none of which are
daemons. I never complained about this before because I had thought
there was already a bug for this and that someone was working on it
(maybe I am wrong, or maybe noone even looks at the old bugs that
never closed (pity to look at all those forgotten bugs)...). Just
tried rebooting to see if it would happen, and it did, but now >I<
can't even reproduce it (was going to try it again and see if I could
catch some other error that might have happened before it). Am going
to try a few more things though, I have some more ideas on what might
have been running that last reboot that isn't now.