From: Todd C. Miller Date: Thu, 9 Sep 2010 20:22:08 +0000 (-0400) Subject: set_home and always_set_home have an effect if HOME is present in X-Git-Tag: SUDO_1_7_5~167 X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=11c90fbe07fd074b0424df76463a985516f8d757;p=sudo set_home and always_set_home have an effect if HOME is present in the env_keep list. --HG-- branch : 1.7 --- diff --git a/sudoers.pod b/sudoers.pod index 798295ce6..519984e1b 100644 --- a/sudoers.pod +++ b/sudoers.pod @@ -598,7 +598,8 @@ home directory of the target user (which is root unless the B<-u> option is used). This effectively means that the B<-H> option is always implied. Note that C is already set when the the I option is enabled, so I is only -effective for configurations where I is disabled. +effective for configurations where either I is disabled +or C is present in the I list. This flag is I by default. =item authenticate @@ -822,7 +823,8 @@ environment variable will be set to the home directory of the target user (which is root unless the B<-u> option is used). This effectively makes the B<-s> option imply B<-H>. Note that C is already set when the the I option is enabled, so I is -only effective for configurations where I is disabled. +only effective for configurations where either I is disabled +or C is present in the I list. This flag is I by default. =item set_logname