Hi, You are right. For the next version fix this. Thank you for your suggestion.
Andrew M. Bishop wrote: > The severity of this bug should be important or higher and it should > be re-opened. The answer given to the previous bug report is > unacceptable. > > > I also see this problem, but it is worse because I have V4L devices > installed but I don't want to use them with motion. The default > configuration file /etc/motion/motion.conf contains the lines: > > # Start in daemon (background) mode and release terminal (default: off) > daemon off > > > When upgrading motion it found my TV capture cards and started motion > using them. This stopped the 'apt-get upgrade' process from > completing. I had to Control-C, edit the /etc/init.d/motion file and > then re-run 'apt-get upgrade' to finish configuring the package. > > This means that booting the machine will start motion running but it > won't background itself (I think this means that the boot will hang at > this point). > > The default should not be to start motion at boot time unless the > file /etc/default/motion specifies that it should be started (see > other packages that do this, e.g. spamassassin or rsync). It should > also not be started if the default configuration file does not contain > the line 'daemon on' since this will hang the startup. > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
