Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 25 Jan 2017 21:25:55 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 216466] Incorrect rc.d startup script for package "motion"
Message-ID:  <bug-216466-13@https.bugs.freebsd.org/bugzilla/>

next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216466

            Bug ID: 216466
           Summary: Incorrect rc.d startup script for package "motion"
           Product: Ports & Packages
           Version: Latest
          Hardware: amd64
                OS: Any
            Status: New
          Severity: Affects Only Me
          Priority: ---
         Component: Individual Port(s)
          Assignee: freebsd-ports-bugs@FreeBSD.org
          Reporter: bakhur@inbox.ru

Good day.
FreeBSD 11.0-Release-p1
motion-4.0.1_1

The "motion" daemon didn't use the config file "/usr/local/etc/motion.conf"
after default package installation.
If you set motion_enable=3D"YES", "motion" uses default settings, and OS fa=
iled
to boot if there is no /dev/bktr0 device in the system, because "motion"
permanently trying to get access to /dev/bktr0.
You have to add: command_args=3D"-c /usr/local/etc/motion.conf" in rc.d sta=
rtup
script to fix this error.
Also there is no possibilities to compile "motion" from ports without using
BKTR or PWCBSD capture drivers. You get an error message about wrong config.
But it would be necessary for using "motion" only with network cameras.

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-216466-13>