Jean-Louis Martineau wrote:
The autoflush option in 2.4.4 and before does not flush today's dump
because the dump of the current run can overwrite the file in the
holding disk.
True, and that explains why it did work before: because those dumps
were from the day before, and last week, I tried it on
Hi Paul,
The autoflush option in 2.4.4 and before does not flush today's dump
because the dump of the current run can overwrite the file in the
holding disk.
This problem is fixed in amanda-2.4.5b1 snapshot because holding disk
use timestamped directory instead of datestamped directory.
Jean-Lou
On Friday 17 September 2004 08:01, Stefan G. Weichinger wrote:
>Hi, Gene,
>
>on Donnerstag, 16. September 2004 at 22:14 you wrote to
> amanda-users:
>
>GH> [EMAIL PROTECTED] amanda-2.4.5b1-20040915]$ amgetconf Daily
>GH> could not open conf file
>GH> "/home/amanda/amanda-2.4.5b1-20040915/amanda.con
Stefan G. Weichinger wrote:
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 ...
A patch for that bug was just posted by John E. Hein on -hackers.
Hi Kevin,
It's easy to try the newest amstatus.
download http://www.iro.umontreal.ca/~martinea/amanda/amanda-2.4.4p3-20040917.tar.gz
run "./configure ..." with your options
run "make"
You can now run the amstatus in server-src/amstatus directly, you don't need
to
Hi, Gene,
on Donnerstag, 16. September 2004 at 22:14 you wrote to amanda-users:
GH> [EMAIL PROTECTED] 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 conf
