Bug 120826 - incorrect aumix rc file used by halt initscript
incorrect aumix rc file used by halt initscript
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: initscripts (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
  Show dependency treegraph
Reported: 2004-04-14 05:03 EDT by Landon Curt Noll
Modified: 2014-03-16 22:44 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-04-14 15:57:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Landon Curt Noll 2004-04-14 05:03:07 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3.1; Linux; X11; , en_US.UTF-8, en_US, en)

Description of problem:
The /etc/rc.d/init.d/halt saves the mixer settings in the
wrong file.  The system wide aumix config file is
/etc/aumixrc, not /etc/.aumixrc.  (see man aumix(1)).

People who use the aumix command end up not getting the
aumix rc setting saved by the halt initscript.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.man aumix
2.grep aumixrc /etc/rc.d/init.d

Actual Results:  The man page shows that the system wide default for aumix is
/etc/aumixrc but /etc/rc.d/init.d/halt uses /etc/.aumixrc.

Expected Results:  /etc/rc.d/init.d/halt saves the current settings in the
system wide /etc/aumixrc file.

Additional info:

As jmd moted in bug #78785, the halt init command saves
the init script makes use of an uncustomary dot file in /etc.
I agree with his point as well.

Also note that the post-install for the sound-slot-0 should
also use /etc/aumixrc as well.  I.e., the /etc/modules.conf line
should be:

    post-install sound-slot-0 /bin/aumix-minimal -f /etc/aumixrc -L >/dev/null 2>&1 || :

Also has bug #78783 been fixed in RHEL3?
Comment 1 Bill Nottingham 2004-04-14 15:57:23 EDT
This probably won't be changed, as it's a flag day and breaks users
existing configurations.

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