Keepass database

[ebyrne242]

I tried to use gdrivefs to store a keepass database with keepassx. However, any time the database is saved, gdrivefs (and/or google drive) creates a new file with (number) after it. Every time I save the file, I get a new file created, without the existing file being modified:

$ ls -al
total 112
drwxrwxrwx 2 sketch users 4096 Apr 7 2016 .
drwxrwxrwx 2 sketch users 4096 Jun 4 2014 ..
-rw-rw-rw- 1 sketch users 26286 Oct 25 15:45 keepass.kdbx
-rw-rw-rw- 1 sketch users 26462 Oct 25 16:03 keepass.kdbx (1)
-rw-rw-rw- 1 sketch users 26446 Oct 25 16:18 keepass.kdbx (2)
-rw-rw-rw- 1 sketch users 26462 Oct 25 16:18 keepass.kdbx (3)

When I close keepassx, the .lock file does go away as expected. I can see if I continually run an ls -al while saving, that it appears to create a temporary file:

-rw-rw-rw- 1 sketch users 0 Oct 25 16:21 keepass.kdbx.Ti8097

Then (I assume) the file is renamed and gets the new name:

-rw-rw-rw- 1 sketch users 26446 Oct 25 16:21 keepass.kdbx (4)

I am not sure if it's keepassx or gdrivefs creating the temporary file and then renaming it. I can't see this behavior on any other FUSE filesystems that I've tried.

Let me know if there's anything else I can do to help troubleshoot.

OS is CentOS 7.
gdrivefs==0.14.8
keepassx-2.0.0-1.el7.centos.x86_64

[dsoprea]

It's the application maybe making a decision based on an observation which
may or may not be accurate. If GDFS is at fault, it'll be in what it's
doing or some delay it has that is not being correctly managed by that
project. I'd be happy to help but we need to understand the flow of that
project first. Unless you're really in the mood to do some strace-ing or
otherwise reverse engineering what they got going on, I'd suggest posting
an issue with them to get their opinion and including me.

On Oct 25, 2016 17:27, "sketch242" [email protected] wrote:

I tried to use gdrivefs to store a keepass database with keepassx.
However, any time the database is saved, gdrivefs (and/or google drive)
creates a new file with (number) after it. Every time I save the file, I
get a new file created, without the existing file being modified:

$ ls -al
total 112
drwxrwxrwx 2 sketch users 4096 Apr 7 2016 .
drwxrwxrwx 2 sketch users 4096 Jun 4 2014 ..
-rw-rw-rw- 1 sketch users 26286 Oct 25 15:45 keepass.kdbx
-rw-rw-rw- 1 sketch users 26462 Oct 25 16:03 keepass.kdbx (1)
-rw-rw-rw- 1 sketch users 26446 Oct 25 16:18 keepass.kdbx (2)
-rw-rw-rw- 1 sketch users 26462 Oct 25 16:18 keepass.kdbx (3)

When I close keepassx, the .lock file does go away as expected. I can see
if I continually run an ls -al while saving, that it appears to create a
temporary file:

-rw-rw-rw- 1 sketch users 0 Oct 25 16:21 keepass.kdbx.Ti8097

Then (I assume) the file is renamed and gets the new name:

-rw-rw-rw- 1 sketch users 26446 Oct 25 16:21 keepass.kdbx (4)

I am not sure if it's keepassx or gdrivefs creating the temporary file and
then renaming it. I can't see this behavior on any other FUSE filesystems
that I've tried.

Let me know if there's anything else I can do to help troubleshoot.

OS is CentOS 7.
gdrivefs==0.14.8
keepassx-2.0.0-1.el7.centos.x86_64

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#165, or mute the thread
https://github.com/notifications/unsubscribe-auth/AArrarIL-MDMFjmFc5STZ9JtbP3HJuM5ks5q3nRYgaJpZM4KggXM
.

[ebyrne242]

Looks like someone else has basically the same problem with keepassx using google-drive-ocamlfuse, so it's probably not a gdrivefs issue: https://dev.keepassx.org/issues/449

[Querulous]

I have the same problem and i did simple test.

I created text file on GDriveFS, then I edited it and saved. After this operation I had two files on Google Drive one with original name and without changes and one with appended " (1)" at end of filename and with changes.

This means that is a issue with the file system instead keepass.

On drive.google.com webpage all " (x)" appended to filenames are trimmed. It maybe some mechanism for file history, but something is not implemented on GDriveFS side because webpage and KPGoogleSync extension for Keepass2 is working fine.