diff options
| author | Ondrej Holy <oholy@redhat.com> | 2018-10-11 17:47:59 +0200 |
|---|---|---|
| committer | Ondrej Holy <oholy@redhat.com> | 2018-11-19 13:34:47 +0100 |
| commit | 396216f71abf6907efd1383ca0d1a597918cd83d (patch) | |
| tree | 1dfd738c1163b08b63ce2fa5ad244d8eb845c543 /monitor | |
| parent | a23eb6f14eb3cffa1585d4e5e566f779337d1e04 (diff) | |
| download | gvfs-396216f71abf6907efd1383ca0d1a597918cd83d.tar.gz | |
daemon: Prevent spawning new daemons if outgoing operation exists
A new daemon is always spawned if MountLocation method (or LookupMount for
automounted) is called and the respective mount isn't registered yet. This
is not usually an issue, because the redundant daemons are consequently
terminated. However, this is a problem if mount operations hang for some reason.
This may happen e.g. with trash backend due to stale NFS mounts. Consequently,
new and new daemons are spawned which may lead to system failures due to lack
of system resources. See the following downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1632960
Let's fix that behavior simply by preventing spawning of new daemons if
respective outgoing mount operations exist.
https://gitlab.gnome.org/GNOME/gvfs/merge_requests/19
Diffstat (limited to 'monitor')
0 files changed, 0 insertions, 0 deletions