Hi Leo,
I did not like adding autofs either, although it is explainable - the file
systems may be local, remote or auto.
Meanwhile I continued messing with init scripts, a common approach for
non-vital daemons is to set
# Should-Start: $all
Thus update-rc.d puts it to the end of the list of known up to the moment.
`autofs' allows to keep unused drives unmounted, thus suspends/wakeups do
not need to spin them up. It also safer for filesystems in a case the host
gets disconnected while asleep. Transmission daemon and autofs seem to
naturally belong to a homesite NAS.
On Thu, Nov 21, 2013 at 6:49 PM, Leo Antunes <cost...@debian.org> wrote:
> Hi
>
> On 21/11/13 18:41, Alexander Kuznetsov wrote:
> > the defaults chosen by dh_installinit is inappropriate for
> transmission-daemon. The .postinst contains
> > a line `update-rc.d transmission-daemon defaults', which results in
> creation
> > /etc/rc2.d/S01transmission-daemon
> The ordering is done automatically by insserv and transmission-daemon's
> init script already requires $remote_fs precisely for that reason.
> Unfortunately it seems autofs isn't considered part of $remote_fs.
> I wouldn't rule out fixing this on transmission-daemon's side, but it
> would require adding an explicit mention of autofs (i.e.: Should-Start:
> autofs), which doesn't sound that elegant.
> Another option which seems better at first glance would be adding autofs
> as an optional service to $remote_fs, i.e. adding the changing the
> appropriate line in /etc/insserv.conf to include +autofs.
> You can do this manually as a stopgap measure (just remember to call
> update-rc.d afterwards).
>
> Cheers
>
> --
> Leo "costela" Antunes
> [insert a witty retort here]
>
>
--
Sincerely yours, Alexander Kuznetsov
