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.conf": No such file > or GH> directory >GH> amgetconf: errors processing config file >GH> "/home/amanda/amanda-2.4.5b1-20040915/amanda.conf" >GH> [EMAIL PROTECTED] 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> [EMAIL PROTECTED] amanda-2.4.5b1-20040915]$ >GH> cp /usr/local/etc/amanda/Daily/amanda.conf . >GH> [EMAIL PROTECTED] 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.
And I don't recall if it has ever worked here, Stefan. I had so much trouble with the tape drives over the last year that any autoflush miss-fires were probably lost in the background noise of me swearing at 4 failed drives. Now I'm using the file: setup, which, until this shiney new 200GB drive dies at least, would appear to be considerably more dependable than tape *here*. Not to mention faster, but its also pushed some buttons for the kernel and I had 2 instances of my main drives '/' partition going read-only on me when the system was i/o busy, like amdump still running when logrotate or updatedb fires up. Since /var is on /, my last move was to give 15GB of the swap I had accidently setup on that new 200GB drive, to a new /var partition so that the next time / goes read-only, I'll hopefully have a trail in the logs. However, that was now 2 days back, and 'the watched pot never boils' syndrome is in effect. :( Last nights run was 'nominal'. And I've added a run of amverify to the wrapper scripts I use here, so I have a wee bit more confidence. -- Cheers, Gene "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) 99.26% setiathome rank, not too shabby for a WV hillbilly Yahoo.com attorneys please note, additions to this message by Gene Heskett are: Copyright 2004 by Maurice Eugene Heskett, all rights reserved.