Would the rc support module loading? In other words, a sysadmin might want
to give access to certain Perl modules to his/her users, and not to other
users. That's the only use I can think of for dynamic Perl config. BTW,
it's not something I'm against, I'm just trying to find a way I could use
it.
Greg Rollins
Sys Admin
Communication Associates Inc.
----- Original Message -----
From: "Uri Guttman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Friday, September 01, 2000 6:42 PM
Subject: Re: RFC 114 (v2) Perl resource configuration
> >>>>> "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. it
> needs to be separate from the env vars the user might want to set.
>
> TC> Heck, I bet you could do a cleverness with .perldb, too. :-)
>
> i don't want to go there.
>
> uri
>
> --
> Uri Guttman --------- [EMAIL PROTECTED] ----------
http://www.sysarch.com
> SYStems ARCHitecture, Software Engineering, Perl, Internet, UNIX
Consulting
> The Perl Books Page -----------
http://www.sysarch.com/cgi-bin/perl_books
> The Best Search Engine on the Net ----------
http://www.northernlight.com
>
