Send Motion-user mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
[email protected]
You can reach the person managing the list at
[email protected]
When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."
Today's Topics:
1. RPI4 Bullseye and libcamerify (Mathias Koerber)
----------------------------------------------------------------------
Message: 1
Date: Thu, 11 Jan 2024 00:43:55 +0800
From: Mathias Koerber <[email protected]>
To: [email protected]
Subject: [Motion-user] RPI4 Bullseye and libcamerify
Message-ID: <[email protected]>
Content-Type: text/plain; charset=UTF-8; format=flowed
So it seems that we now need libcamerify to start motion for it to use
the Rpi cameras
That seems to work, but I usually run motion as a service
and it seems that motion running as service needs
its systemtl service definition updated
for now I have updated
/usr/lib/systemd/system/motion.service
with this parameter as follows:
ExecStart=libcamerify /usr/bin/motion
I also needed to amend the ownershios for /var/log/motion and
/var/lib/motion:
# chown -R motion:motion /var/og/motion /var/lib/motion
buts is that enough? Am I missing something
that will bite me later?
I thing the distribution should have a means to
handle this out of the box (a future upgrade might
rewrite this unit fie and lose the changes)?
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 209, Issue 9
*******************************************
