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. Question about sqlite3 and locking / read-only mode
(Chris Clemson)
----------------------------------------------------------------------
Message: 1
Date: Mon, 24 Apr 2023 20:05:45 +0100
From: Chris Clemson <[email protected]>
To: [email protected]
Subject: [Motion-user] Question about sqlite3 and locking / read-only
mode
Message-ID: <[email protected]>
Content-Type: text/plain; charset="utf-8"; Format="flowed"
Hi Everyone,
I am using motion with 5 cameras and an sqlite database.
I am trying to use PHP to create an interface for it, which is partially
working, but quite often the DB goes into "read-only" mode, even though
I can manipulate the database from the sqlite3 command in a bash shell.
I did notice that I get the following messages on start up:
dbse_init_sqlite3: Setting busy timeout to 0 msec
Could this be the problem? How can I change the timeout to a couple of seconds
or something?
My setup is too simple to warrant a whole mysql (or similar) setup, and I want
as fewer dependencies as possible.
If I stop motion (and/or apache) and start it again, that usually fixes the
problem, but it's difficult to tell when this happens, unless I write some sort
of log parser, which seems a bit of a kludge.
Thanks,
Chris
-------------- next part --------------
An HTML attachment was scrubbed...
------------------------------
------------------------------
Subject: Digest Footer
_______________________________________________
Motion-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/motion-user
------------------------------
End of Motion-user Digest, Vol 200, Issue 11
********************************************
