Public bug reported:
Currently the dbus upstart script has this:
start on local-filesystems
But this makes the dbus startup fail if /usr is an NFS filesystem.
After changing the above line to:
start on remote-filesystems
dbus started working correctly.
This actually highlights the problem with init events that assume
certain things about the system installation. You really want a "start
on usr-available" here, not on events that naïvely assume what kind of
filesystem it's on.
** Affects: dbus (Ubuntu)
Importance: Undecided
Status: New
** Tags: trusty
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus in Ubuntu.
https://bugs.launchpad.net/bugs/1607024
Title:
needs to wait for remote-filesystems to start
Status in dbus package in Ubuntu:
New
Bug description:
Currently the dbus upstart script has this:
start on local-filesystems
But this makes the dbus startup fail if /usr is an NFS filesystem.
After changing the above line to:
start on remote-filesystems
dbus started working correctly.
This actually highlights the problem with init events that assume
certain things about the system installation. You really want a
"start on usr-available" here, not on events that naïvely assume what
kind of filesystem it's on.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1607024/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
