On Wednesday 30 July 2014 09:29:45 Nathan Stratton Treadway did opine And Gene did reply: > On Tue, Jul 29, 2014 at 12:15:06 +0700, Olivier Nicole wrote: > > If I may... I think the solution suggested by Nathan does not lean > > toward the excludes. > > Yes, that's correct. The thread only mentions excludes as a workaround > for situations where program=GNUTAR dumptypes are still being using, > since those dumptypes don't allow message handling to be configured on > the fly. > > When one is using the amgtar application (as Gene is), the "direct" way > to adjust to tar's new behavior is to add the > property "NORMAL" ": directory is on a different filesystem; not > dumped" line to the amgtar configuration block (or perhaps an IGNORE > line instead). That approach changes Amanda's handling of this > specific warning message, without changing anything else about the > operation of the dump. (And this is the default configuration in > Amanda 3.3.6 and later.) > > > (Gene, if you still decide to use excludes, you'll need to be sure that > the exclude lines you use allow tar to back up the mount-point > directory themselves -- otherwise if you have to do a bare-metal > restore you'll probably have to manually go back and create those > directories before the Ubuntu startup scripts will be able to work > properly.... [This "directory v.s. contents" topic is touched on in > http://wiki.zmanda.com/index.php/Exclude_and_include_lists > ... but I won't be more specific since you shouldn't be doing it that > way :) .]) > > > Nathan
My personal puzzle in this little contretemps is that the way amanda handles excludes, the string is a relatively formatted string, and only applies to what the scan algorithms can see at the current directory level. Ergo, a string "./lib/nfs/rpc_pipefs" isn't valid because it references 2 more subdirs. And I have tried just "./rpc_pipefs", which, while it should be valid, did not work. And a simple ./lib make it skip about 50 megs worth of stuff that lives in /var/lib, not to mention the whole /lib tree. Bad karma that. Now, you mention NORMAL in the amgtar setup, so I have the man page on another screen right now. But the man page is not detailed enough to provide any hints on how to actually use it. ANY man page should at the very least, supply an example of the syntax needed to use the feature. To call such a meatless skeleton a man page ought to be discouraged at the highest levels. Man pages are supposed to tell you how to use it, and that man page to me is a miserable failure. But that is too often what we get when the same author who wrote the code, also writes the man page. He assumes everyone knows all about it because he does. I don't know at the number of times I have been guilty of exactly that, so the last 2 major pieces I wrote for the (Nitr)OS9 os (a mini unix for 64k 6x09 based machines) on the TRS-80 Color Computer, affectionately known as the CoCo, had a man page type of tutorial as its error output, showing the expected syntax to use it correctly for every variation of its swiss army knife blades. Thanks Nathan. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
