| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The `PartOf` directive sets up a one-way dependency between
`graphical-session.target` and our services, so that when
`graphical-session.target` is stopped or restarted, our services also get
stopped or restarted.
This ensures that gvfs daemons that were started in the context of a GUI
login session (through dbus activation) do not continue to run after the
user has logged out.
See `systemd.unit(5)` for more info.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This puts all gvfs systemd services (which are all dbus-activated through
`SystemdService=`) inside of the `session` slice that was introduced in
v249 (https://github.com/systemd/systemd/pull/16603) and described in
https://systemd.io/DESKTOP_ENVIRONMENTS/ and `systemd.special(7)`
This allows sysadmins or OS integrators to assign higher-priority
`systemd.resource-control(5)` on `session.slice` and have it propagate
down to important session services such as gvfs, so that the gvfs daemons
receive sufficient priority for resource allocations to keep the session
running smoothly under load.
Note that it still works on older systemd
(the slice, which is just a cgroup inner directory, is created on demand)
|
|
|
|
|
|
|
|
| |
When using "systemd --user" in conjunction with "dbus-daemon --session
--systemd-activation", this ensures that each daemon is correctly placed
in its own cgroup, instead of being treated as part of dbus.service.
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=755760
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This naming is mandatory for the system bus, but is also recommended
for the session bus.
The D-Bus maintainers recommend that all activatable session services'
service files are named according to the bus name, so that any conflict
is resolved in a deterministic way. If the services are in different
directories (precedence levels) the result is the same as it is now:
the higher precedence "wins". If the services are in the same
directory, either one overwrites the other and consistently "wins",
or a packaging system like dpkg prevents co-installation.
If the service files were named differently, it would be possible
to have two implementations for the same name. dbus-daemon resolves
this by choosing one arbitrarily, not necessarily the same one every
time. systemd's kdbus support is more strict (or less concerned with
backwards compatibility), and treats this situation as an error.
Bug: https://bugzilla.gnome.org/show_bug.cgi?id=755760
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2007-11-15 Alexander Larsson <alexl@redhat.com>
* daemon/Makefile.am:
* daemon/ftp.mount.in:
* daemon/gvfs-daemon.service.in:
* daemon/sftp.mount.in:
* daemon/smb-browse.mount.in:
* daemon/smb.mount.in:
* daemon/trash.mount.in:
Rename gvfs daemon processes to start
with "gvfsd". This is shorter and nicer.
svn path=/trunk/; revision=1026
|
|
Original git commit by Alexander Larsson <alex@greebo.(none)> at 1170175197 +0100
svn path=/trunk/; revision=290
|