I have not heard of this on Debian, but
it is a problem on Ubuntu and in their bugzilla database. I
suspect that even though Ubuntu takes a number of Debian packages,
they probably add some different linking options.
On 10/02/2016 01:41 AM, Sven Hartge
Hello,
When one uses the -Bsymbolic_functions link option, the effect on
Bacula is that the default values will not in all cases be set
correctly. The exact mechanism is a bit complicated but I think it
applies mostly to the Director. The "workaround" for this problem
(requiring no
On 01.10.2016 16:51, Hankins, Jonathan wrote:
> It seems weird that the bacula package in Debian and Ubuntu, et al, is
> broken and no one has noticed (checked Debian bug database). I know
> Debian has been on 5.x in the stable release for years (still is). It's
> possible that 7.0.5 got packaged
Thanks to Kern, John, and Josh,
It seems I am not crazy after all :). So the current release version
from Mint 18 seems to be compiled with a link switch
-Bsymbolic_functions, which makes it not work. The version lines for my
bacula-dir and bconsole:
trinity% sudo /usr/sbin/bacula-dir -?
After using Bacula for close to a decade with a tape autochanger, I'm
slightly lost with ideas related to disk-based backup I'm now trying to
implement.
Now I have a fersh test install of Bacula 7.0.5, on CentOS 7. Bacula comes
from EPEL repo.
The supplied example conf files define a
I cannot say for sure about Debian, but
for Ubuntu there are/were bug reports open. All have been
resolved by the packagers with my input. What happened with
Ubuntu is that they simply
packaged it and released it without testing (surely due to lack of
It seems weird that the bacula package in Debian and Ubuntu, et al, is
broken and no one has noticed (checked Debian bug database). I know Debian
has been on 5.x in the stable release for years (still is). It's possible
that 7.0.5 got packaged for their testing release and maybe Ubuntu xenial
Hello Josh,
Yes, if you build either with -D fortify-source=2 or link with -Bsymbolic-functions, Bacula will
fail. It is best
to stick with the Bacula recommended build options, which is
what you are using.
Also if you have a Bacula
On 10/1/2016 2:44 AM, Hankins, Jonathan wrote:
So I've narrowed it down. If I build from Debian's patched source, but
run ./configure myself, my flags in config.out look like:
Compiler flags: -g -O2 -Wall -fno-strict-aliasing
-fno-exceptions -fno-rtti
Linker flags:
However, if I
This is by design to ensure that Bacula
never destroys good data. On the other hand, if you run Bacula in
the manner it was designed to run, it will reuse old volumes.
In newer versions of Bacula, it is possible to tell Bacula to
truncate volumes when
So I've narrowed it down. If I build from Debian's patched source, but run
./configure myself, my flags in config.out look like:
Compiler flags: -g -O2 -Wall -fno-strict-aliasing -fno-exceptions
-fno-rtti
Linker flags:
However, if I build using debian's rules file, my flags in
11 matches
Mail list logo
