Thanks Jean-Lous.
In my dumptype I have
program "GNUTAR"
but I don't know if this always means 'gtar' or if it's defined somewhere.
I can't find a define for it.
However, other 'include' expressions seem to be globbing correclty, even
though the amgtar docs says gtar won't normal accept them. e.g. this
expression is working:
include "./[f-i]*"
So maybe GNUTAR is defined to use amgtar?
Assuming I'm using amgtar, then it seems since it only manually globs
expressions with a single forward slash, I should change my DLE to this,
which includes the sub-dir in the DLE diskdevice:
cfile.uphs.upenn.edu jet-grosspeople-h-z /jet/grosspeople {
gui-base
include "./[h-zH-Z]*"
exclude "./Volumetric"
}
Does that seem right?
Regarding the related globbing issue:
As an aside (or possibly related?) the case-sensitivity of globbing on my
> client is not behaving how I'd expect. e.g. 'echo [a-c]*' includes files
> that start with capital A-B, which I don't expect. Files starting with C
> are *not* listed. My shell option nocaseglob is off, and I've tried setting
> and unsetting it just to test. Nothing changes. I'll post about this last
> bit to another list too.
It seems that with shift to unicode years ago, the sorting order doesn't
follow ascii order by default anymore.
If I add 'export LC_COLLATE=C' to my shell, then 'echo [a-c]*' behaves as
expected. Assuming that amgtar uses shell globbing to do its manually
globbing of 'include' expressions, and since gtar seems to use shell
globbing on its own for 'exclude' expressions, I figure I should add
'export LC_COLLATE=C' to my amandabackup profiles. It seems also that for
'exclude' expressions, I could use '[[:lower:]]' to indicate lower case,
e.g. But then that wouldn't work for 'include' expressions b/c of amgtar's
manual globbing.
Thoughts?
Thanks
-M
On Tue, Mar 11, 2014 at 2:04 PM, Jean-Louis Martineau
<[email protected]>wrote:
> Michael,
>
> Look at the amgtar man page if you are using amgtar:
>
> Similarly, include expressions are supplied to GNU-tar's
> --files-from
> option. This option ordinarily does not accept any sort of
> wildcards,
> but amgtar "manually" applies glob pattern matching to include
> expressions with only one slash. The expressions must still begin
> with
> "./", so this effectively only allows expressions like "./[abc]*" or
> "./*.txt".
>
> Jean-Louis
>
>
> On 03/11/2014 01:53 PM, Michael Stauffer wrote:
>
> Amanda 3.3.4
>
> Hi,
>
> I'm confused about using glob patterns in disklist. Am I right that if I
> use dumptype include and exclude directives, I can use shell globbing?
>
> This is part of my disklist:
>
> cfile.uphs.upenn.edu jet-grosspeople-0-g /jet {
> gui-base
> #Get everything ^[0-9] and ^[a-zA-Z]
> include "./grosspeople"
> exclude "./grosspeople/[h-zH-Z]*"
> }
> cfile.uphs.upenn.edu jet-grosspeople-h-z /jet {
> gui-base
> include "./grosspeople/[h-zH-Z]*"
> exclude "./grosspeople/Volumetric"
> }
> cfile.uphs.upenn.edu jet-grosspeople-Volumetric /jet {
> gui-base
> include "./grosspeople/Volumetric"
> }
>
> My log shows me this warning:
>
> STRANGE dumper cfile.uphs.upenn.edu jet-grosspeople-h-z 1 [sec 0.232 kb
> 10 kps 43.1 orig-kb 10]
> sendbackup: start [cfile.uphs.upenn.edu:jet-grosspeople-h-z level 1]
> sendbackup: info BACKUP=/bin/gtar
> sendbackup: info RECOVER_CMD=/bin/gtar -xpGf - ...
> sendbackup: info end
> ? /bin/gtar: ./grosspeople/[h-zH-Z]*: Warning: Cannot stat: No such file
> or directory
> ? /bin/gtar: ./grosspeople/[h-zH-Z]*: Warning: Cannot stat: No such file
> or directory
> | Total bytes written: 10240 (10KiB, 41MiB/s)
> sendbackup: size 10
> sendbackup: end
>
> If I do a shell glob manually on the client, e.g. 'echo
> /jet/grosspeople/[h-zH-Z]*', there's no warning and it shows the list of
> files.
>
> Interestingly, it does not complain about the same glob in the
> jet-grosspeople-0-g DLE. And, the reported size from 'amstatus jet1' of
> the jet-grosspeople-0-g DLE looks to match the size I expect if the
> 'exclude "./grosspeople/[h-zH-Z]*"' directive was properly exectued.
>
> Anyone know why this might be be responding differently to the same glob?
>
> As an aside (or possibly related?) the case-sensitivity of globbing on
> my client is not behaving how I'd expect. e.g. 'echo [a-c]*' includes files
> that start with capital A-B, which I don't expect. Files starting with C
> are *not* listed. My shell option nocaseglob is off, and I've tried setting
> and unsetting it just to test. Nothing changes. I'll post about this last
> bit to another list too.
>
> Thanks for any thoughts.
>
> -M
>
>
>
