search for: integrity_check

...to use flock() around the SQLite3 db connection open/update/close to protect it. However, that is not enough - although from testing, it looks like flock() works as advertised across gluster mounted files, sync/fsync don't appear to, so we end up getting corruption in the SQLite3 file (pragma integrity_check generally will show a bunch of problems after a short test). Is what we're trying to do achievable? We're testing using the docker container gluster/gluster-centos as the three servers, with a php test inside of php-cli using filesystem mounts. If we mount the gluster FS via sapk/plugin-gl...

...he SQLite3 db connection open/update/close to protect it. > > However, that is not enough - although from testing, it looks like > flock() works as advertised across gluster mounted files, sync/fsync > don't appear to, so we end up getting corruption in the SQLite3 file > (pragma integrity_check generally will show a bunch of problems after > a short test). > > Is what we're trying to do achievable? We're testing using the docker > container gluster/gluster-centos as the three servers, with a php test > inside of php-cli using filesystem mounts. If we mount the glust...

...tion open/update/close to protect it. >> >> However, that is not enough - although from testing, it looks like >> flock() works as advertised across gluster mounted files, sync/fsync >> don't appear to, so we end up getting corruption in the SQLite3 file >> (pragma integrity_check generally will show a bunch of problems after >> a short test). >> >> Is what we're trying to do achievable? We're testing using the docker >> container gluster/gluster-centos as the three servers, with a php test >> inside of php-cli using filesystem mounts. I...

...protect it. > >> > >> However, that is not enough - although from testing, it looks like > >> flock() works as advertised across gluster mounted files, sync/fsync > >> don't appear to, so we end up getting corruption in the SQLite3 file > >> (pragma integrity_check generally will show a bunch of problems after > >> a short test). > >> > >> Is what we're trying to do achievable? We're testing using the docker > >> container gluster/gluster-centos as the three servers, with a php test > >> inside of php-cli u...

...; >> >> >> However, that is not enough - although from testing, it looks like >> >> flock() works as advertised across gluster mounted files, sync/fsync >> >> don't appear to, so we end up getting corruption in the SQLite3 file >> >> (pragma integrity_check generally will show a bunch of problems after >> >> a short test). >> >> >> >> Is what we're trying to do achievable? We're testing using the docker >> >> container gluster/gluster-centos as the three servers, with a php test >> >>...

...rom http://wald.intevation.org/projects/gpg4win/ : gpg4win-1.0.3.tar.bz2 (3.9M) gpg4win-1.0.3.tar.bz2.sig The second file is a digital signature of the the first file. Either check that this signature is fine or compare with the checksums given below. (see also http://www.gnupg.org/download/integrity_check.html) The *ready to use installer* is available at: http://ftp.gpg4win.org/gpg4win-1.0.3.exe (6.2M) http://ftp.gpg4win.org/gpg4win-1.0.3.exe.sig Or using the ftp protocol at: ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.0.3.exe (6.2M) ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.0.3.exe.sig SH...

...> >> However, that is not enough - although from testing, it looks like > >> >> flock() works as advertised across gluster mounted files, sync/fsync > >> >> don't appear to, so we end up getting corruption in the SQLite3 file > >> >> (pragma integrity_check generally will show a bunch of problems after > >> >> a short test). > >> >> > >> >> Is what we're trying to do achievable? We're testing using the docker > >> >> container gluster/gluster-centos as the three servers, with a php &g...

...rom http://wald.intevation.org/projects/gpg4win/ : gpg4win-1.0.4.tar.bz2 (3.9M) gpg4win-1.0.4.tar.bz2.sig The second file is a digital signature of the the first file. Either check that this signature is fine or compare with the checksums given below. (see also http://www.gnupg.org/download/integrity_check.html) The *ready to use installer* is available at: http://ftp.gpg4win.org/gpg4win-1.0.4.exe (6.3M) http://ftp.gpg4win.org/gpg4win-1.0.4.exe.sig Or using the ftp protocol at: ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.0.4.exe (6.3M) ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.0.4.exe.sig SH...

...; However, that is not enough - although from testing, it looks like >> >> >> flock() works as advertised across gluster mounted files, sync/fsync >> >> >> don't appear to, so we end up getting corruption in the SQLite3 file >> >> >> (pragma integrity_check generally will show a bunch of problems >> after >> >> >> a short test). >> >> >> >> >> >> Is what we're trying to do achievable? We're testing using the >> docker >> >> >> container gluster/gluster-centos a...

...rom http://wald.intevation.org/projects/gpg4win/ : gpg4win-1.1.4.tar.bz2 (4.3M) gpg4win-1.1.4.tar.bz2.sig The second file is a digital signature of the the first file. Either check that this signature is fine or compare with the checksums given below. (see also http://www.gnupg.org/download/integrity_check.html) The *ready to use installer* is available at: http://ftp.gpg4win.org/gpg4win-1.1.4.exe (9.6M) http://ftp.gpg4win.org/gpg4win-1.1.4.exe.sig Or using the ftp protocol at: ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.1.4.exe (9.6M) ftp://ftp.gpg4win.org/gpg4win/gpg4win-1.1.4.exe.sig SH...