Lines Matching refs:this

37    in this context.)
40    mount some suitable TTY to `/dev/console`. If this is a pty, make sure to
75    (this only applies to cgroupv1, of course), to protect the controllers from
76    alteration from inside the containers. Or to turn this around: only the
99    implementation. With this in place the `ConditionVirtualization=` setting in
111    `/etc/machine-id` (if writable) when this option is used, hence you should
125    Note that this variable should not include the pty that `/dev/console` maps
131    running the container manager, if this is considered desirable, please parse
145    'ramfs'), and the absolute path to this directory exported in the
147    does this, the credentials passed to the service manager can be propagated
170    `SIGRTMIN+3` like this, this might confuse other init systems.
196    make use of this functionality. (Also see information about
222 container). Note that this hierarchy is used by various container managers, and
229    bind`. Container payload should usually not directly interact with this
231    it only, and is mostly an internal vehicle to achieve this. Other container
242    `InaccessiblePath=` setting of unit files, i.e. file nodes to mask this way
244    node type does not change this way but the nodes still become
248    character and block devices nodes (there are fallbacks for this case).
252    container manager when boot-up is complete. The path used for this doesn't
254    variable, following the usual protocol for this, however it's suitable, and
255    recommended place for this socket in case ready notification is desired.
264    should be newline terminated. Passing this information via this file has the
279    version of `/dev/`. To set this up systemd in the container needs this
280    capability. If you take away the capability, then all services that set this
353 First things first, to make this clear: Linux containers are not a security
386 own. Note though that this file is only accessible to root. systemd hence early