New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NBU libs in /usr/openv/netbackup/sec/at/lib not included #2105
Comments
|
I do not use NBU (Symantec/Veritas NetBackup) Perhaps Perhaps this issue here has the same root cause as How to try out our current ReaR GitHub master code Basically "git clone" our current ReaR upstream GitHub master code Note the relative paths "etc/rear/" and "usr/sbin/". |
|
Hi! Maybe you can integrate this?! Or shall I provide the merge request? |
|
@rmetrich #2105 (comment) to The question (that I cannot answer) is whether or not |
|
@jsmeix Thanks for pulling in the right person. |
|
I do not see any issue with this change.
Renaud.
Out of the office / Sent from my phone.
Le lun. 15 avr. 2019 11:52, Johannes Meixner <notifications@github.com> a
écrit :
… @rmetrich <https://github.com/rmetrich>
I dared to assign this issue to you because
you had worked on #1974 <#1974>
#2105 (comment)
<#2105 (comment)>
is about to change default.conf
from
NBU_LD_LIBRARY_PATH="/usr/openv/lib"
to
NBU_LD_LIBRARY_PATH="/usr/openv/lib:/usr/openv/netbackup/sec/at/lib/"
The question (that I cannot answer) is whether or not
adding /usr/openv/netbackup/sec/at/lib/ to NBU_LD_LIBRARY_PATH
by default could have unwanted side-effects (a.k.a. regressions) elsewhere.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2105 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABHBc7Y5G6vQE3ht1oEcf9Hm07cZA3dyks5vhEv1gaJpZM4cXjzu>
.
|
|
Created PR for this. Let me know if you need anything additionally changed/done, etc. |
|
Via |
|
Awesome - thanks for the prompt replies and merge! |
|
@ofalk do you know if there was there any reason to add the trailing slash? (Other entries do not have it, so I would prefer to be consistent.) |
|
@pcahyna I don't think there was any special reason to use trailing slash - I think it was just the preference of my customer back then and I used it as it is, given they had tested it that way. |
|
@ofalk thanks, I have another customer who tested it with the slash removed, so I will submit a PR to remove it for consistency. |
|
@pcahyna Sure!! |
ReaR version ("/usr/sbin/rear -V"): 2.4
OS version ("cat /etc/rear/os.conf" or "lsb_release -a" or "cat /etc/os-release"): RHEL7.6
ReaR configuration files ("cat /etc/rear/site.conf" and/or "cat /etc/rear/local.conf"):
Hardware (PC or PowerNV BareMetal or ARM) or virtual machine (KVM guest or PoverVM LPAR): n/a
System architecture (x86 compatible or PPC64/PPC64LE or what exact ARM device): x86_64
Firmware (BIOS or UEFI or Open Firmware) and bootloader (GRUB or ELILO or Petitboot): n/a
Storage (lokal disk or SSD) and/or SAN (FC or iSCSI or FCoE) and/or multipath (DM or NVMe): n/a (I guess you want this template to read 'local disk', not 'lokal disk' :-))
Description of the issue (ideally so that others can reproduce it):
While running
rear mkrescue -v, it reports the followingCurrently we're checking if setting
NBU_LD_LIBRARY_PATHto the following will solve the issue:The text was updated successfully, but these errors were encountered: