On Wed, 2014-03-05 at 19:06 -0500, Phillip Susi wrote: > Udisks2 added support for setting standby timers and I think some > other drive settings. At the same time, udisksd is a demand start > daemon, that is launched by dbus only when a client tries to use it. > This combination seems to conflict: if no udisks client is run, then > the settings won't be applied. > > Now that I think about it, udisks also does periodic polling of SMART > health, which has the same issue. > > Does it really make sense for udisksd to be demand start?
It will be started by gvfsd-udisks2-volume-monitor when the session starts, so it's not actually a problem. It means it won't slow down I/O during boot. _______________________________________________ devkit-devel mailing list devkit-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/devkit-devel
