Home
last modified time | relevance | path

Searched refs:own (Results 1 – 25 of 74) sorted by relevance

123

/systemd-251/src/nspawn/
Dnspawn-cgroup.c549 static int mount_systemd_cgroup_writable_one(const char *root, const char *own) { in mount_systemd_cgroup_writable_one() argument
553 assert(own); in mount_systemd_cgroup_writable_one()
556 r = mount_nofollow_verbose(LOG_ERR, own, own, NULL, MS_BIND, NULL); in mount_systemd_cgroup_writable_one()
570 const char *root, *own; in mount_systemd_cgroup_writable() local
586 own = strjoina(root, own_cgroup_path); in mount_systemd_cgroup_writable()
592 own = strjoina(root, own_cgroup_path); in mount_systemd_cgroup_writable()
594 r = mount_systemd_cgroup_writable_one(root, own); in mount_systemd_cgroup_writable()
600 own = strjoina(root, own_cgroup_path); in mount_systemd_cgroup_writable()
603 return mount_systemd_cgroup_writable_one(root, own); in mount_systemd_cgroup_writable()
/systemd-251/src/resolve/
Dresolved-resolv-conf.c25 struct stat st, own; in manager_check_resolv_conf() local
43 if (stat(PRIVATE_STATIC_RESOLV_CONF, &own) >= 0 && in manager_check_resolv_conf()
44 stat_inode_same(&st, &own)) in manager_check_resolv_conf()
60 struct stat own; in file_is_our_own() local
63 if (stat(path, &own) >= 0 && in file_is_our_own()
64 stat_inode_same(st, &own)) in file_is_our_own()
Dorg.freedesktop.resolve1.conf17 <allow own="org.freedesktop.resolve1"/>
/systemd-251/src/systemd/
Dsd-event.h137 int sd_event_source_set_io_fd_own(sd_event_source *s, int own);
151 int sd_event_source_set_child_pidfd_own(sd_event_source *s, int own);
153 int sd_event_source_set_child_process_own(sd_event_source *s, int own);
/systemd-251/docs/
DCGROUP_DELEGATION.md58 different processes managing them. However, only a single process should own a
95 various controllers each get their own cgroup file system mounted to
96 `/sys/fs/cgroup/<controller>/`. On top of that systemd manages its own cgroup
146 they might contain a sub-tree of their own managed by something else, made
186 its own below that.
226 hierarchy (in unified and hybrid mode) as well as on systemd's own private
249 both systemd and your own manager would create/delete cgroups below the slice
252 So, if you want to do your own raw cgroups kernel level access, then allocate a
317 2. �� The *i-like-islands* option. If all you care about is your own cgroup tree,
340 service's unit file and you are done and have your own sub-tree. In fact, #2 is
[all …]
DDISTRO_PORTING.md58 If you prefer to use leap second steps, please register your own
84 instead install your own.
DPREDICTABLE_INTERFACE_NAMES.md18 …hemes that udev generally uses for these symlinks, and instead invents its own enumeration schemes.
65 … You create your own manual naming scheme, for example by naming your interfaces `internet0`, `dmz…
DRANDOM_SEEDS.md146 Since most of systemd's own use of random numbers do not require
261 3. In general, systemd's own reliance on the kernel entropy pool is minimal
334 something the kernel could much better do on its own. Hence, if what these
350 on using it, as we'd have to maintain that on our own, and we don't want to
351 maintain our own cryptographic primitives if we don't have to. Since
369 instead of kernel doing that on its own?*
371 That's a good question. Ideally the kernel would do that on its own, and we
DBOOT_LOADER_SPECIFICATION.md49 loader in their own partition headers. In this new scheme as all
52 collisions and can install/remove their own boot menu entries at free will,
166 implement this specification might install their own boot code into the `$BOOT`
170 directory. Implementations that add their own files or directories to the file
306 read from other partitions/disks the boot loader can do this in its own native
307 configuration, using its own specific device path language, and this is out of
362 additional items from other configuration files (for example its own native
DCONVERTING_TO_HOMED.md27 own risk, read up beforehand, and make a backup first. You know what's at
28 stake: your own home directory, i.e. all your personal data.
/systemd-251/src/oom/
Dorg.freedesktop.oom1.conf10 <allow own="org.freedesktop.oom1"/>
/systemd-251/src/network/
Dorg.freedesktop.network1.conf17 <allow own="org.freedesktop.network1"/>
/systemd-251/rules.d/
D90-vconsole.rules.in10 # Each vtcon keeps its own state of fonts.
/systemd-251/src/timedate/
Dorg.freedesktop.timedate1.conf19 <allow own="org.freedesktop.timedate1"/>
/systemd-251/src/hostname/
Dorg.freedesktop.hostname1.conf19 <allow own="org.freedesktop.hostname1"/>
/systemd-251/src/locale/
Dorg.freedesktop.locale1.conf19 <allow own="org.freedesktop.locale1"/>
/systemd-251/src/timesync/
Dorg.freedesktop.timesync1.conf17 <allow own="org.freedesktop.timesync1"/>
/systemd-251/src/import/
Dorg.freedesktop.import1.conf19 <allow own="org.freedesktop.import1"/>
/systemd-251/src/portable/
Dorg.freedesktop.portable1.conf10 <allow own="org.freedesktop.portable1"/>
/systemd-251/test/
Dmkosi.default.networkd-test80 # Run our own script
/systemd-251/src/home/
Dorg.freedesktop.home1.conf10 <allow own="org.freedesktop.home1"/>
/systemd-251/units/
Dsystem-update-cleanup.service29 # reboot or some other action on its own.
Dsystemd-nspawn@.service.in32 # allocates its own scope unit. Make sure to keep these policies in sync if you
/systemd-251/catalog/
Dsystemd.sr.catalog.in3 # Message catalog for systemd's own messages
Dsystemd.zh_CN.catalog.in5 # Message catalog for systemd's own messages

123