On Mon, 9 Mar 2020 at 23:22, Daniel Polski <dan...@agelektronik.se> wrote:
> Updated to 3.31.1 but my application started spitting out an error when
> opening the database, so I tested some earlier sqlite versions to figure
> out when the problem starts.
> I don't get the message in versions <= 3.30.1.
>
> (from the applications log)
> SQLite Version: 3.31.0
> INFO: Database opened: /tmp/database.sqlite
> WARNING: SQLITE error code: 14 cannot open file at line 36982 of
> [3bfa9cc97d]
> WARNING: SQLITE error code: 14 os_unix.c:36982: (40) openDirectory(/tmp) -
>
errno 40 is ELOOP, "Too many symbolic links encountered". open(2) says:
ELOOP Too many symbolic links were encountered in resolving
pathname, or O_NOFOLLOW was
specified but pathname was a symbolic link.
Is your /tmp/ a symlink? Sqlite seems to use O_NOFOLLOW unconditionally in
openDirectory() since this checkin:
https://www.sqlite.org/src/info/6a64fb6a2da6c98f
Probably a bug? The changelog for sqlite 3.31.0 include this which is
likely related:
- * Add the SQLITE_OPEN_NOFOLLOW
<https://www.sqlite.org/c3ref/open.html#opennofollow> option to
sqlite3_open_v2() <https://www.sqlite.org/c3ref/open.html> that prevents
SQLite from opening symbolic links.
-Rowan
_______________________________________________
sqlite-users mailing list
sqlite-users@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
