definition of "filesystem" signal is uselessly overbroad (don't include /srv)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mountall (Ubuntu) |
Fix Released
|
High
|
Scott James Remnant (Canonical) | ||
Karmic |
Fix Released
|
High
|
Scott James Remnant (Canonical) |
Bug Description
Binary package hint: mountall
The "filesystem" signal which blocks the start of rc-sysinit processing and the gdm service is way overbroad in its definition. Yes, /home and /srv are directories that are defined in the FHS, but there's no reason that we should be blocking on these before starting sysvinit processing, because services are not supposed to be relying on anything in these directories for their overall operation. Users *may* have configured services to point at /srv, but they may also have configured services to point at any number of other non-FHS directories not covered by this signal.
In the specific case of /srv, blocking on it before starting gdm/rc-sysinit causes a dependency loop if /srv is a remote filesystem and the network interface is, e.g., a wireless interface managed via network-manager with user-session-
ProblemType: Bug
Architecture: amd64
Date: Sat Oct 10 13:34:04 2009
DistroRelease: Ubuntu 9.10
Package: mountall 0.2.1
ProcEnviron:
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: mountall
Uname: Linux 2.6.31-13-generic x86_64
summary: |
- definition of "filesystem" signal is uselessly overbroad + definition of "filesystem" signal is uselessly overbroad (don't include + /sys) |
summary: |
definition of "filesystem" signal is uselessly overbroad (don't include - /sys) + /srv) |
Changed in mountall (Ubuntu Karmic): | |
status: | Triaged → Fix Committed |
Agree