On 01/29/16 19:41, Hector Javier Agudelo Corredor wrote:
> HI team
>
>
> I installed centos 6.7.
>
> I have installed bacula 7.4 with postgres 5.7.10 but when I set the
> mysql password in the file director.
[...]
> But when I test settings file manager with the command
>
> bacula-dir sudo -t
I’ve seen this issue before. On Debian Wheezy 7.9 x86.
I *think* it is a conflict between x86 and x64 versions of the libs. For some
reason, when you compile on x86 (am I to assume you are running on x86 too?)
configure does not fail when it should. It clearly cannot find the binaries it
needs,
HI team
I installed centos 6.7.
I have installed bacula 7.4 with postgres 5.7.10 but when I set the mysql
password in the file director.
Catalog {
Name = MyCatalog
dbname = "bacula"; dbuser = "root"; dbpassword = "Bacula2016.,"
}
But when I test settings file manager with the command
ba
> Then you need to download the source for postgres 9.4 and compile from
source
it's a really bad idea
# lsb_release -a
LSB Version:
:base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch
Distributor ID: CentOS
Description:CentOS release 6.7 (Final)
Release:6.7
Codename:
On 01/29/2016 01:08 PM, Michael Munger wrote:
> Kindly disregard this post.
>
> MySQL Workbench detects the Name field as a BLOB type, and so,
promptly displays this as if I wanted to look at hex / binary data.
The long answer is postgres "text" data type stores somewhere between
1GB and "unlimit
On 01/29/2016 12:59 PM, Michael Munger wrote:
> Really. The table Filename, for example, has two columns:
> FilenameId INT(10)
> Name BLOB
Yuck. I think you should be able to run that query, though: they're just
text.
--
Dimitri Maziuk
Programmer/sysadmin
BioMagResBank, UW-Madison -- http://www.
Kindly disregard this post.
MySQL Workbench detects the Name field as a BLOB type, and so, promptly
displays this as if I wanted to look at hex / binary data.
When searching from the CLI, the filenames are readily apparent.
Incidentally, from the make_mysql_tables:
--Note, we use BLOB rather t
Really. The table Filename, for example, has two columns:
FilenameId INT(10)
Name BLOB
Michael Munger, dCAP, MCPS, MCNPS, MBSS
High Powered Help, Inc.
Microsoft Certified Professional
Microsoft Certified Small Business Specialist
Digium Certified Asterisk Professional
mich...@highpoweredhelp.com
On 01/29/2016 12:31 PM, Michael Munger wrote:
> (I tried to use MySQL Workbench to do a search on the actual
> database, but everything is stored as a blob…
Really? On postgres,
select p.path from path p join file f on f.pathid=p.pathid join filename
n on n.filenameid=f.filenameid where n.name='f
The “query” command, if memory serves, from console.
> On Jan 29, 2016, at 1:31 PM, Michael Munger
> wrote:
>
> I have read the docs for restore, but do not see (or perhaps I do not
> understand) how to search for a file in a backup.
>
> Suppose I know I want file foo.dat, but don’t remember
I have read the docs for restore, but do not see (or perhaps I do not
understand) how to search for a file in a backup.
Suppose I know I want file foo.dat, but don’t remember what directory it’s in.
How do I search for foo.dat in a backup? I know it might be possible because
when you restore, i
Hello,
Yes, I read the sentences with a problem, and suggested a resolution.
Nothing else.
If you have a patch which fix some bug then you need to report it at
http://bugs.bacula.org/ and attach your patch here. The users group is
dedicated to the support for user's problems.
I'm happy that you fi
On 01/29/2016 01:56 AM, Eric Bollengier wrote:
> Hello Peter,
>
> On 01/28/2016 10:09 PM, Peter Keller wrote:
>>
>> In bacula 7.2.0, in the Options block in a FileSet, if I specify something
>> like
>> accurate=s5, in what order is it tested? I ask because I'd prefer the order
>> of
>> check siz
13 matches
Mail list logo
