On 9/28/18 10:09 PM, Gary R. Schmidt wrote:
> Most of the time the various Bacula programs are waiting for I/O
> operations to complete, the only time the CPU gets heavily involved is
> if you are running compression.
>
> Just use the defaults. You won't save enough CPU, memory, or time to
> j
On 29/09/2018 04:00, George Anchev via Bacula-users wrote:
On Fri, 28 Sep 2018 14:47:46 +0100 Martin Simmons
wrote:
This is not Bacula-specific: producing debugging
information is useful, just in case you need it.
And an end user generally does not need it. Also AFAIK
adding debugging info to
Am 28.09.2018 um 22:05 schrieb George Anchev via Bacula-users:
> On Fri, 28 Sep 2018 21:22:31 +0200 Tilman Schmidt wrote:
>
[debuging information]
>> What's more, it's easy to remove should it bother
>> you, but imposssible to add later if you didn't
>> create it while building the executable.
>
Hello Miguel,
Thanks for your detailed response.
If you don't have api.conf in
/usr/share/baculum/htdocs/protected/API/Config/ it means that you
don't have Baculum API configured. Did you go through the Baculum API
wizard on http://localhost:9096 ? Is the Baculum API working on your
side? I mean
On Fri, 28 Sep 2018 21:22:31 +0200 Tilman Schmidt
wrote:
> As long as everything runs smoothly you don't.
> As soon as you want to create a crash report you do.
> And it costs next to nothing so it is a good thing
> to have in place should a crash occur.
> What's more, it's easy to remove should i
Am 28.09.2018 um 20:00 schrieb George Anchev via Bacula-users:
> On Fri, 28 Sep 2018 14:47:46 +0100 Martin Simmons wrote:
>
>> This is not Bacula-specific: producing debugging
>> information is useful, just in case you need it.
>
> And an end user generally does not need it.
As long as everythin
On 2018-09-28 09:32 AM, Martin Simmons wrote:
On Thu, 27 Sep 2018 20:57:35 -0400, Gary Dale said:
On 2018-09-27 11:05 AM, Martin Simmons wrote:
On Wed, 26 Sep 2018 23:38:39 -0400, Gary Dale said:
On 2018-09-26 11:33 AM, Bill Arlofski wrote:
On 09/26/2018 06:22 AM, Martin Simmons wrote:
Try
On 2018-09-28 06:13 AM, Kern Sibbald wrote:
Hello,
It should not take "I need a lot of new volumes to handle what amounts
to a full backup of 160G of data" unless you are artificially
restricting volume size. Unless I misunderstood what you wrote, you
should not have 40 volumes to store 160G
On Fri, 28 Sep 2018 14:47:46 +0100 Martin Simmons
wrote:
> This is not Bacula-specific: producing debugging
> information is useful, just in case you need it.
And an end user generally does not need it. Also AFAIK
adding debugging info to binaries makes them slower.
> You can remove it using str
You can find the actual tmpdir by running the sql command
show variables like 'tmpdir';
The missing error message is very strange.
Is there anything in the mysqld logs? Turning up the mysqld query logging
level might help to narrow it down (sorry I don't know how to do that).
__Martin
>
Hi,
Bacula was not compiled with batch insert enabled.
The OS partition has 13 GB available. I ran the command "mysqld --verbose
--help | grep tmp" and got the following:
max_tmp_tables32
slave-load-tmpdir /tmp
tmpdir(No default val
> On Thu, 27 Sep 2018 19:26:40 +0300, George Anchev via Bacula-users said:
>
> As for standard options - according to the manual:
>
> 'We recommend [...] CFLAGS="-g -O2 -Wall" [...]'
>
> but it is not clear why e.g. "-g" is needed ("Produce
> debugging information" (ref. `man gcc`)) if one i
> On Thu, 27 Sep 2018 20:57:35 -0400, Gary Dale said:
>
> On 2018-09-27 11:05 AM, Martin Simmons wrote:
> >> On Wed, 26 Sep 2018 23:38:39 -0400, Gary Dale said:
> >> On 2018-09-26 11:33 AM, Bill Arlofski wrote:
> >>> On 09/26/2018 06:22 AM, Martin Simmons wrote:
> Try
>
> se
Hello,
It should not take "I need a lot of new volumes to handle what amounts
to a full backup of 160G of data" unless you are artificially
restricting volume size. Unless I misunderstood what you wrote, you
should not have 40 volumes to store 160G of data. One would be
sufficient. In fact
14 matches
Mail list logo
