> True, unless you updated it all in a term window and want to make it
> apply to everything.
Good point; also, in reference to the (apparent) need voiced in the
original question, any tinkering with the PATH that affects daemons
like apache and its spawn will require some other work. But I still
consider rebooting to be a last resort. I love big uptime numbers.
> The only problem I have with sourcing is that it tends to duplicate the
> entire PATH and add it onto the one that already exists.
Though I am happy with the traditional simplicity of the PATH mechanism,
it might be cool to have a more structured tool to manage it. I generally
use a script for my own login environment, and hook it into my shell
session via an alias. But I generally don't try and set that up for the
system.
Such a tool might provide neat features like, for example, checking the
contents of the canonical "system" path and reporting on changes since
the last boot. It could provide a privileged API that packages could use
at install time to extend the PATH appropriately without resulting in a
big redundant PATH.
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list