On 05/30/16 10:24 AM, Marco van Wieringen wrote:
> On 05/30/16 02:38 AM, Douglas K. Rand wrote:
>> Any thought to allow pool types to not need to be capitalized? Took me
>> several hours to track down problems when a new pool used
>>
>>   pool type = backup
>>
>> That took me into the logs, then the database logs, and finally the
>> PostgreSQL create tables scripts to find the check statement.
>>
>> Nearly every thing else in the Bareos configuration file is case
>> insensitive, but the pool type isn't.
>>
>> Perhaps the config file parsing code should normalize the case?  (I'd
>> have thought that the pool type was a token, not a string.)
>>
> 
> I think no one ever tried fixing this behavior which we inherited from
> our forked project. Things are now defined as a normal string so you
> can enter whatever you like but there are only some types that are
> really allowed e.g. Backup, Copy, Cloned, Archive, Migration, Scratch
> 
> The simple solution is to add a special handler for parsing pool types
> that compares the data against the above mentioned allowed values and
> use the value from the list instead of the end user entered value.
> 
> I'll have a stab at it and if its not to much work it should be in
> the next stable release (e.g. 15.2.4 and 16.2.3).
> 

https://bugs.bareos.org/view.php?id=664

This should merge into 15.2 and master by Friday on which the
trigger from github will set the above mantis bug to resolved.

-- 
Marco van Wieringen                   [email protected]
Bareos GmbH & Co. KG                  Phone: +49-221-63069389
http://www.bareos.com                     

Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Komplementär: Bareos Verwaltungs-GmbH
Geschäftsführer: Stephan Dühr, M. Außendorf, J. Steffens,
                 P. Storz, M. v. Wieringen

-- 
You received this message because you are subscribed to the Google Groups 
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To post to this group, send email to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to