Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#18586 - [alsa-utils] /etc/conf.d/alsa comment suggests /var/run/alsa-state, should be /var/lib

Attached to Project: Arch Linux
Opened by Isaac Dupree (idupree) - Saturday, 06 March 2010, 22:19 GMT
Last edited by Andrea Scarpino (BaSh) - Monday, 15 November 2010, 17:10 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

According to the Filesystem Hierarchy Standard, /var/run is for data that does not persist between boots. http://www.pathname.com/fhs/pub/fhs-2.3.html#VARRUNRUNTIMEVARIABLEDATA

The entire purpose of alsa-state is to persist between shutdown and booting. It is not a cache (if it disposed, system behavior changes), and it does not need to be edited by the user. I believe /var/lib is the correct location for anyone who wishes to change it from the default, unfortunate /etc/asound.state .

/etc/conf.d/alsa begins:
# Arguments for alsactl
# example: ALSA_ARGS="--file /var/run/alsa-state"
ALSA_ARGS=""

The example line should instead be:
# example: ALSA_ARGS="--file /var/lib/alsa-state"
or perhaps (in order to be consistent with the name of the file in /etc, because we have no reason not to), it should really say:
# example: ALSA_ARGS="--file /var/lib/asound.state"
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Monday, 15 November 2010, 17:10 GMT
Reason for closing:  Fixed
Additional comments about closing:  alsa-utils 1.0.23-3

Loading...