| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=792677
|
| |
|
|
|
|
| |
We ought to be including this from each .c file.
|
|
|
|
| |
Mostly missing 'static'.
|
|
|
|
|
|
|
|
| |
Avoid initialising all of GVfs for dconf-service in order to monitor a
local file for changes.
See https://bugzilla.gnome.org/show_bug.cgi?id=691618 for the
possibility of a better fix.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
Use fcntl() on a lockfile when accessing a keyfile.
Now reading the keyfile, notifying local processes of changes in it,
applying changes from local request and rewriting it is all done under a
single acquire of the lock. This effectively means that concurrent
changes made to the database across several machines sharing a home
directory over NFS will be seen by all machines as having occurred in
the same order (decided by who won the race to the lock).
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Store the keyfile in ~/.config/dconf/$(name).txt instead of
~/.config/dconf-keyfile/name. Adjust the base writer not to pick up
filenames with dots in them (so we will skip the .txt files the keyfile
writer puts into the same directory).
Add file change monitoring and reload the file if anyone changes it.
Fix a crasher on the first write of a file if it does not yet exist.
Add proper finalize handling.
|
| |
|
|
It is now possible to have keyfile-based dconf databases.
|