> -----Original Message----- > From: sqlite-users-boun...@sqlite.org [mailto:sqlite-users- > boun...@sqlite.org] On Behalf Of Richard Hipp > Sent: 01 September 2014 15:30 > To: General Discussion of SQLite Database > Subject: Re: [sqlite] HELP sqlite3 used in vxworks has some problem > > > Please try the patch at > > > > http://www.sqlite.org/src/info/b0f6b91f36b503d8ba8d5257bb194f8c1afb483 > > > 3 and > > > see if that fixes the problem. > > > > > > > I think that fixes unixDelete. Running on the vxWorks dosFs disk > > everything works as before. > > > > If I use the host filing system, then I think the delete of the > > non-existent file works, but it then fails in unixSync followed by a fail > > in unixDelete > > > > os_unix.c:27830: (35) full_fsync(/tgtsvr/testdb.sql-journal) - (1034) > > > > > Error code 35 is ENOTSUP - fsync is apparently not supported on your > filesystem. >
OK. So it sounds like the answer to Wang Qinggang at the moment is that the host filing system is not supported. I'm slightly surprised fsync isn't supported, but a quick test here proves that it isn't. I will try and raise it with WindRiver and see what they say. It may be a general problem with any network filing system under vxWorks. I'm happy that dosFs works. That's all I need for the time being. Regards Andy Ling _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
