Greetings;
I've been trying to help Anne Wilson setup a working amanda system at
her place for over a week now, and having all sorts of troubles that
were triggered by the amanda executables not being in the user amanda's
environmental path when she actually logs in as amanda, as opposed to
On Wed, Apr 05, 2006 at 10:20:59AM -0400, Gene Heskett enlightened us:
When doing it as amanda, with amanda's full $PATH, /usr/local/sbin,
where all of amanda's executables live, is NOT in the $PATH.
Adding it to ~/.bash_profile seems to allow it to survive the
pathmunge'ing being done in
On Wednesday 05 April 2006 11:18, Jon LaBadie wrote:
On Wed, Apr 05, 2006 at 10:20:59AM -0400, Gene Heskett wrote:
Greetings;
I've been trying to help Anne Wilson setup a working amanda system
at her place for over a week now, and having all sorts of troubles
that were triggered by the amanda
Gene Heskett wrote:
On Wednesday 05 April 2006 11:18, Jon LaBadie wrote:
anything/sbin is supposed to contain programs of interest to
systems accounts, not to ordinary users. Thus they would not
be in an ordinary users PATH by default because those users would
not look to execute them.
So
On Wed, Apr 05, 2006 at 02:54:22PM -0500, Frank Smith wrote:
Gene Heskett wrote:
On Wednesday 05 April 2006 11:18, Jon LaBadie wrote:
anything/sbin is supposed to contain programs of interest to
systems accounts, not to ordinary users. Thus they would not
be in an ordinary users PATH by
