tag:blogger.com,1999:blog-1539046083268926117.post2283976792602911075..comments2010-08-18T10:31:00.771-07:00Mike Greenlyhttps://profiles.google.com/118145172612811800326noreply@blogger.comBlogger3125tag:blogger.com,1999:blog-1539046083268926117.post-75349832828468701722010-08-18T10:31:00.771-07:002010-08-18T10:31:00.771-07:00Helpful, thanks.Tomnoreply@blogger.comtag:blogger.com,1999:blog-1539046083268926117.post-53509894994126738892009-04-24T07:17:00.000-07:002009-04-24T07:17:00.000-07:00gregf: Thanks. I knew it was possible to fix by making changes in /etc/sudoers but hadn't taken the time to figure out how until you gave me this hint.<br /><br />On the other hand even after figuring it out I'm staying with my approach. Mostly because I prefer to limit the scope of configuration file changes to my /HOME directory when possible.<br /><br />It seems to make distribution upgrades less painful.Mike Greenlyhttp://www.blogger.com/profile/15964361079720234778noreply@blogger.comtag:blogger.com,1999:blog-1539046083268926117.post-20626320093495683832009-04-24T06:58:00.000-07:002009-04-24T06:58:00.000-07:00Instead of passing the path through you could just use -E. <br /><br />-E The -E (preserve environment) option will override the env_reset option in sudoers(5)). It is only available when either the matching command has the SETENV tag or the setenv option is set in sudoers(5).<br /><br />And as this mentions you could just use setenv in your /etc/sudoers file.gregfhttp://netzdamon.myopenid.com/noreply@blogger.com