Re: "wildcard" datestamp match in dumpspecs?

(Looks like this question about wildcarding the datestamps in dumpspecs
still applies in v3.5, so bumping this thread.)

							Nathan

On Mon, Sep 25, 2017 at 12:55:11 -0400, Nathan Stratton Treadway wrote:
> (Amanda v3.4.5:)
> 
> The amanda-match.7 man page includes the following example in the DUMP
> SPECIFICATIONS section:
> 
>        amtool MyConfig www1 /var/www '*' www2 /var/www '*'
>            All dumps of /var/www on www1 and www2 (assuming amtool does not
>            require a level argument)
> 
> However, in my tests using amvault, "*" is not valid for the datestamp.
> 
>   $ amvault TestBackup --dest-storage TestOffsite --dry-run '*' '*' '*' 1
>   amvault: Illegal datestamp expression *
> 
> similarly:
>   $ amvault TestBackup --dest-storage TestOffsite --dry-run '*' '*' '' 1
>   amvault: Illegal datestamp expression
> 
> while e.g.
> 
>   $ amvault TestBackup --dest-storage TestOffsite --dry-run '*' '*' '2' 1
> does produce a list of all the level-1 dumps.
> 
> Am I correct that "2" is currently the best "wildcard" to use for
> place-holding the datestamp position in a dumpspec?
> 
> Is there any reason '*' couldn't be handled as a special exception in
> match.c:match_datestamp(), so that field would behave similar to the
> host and disk fields?  
> 
> 							Nathan


----------------------------------------------------------------------------
Nathan Stratton Treadway  -  [email protected]  -  Mid-Atlantic region
Ray Ontko & Co.  -  Software consulting services  -   http://www.ontko.com/
 GPG Key: http://www.ontko.com/~nathanst/gpg_key.txt   ID: 1023D/ECFB6239
 Key fingerprint = 6AD8 485E 20B9 5C71 231C  0C32 15F3 ADCD ECFB 6239