Home
last modified time | relevance | path

Searched refs:mapped (Results 1 – 12 of 12) sorted by relevance

/systemd-251/src/journal/
Djournald-audit.c263 bool mapped = false; in map_all_fields() local
316 mapped = true; in map_all_fields()
322 if (!mapped) { in map_all_fields()
/systemd-251/src/libsystemd/sd-bus/
Dbus-kernel.h19 size_t mapped; member
Dbus-kernel.c46 … close_and_munmap(b->memfd_cache[i].fd, b->memfd_cache[i].address, b->memfd_cache[i].mapped); in bus_flush_memfd()
Dbus-message.h40 size_t mapped; member
Dbus-message.c52 close_and_munmap(part->memfd, part->mmap_begin, part->mapped); in message_free_part()
56 munmap(part->mmap_begin, part->mapped); in message_free_part()
3033 part->mapped = psz; in bus_body_part_map()
3054 assert_se(munmap(part->mmap_begin, part->mapped) == 0); in bus_body_part_unmap()
3058 part->mapped = 0; in bus_body_part_unmap()
/systemd-251/test/test-network/conf/
D25-ipv6-address-label-section.network27 # IPv4 mapped prefix
/systemd-251/docs/sysvinit/
DREADME.in18 system. An init script {{ SYSTEM_SYSVINIT_PATH }}/foobar is implicitly mapped
/systemd-251/catalog/
Dsystemd.catalog.in83 The process had more memory mapped than the configured maximum for processing
468 mapped to a unit. In this case systemd will refrain from synthesizing a unit
486 operating systems is to be the owner of files that otherwise cannot be mapped
490 otherwise be mapped.
/systemd-251/docs/
DJOURNAL_EXPORT_FORMATS.md133 …cannot embed binary data natively. Each byte of the binary field will be mapped to its numeric val…
DUIDS-GIDS.md246 level of UID mapped mounts, at *runtime*) or at a base UID from the container
267 | 60514…60577 | Host users mapped into containers | `systemd` | `systemd-nspawn` …
DJOURNAL_FILE_FORMAT.md78 * The format is designed to be read and written via memory mapping using multiple mapped windows.
/systemd-251/
DNEWS168 file systems support it). So far it mapped three UID ranges: the
171 is mapped almost fully, with the exception of the UID subrange used
185 that this mapping is mapped 1:1 in a pass-through fashion, i.e. the
186 UID assignments from the range are not managed or mapped by
1049 the host's file ownerships are mapped 1:1 to container file
1241 * systemd-homed now makes use of UID mapped mounts for the home areas.
1244 for indicating "this ownership is not mapped"), and dynamically
1245 mapped to the UID used locally on the system via the UID mapping
1808 mapped to the host UID 0, and the UID 1 to host UID 1. On first look
1833 UID mapped mounts do not exist; or your container actually needs
[all …]