>On Fri, Sep 01, 2000 at 07:42:32PM -0400, Uri Guttman wrote:
>> >>>>> "TC" == Tom Christiansen <[EMAIL PROTECTED]> writes:
>> >> i think an environment var might be a good way. if it is set, it is the
>> >> file(s) to preload before running your code.
>>
>> TC> You've got PERL5OPT.
>>
>> but that is the user's to set. PERL_PRELOAD allows the admin to globally
>> set (in the system shell rc file) the rc files that perl will load.
>Like any other environment variable which the admin wants to be
>everywhere, put it in /etc/profile. A well configured system will
>handle it from there.
Not all shells -- nor shell invocations -- attend to that file.
A shell is ``privileged'' if the -p option is used or if the real user ID
or group ID does not match the effective user ID or group ID (see getu-
id(2) and getgid(2)). A privileged shell does not process $HOME/.profile
nor the ENV parameter (see below). Instead, the file /etc/suid_profile is
processed. Clearing the privileged option causes the shell to set its ef-
fective user ID (group ID) to its real user ID (group ID).
If the basename of the name the shell is called with (i.e., argv[0])
starts with `-' or if the -l option is used, the shell is assumed to be a
login shell and the shell reads and executes the contents of /etc/profile
and $HOME/.profile if they exist and are readable.
This is clearly for login shells only; that is, interactive work.
Which is what .perldb does. :-)
But still, I'm not clear on what to do with it.
--tom
