On Wed, May 03, 2000 at 09:45:53PM +1000, Anthony Towns wrote:
> [...]
> However, changing /etc/proxies *would* be a much easier way of doing
> this, and it would probably be the only real way of getting it to work
> if some of the places I want to connect to use proxies and others don't.
> It would also require much less effort on a user's part to get their
> system to Just Work (tm) if these scripts were included in netbase,
> or similar.
>
> So I think /etc/proxies would actually have a practical improvement.
>
> OTOH, http_proxy (and optionally {ftp,gopher,wais,no,*}_proxy too)
> should go into policy anyway, I suspect.
Also, if the sysadmin wants to change the proxies, but the user has
needed things like http_proxy=... in their .profile (or wherever),
it's going to be a pain. I can think of multiple places where one
would need proxies: in the config files of things like the CPAN.pm
module, in wget configuration (perhaps called from a cron job) and so
on. So a system-wide config file would be _very_ good.
Julian
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Julian Gilbey, Dept of Maths, QMW, Univ. of London. [EMAIL PROTECTED]
Debian GNU/Linux Developer, see http://www.debian.org/~jdg
Donate free food to the world's hungry: see http://www.thehungersite.com/
