Searched refs:policies (Results 1 – 7 of 7) sorted by relevance
270 strv_free(link->policies); in link_free()948 _cleanup_strv_free_ char **policies = NULL, **alt_policies = NULL; in parse_cmdline_ifname_policy() local989 r = strv_consume(&policies, TAKE_PTR(word)); in parse_cmdline_ifname_policy()994 if (strv_isempty(policies)) in parse_cmdline_ifname_policy()1001 link->policies = TAKE_PTR(policies); in parse_cmdline_ifname_policy()1213 if (!strv_isempty(link->policies)) { in link_dump()1215 fputstrv(f, link->policies, " ", NULL); in link_dump()
91 char **policies; member
32 # allocates its own scope unit. Make sure to keep these policies in sync if you
27 With systemd 197 we have added native support for a number of different naming policies into system…
17 2. Stricter default security policies, i.e. sand-boxing of applications.
102 this way we can implement disk encryption policies that bind to specific119 policies (e.g. the string like "4+7+9") so that it can also include explicit
802 updates the SHA1 banks. In such a case PCR policies will be804 policies reliable, but of course do not provide the same level of891 --security-policy= switch for configuring security policies to895 analysis and enforcement of security policies on unit files.1962 instead of a single one, to configure multiple wake-on-LAN policies.3195 * PID 1 may now automatically load pre-compiled AppArmor policies from9101 policies, that make decisions depending on these parameters.11372 for enforced policies is now in place. (Note that enabling12935 * In addition to the SELinux and IMA policies we will now also12936 load SMACK policies at early boot.[all …]