[rear-users] rear checklayout questions

Robert Owens rowens at fdrinnovation.com
Fri Sep 25 17:06:12 CEST 2015


Done.

Thanks for all the advice, guys.  I am new to git and taking my time to 
read the docs.  Your advice is very helpful and appreciated.

-Rob

On 9/25/2015 3:26 AM, Gratien D'haese wrote:
> You still have to prepare a pull request via:
> https://github.com/rear/rear/compare/master...Innovation-Data-Processing:master
>
> rdgs,
> Gratien
>
> On Thu, 24 Sep 2015 16:16:04 -0400, Robert Owens
> <rowens at fdrinnovation.com> wrote:
>> Thanks for the advice.
>>
>> I've pushed my changes to
>> https://github.com/Innovation-Data-Processing/rear
>>
>>
>> On 9/24/2015 10:54 AM, Schlomo Schapiro wrote:
>>> Normally we edit configuration not in the software source but when
>>> deploying the software onto the target server.
>>>
>>> Adding local.conf from the *source tree* to .gitignore also won't work
>>> well because then you would be sending us the modified .gitignore along
>>> with your pull request.
>>>
>>> So from a larger perspective the best would be to leave local.conf
>>> unchanged. If you want, you can for example add your custom config to
>>> /etc/resr/site.conf on your test server. That file is read before
>>> local.conf (which we ship empty) and it it not part of the ReaR
>>> distribution so that it avoids this kind of conflict.
>>>
>>> On 24 September 2015 at 16:08, Robert Owens <rowens at fdrinnovation.com
>>> <mailto:rowens at fdrinnovation.com>> wrote:
>>>
>>>     One question before I upload:
>>>
>>>     My local.conf has been modified to specify 'BACKUP=FDRUPSTREAM'. Is
>>>     it proper procedure for me to add that file to .gitignore?  Or
>>>     should I upload it to my repo and you guys ignore it when pulling
>>>     from my repo?
>>>
>>>     -Rob
>>>
>>>     On 9/24/2015 5:42 AM, Schlomo Schapiro wrote:
>>>
>>>         Dear Robert,
>>>
>>>         without looking at your code I can't really help with that
>>> question.
>>>
>>>         Kind Regards,
>>>         Schlomo
>>>
>>>         On 23 September 2015 at 20:52, Robert Owens
>>>         <rowens at fdrinnovation.com <mailto:rowens at fdrinnovation.com>
>>>         <mailto:rowens at fdrinnovation.com
>>>         <mailto:rowens at fdrinnovation.com>>> wrote:
>>>
>>>              On 9/23/2015 9:42 AM, Robert Owens wrote:
>>>
>>>                  After I create an iso, I see a list of md5sums in
>>>                  var/lib/rear/layout/config/files.md5sum.  If I edit one
>>>         of the
>>>                  files in
>>>                  that list (lvm.conf, for example), should 'rear
>>>         checklayout'
>>>                  report the
>>>                  change to me?  Currently it does not, even though
>>>         running 'md5sum
>>>                  lvm.conf' shows that the md5sum has changed from what
>>>         is listed in
>>>                  files.md5sum.
>>>
>>>
>>>              Nevermind on this part, I expected output but I see now
>>>         that I have
>>>              to 'echo $?' to see the return code.  And it's working as
>>>         expected.
>>>
>>>                  Is it acceptable for me to add files to be checked,
>>> using
>>>                  CHECK_CONFIG_FILES_FDRUPSTREAM?  I would like a change
>>>         of my backup
>>>                  product's config file to be noticed by ReaR.
>>>
>>>
>>>              I'm still wondering if this variable is reserved for
>>>              behind-the-scenes Relax and Recover operations, or if I am
>>>         able to
>>>              create it.  And I guess that question extends to any
>>>         variable -- can
>>>              I always make my own or are there restrictions to what
>>>         variables I
>>>              can create/modify?
>>>
>>>
>>>              --
>>>              Rob Owens
>>>              Innovation Data Processing
>>>              973-890-7300
>>>         rowens at fdrinnovation.com <mailto:rowens at fdrinnovation.com>
>>>         <mailto:rowens at fdrinnovation.com
>>> <mailto:rowens at fdrinnovation.com>>
>>>
>>>              _______________________________________________
>
>



More information about the rear-users mailing list