On 02/19/2013 04:47 AM, Ian Kent wrote:
> All I'm really saying is that, the program map returns a string that is
> then used as the map entry, so when it is parsed the variables $UID,
> $GID, etc. will be present in the macro lookup table as ${UID} (and $UID
> etc. works) ... so maybe these same variables should be provided in the
> environment of the program.
>
> It isn't entirely clear if that is needed since those macro values may
> be returned in the map entry text with things like echo "/some/string
> \ ... ${UID} ..." etc. for later translation.
>
> Really, a revised patch depends on this question being answered first.
For the purpose of accessing the Kerberos ticket cache that I was
dealing with, it isn't necessary to export any further environment.
Unless someone speaks up who needs more detail in environment variables,
I vote for to keeping it simple.
Martin
>
> Ian
>
>
--
Dr. Martin Wilck
PRIMERGY System Software Engineer
x86 Server Engineering
FUJITSU
Fujitsu Technology Solutions GmbH
Heinz-Nixdorf-Ring 1
33106 Paderborn, Germany
Phone: ++49 5251 525 2796
Fax: ++49 5251 525 2820
Email: martin.wilck@xxxxxxxxxxxxxx
Internet: http://ts.fujitsu.com
Company Details: http://ts.fujitsu.com/imprint
--
To unsubscribe from this list: send the line "unsubscribe autofs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
