View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0000922 | bareos-core | director | public | 2018-03-02 08:26 | 2024-03-20 14:37 |
Reporter | tuxmaster | Assigned To | joergs | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Platform | Linux | OS | CentOS | OS Version | 7 |
Product Version | 17.2.5 | ||||
Summary | 0000922: true/false will not work always in the same manner as yes/no | ||||
Description | In the documentation is written under data types: yes|no Either a yes or a no (or true or false). So on most parts of the configuration you can use yes/no or true/false. But not on the FileSet -> Include -> Options part. Here it will break the director. | ||||
Steps To Reproduce | For example: 1. set use "onefs = true" instant of "onefs = yes" 2. restart the director 3. now the director don't start. | ||||
Additional Information | Error message: ERROR TERMINATION at inc_conf.c:254 Config error: Expected a FileSet option keyword, got: true: line 8, col 42 of file /etc/bareos/bareos-dir.d/fileset/foo.conf onefs=true | ||||
Tags | No tags attached. | ||||
documentation say yes|no not true false and that doesn't mean you can exchange this. this is also the case for Portable option and certainly a lot of other parameters. Feel free to propose a PR to fix that behavior, or perceived as a limit. |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2018-03-02 08:26 | tuxmaster | New Issue | |
2018-04-05 18:16 | joergs | Assigned To | => joergs |
2018-04-05 18:16 | joergs | Status | new => assigned |
2024-03-20 14:37 | bruno-at-bareos | Status | assigned => closed |
2024-03-20 14:37 | bruno-at-bareos | Resolution | open => no change required |
2024-03-20 14:37 | bruno-at-bareos | Note Added: 0005853 |