View Issue Details

IDProjectCategoryView StatusLast Update
0000301bareos-core[All Projects] directorpublic2015-01-26 16:12
ReporteralexbrueckelAssigned To 
PrioritylowSeveritytweakReproducibilityalways
Status confirmedResolutionopen 
PlatformOSDebian 7OS Version
Product Version13.2.2 
Target VersionFixed in Version 
Summary0000301: Inconsistency when configuring bandwith limitation
DescriptionHi,
while configuring different jobs for a client, some width bandwith limitation, i noticed that every configuration item could be placed in quotation marks except the desired max. bandwidth.

It's a bit inconsistent this way so it would be great if this could be fixed.

Thank you very much
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

mvwieringen

mvwieringen

2014-05-31 22:04

developer   ~0000889

An example and the exact error would be handy. Its probably some missing
parsing as all config code uses the same config parser. But without a
clear example and the exact error its not something we can go on.
alexbrueckel

alexbrueckel

2014-06-04 17:37

reporter   ~0000899

Hi,

here's the example that works:
Job {
  Name = "myhost-backupjob"
  Client = "myhost.mydomain.tld"
  JobDefs = "default"
  FileSet = "myfileset"
  Maximum Bandwidth = 10Mb/s
}

Note that the bandwidth value has noch quotation marks.

Thats an example that doesn't work:
Job {
  [same as above]
  Maximum Bandwidth = "10Mb/s"
}

The error message i get in this case is:
ERROR in parse_conf.c:764 Config error: expected a speed, got: 10Mb/s

Hope that helps and thanks for your work.
Alex
mvwieringen

mvwieringen

2014-06-06 15:39

developer   ~0000900

It seems that the config engine only allows a quoted string. E.g. all numbers
are now allowed to have a quotation. As the speed get parsed by the same function
as a number it currently doesn't allow you to use quotes. You can indeed argue
that its inconsistent but it seems to be envisioned by the original creator of
the config engine. We might change this one day but for now I wouldn't hold my
breath for it to occur any time soon. There are just more important things to do.
joergs

joergs

2014-12-01 16:13

administrator   ~0001086

I added some notes about this to the documentation.

Issue History

Date Modified Username Field Change
2014-05-27 17:02 alexbrueckel New Issue
2014-05-31 22:04 mvwieringen Note Added: 0000889
2014-05-31 22:04 mvwieringen Status new => feedback
2014-06-04 17:37 alexbrueckel Note Added: 0000899
2014-06-04 17:37 alexbrueckel Status feedback => new
2014-06-06 15:39 mvwieringen Note Added: 0000900
2014-06-06 15:39 mvwieringen Assigned To => mvwieringen
2014-06-06 15:39 mvwieringen Status new => acknowledged
2014-06-06 15:39 mvwieringen Assigned To mvwieringen =>
2014-12-01 11:43 joergs Assigned To => joergs
2014-12-01 11:43 joergs Status acknowledged => assigned
2014-12-01 16:13 joergs Note Added: 0001086
2014-12-01 16:13 joergs Assigned To joergs =>
2015-01-26 16:12 mvwieringen adm Status assigned => confirmed