I'm back with more read-only issues.
Thanks to postings on this list, I've made progress, but still more issues.
Using the sqlite3 command-line, I'm attempted to open,
read-only, a database located on a Windows 7 workstations, from a Linux server.
I am mounting the Windows volume r/o:
mount //${workstation}/C /mnt/iCal -o ro
I am opening the database read-only, with timeout:
$ sqlite3 -separator '~' -cmd ".timeout 20000"
"file:/mnt/tmp/Users.../calendar-date/local.sqlite?mode=ro"
So, why do I occasionally get these Error messages in my logfile?
2016-04-26 14:32 HPRS_Office_Calendar_Calendar.ics updated
Error: attempt to write a readonly database
Error: attempt to write a readonly database
Error: attempt to write a readonly database
Error: attempt to write a readonly database
Error: attempt to write a readonly database
2016-04-26 14:52 HPRS_Office_Calendar_Calendar.ics updated
First of all, why is it attempting to write anything if it's opened read-only?
Secondly, how could it ever succeed if the entire volume is read-only? Note that
there were no errors on the 1st and last examples. And, the "updated" message
refers to the output of the cron script, not an update to the database.
THX --Mark
