Hi, Gene,

on Donnerstag, 16. September 2004 at 22:14 you wrote to amanda-users:

GH> amanda@coyote amanda-2.4.5b1-20040915]$ amgetconf Daily
GH> could not open conf file 
GH> "/home/amanda/amanda-2.4.5b1-20040915/amanda.conf": No such file or
GH> directory
GH> amgetconf: errors processing config file 
GH> "/home/amanda/amanda-2.4.5b1-20040915/amanda.conf"
GH> [amanda@coyote amanda-2.4.5b1-20040915]$                     

GH> Anyone have any ideas why its stuck looking for a file that doesn't
GH> exist unless I copy it to there?

GH> And...  If I copy it there, then I get this:
GH> ------------
GH> [amanda@coyote amanda-2.4.5b1-20040915]$ 
GH> cp /usr/local/etc/amanda/Daily/amanda.conf .
GH> [amanda@coyote amanda-2.4.5b1-20040915]$ amgetconf Daily
GH> amgetconf: no such parameter "Daily"
GH> BUGGY
GH> ------------
GH> I think its right, its BUGGY...  :-)

Usage: amgetconf [config] <parmname>

So if you want to know the value of autoflush for config Daily, it's:

amgetconf Daily autoflush

Although this gives me an error with 2.4.4p3-20040915 AND 2.4.4p3
here ...:-(

Seems as if only numerical values are read correctly ...
Another thing added to the big TODO-list ...


manpage:

> amgetconf: no such parameter "param"
>               Parameter param is not a known keyword (e.g. not  a
>               valid  amanda.conf  keyword).  In this case, amget­
>               conf will write "BUGGY" to stdout as the value.

---

GH> The last time I actually looked at that autoflush code, at least a
GH> year ago, it appeared that just the presence of the keyword was all
GH> it took to set that variable, but the docs then said it was yes or
GH> no.  So its presently set for 

GH> autoflush yes

Works for me.

-- 
best regards,
Stefan

Stefan G. Weichinger
mailto:monitor AT oops.co DOT at