Comment 36 for bug 723482

Revision history for this message
Colin Watson (cjwatson) wrote :

Actually, never mind the previous comment - it was obvious once I thought about it the right way. The mounted event is SYNCHRONOUS: anything that says 'start on mounted ...' will block mountall until it comes back, and this is by design (see mounted(7)). Thus the effect of alsa-restore's 'start on runlevel [2345] and (mounted MOUNTPOINT=/usr) and (mounted MOUNTPOINT=/var)' is to deadlock mountall.

Furthermore, the current job specification means that 'alsactl restore' will never be run unless /usr and /var are both separate mountpoints.

The right way to specify this is not '(mounted MOUNTPOINT=/usr) and (mounted MOUNTPOINT=/var)', but simply 'filesystem'. I'll fix this shortly.