On 06/15/2012 09:17 AM, Marco van Wieringen wrote:
> On 06/15/12 01:53 PM, Steven A. Falco wrote:
>> On 06/15/2012 04:36 AM, Marco van Wieringen wrote:
>>> Steven A. Falco optonline.net> writes:
> I closed the bug it should be part of 5.2.10 when that gets released. You can
> grab
> a copy from
On 06/15/12 01:53 PM, Steven A. Falco wrote:
> On 06/15/2012 04:36 AM, Marco van Wieringen wrote:
>> Steven A. Falco optonline.net> writes:
>
>>> In other words, the call to rwl_writelock_p is returning EINVAL
>>> because the rwl is not valid. (I added a printf right before
>>> the return stateme
On 06/15/2012 04:36 AM, Marco van Wieringen wrote:
> Steven A. Falco optonline.net> writes:
>> In other words, the call to rwl_writelock_p is returning EINVAL
>> because the rwl is not valid. (I added a printf right before
>> the return statement, so I am sure that this is the place the
>> EINVA
Steven A. Falco optonline.net> writes:
>
>
> In other words, the call to rwl_writelock_p is returning EINVAL
> because the rwl is not valid. (I added a printf right before
> the return statement, so I am sure that this is the place the
> EINVAL (err 22) comes from.)
>
> Again, dbcheck puts ou
On 06/14/2012 09:46 PM, Steven A. Falco wrote:
A line feed got dropped - here is the corrected output from
dbcheck:
saf# dbcheck -B -c /etc/bacula/bacula-dir.conf
catalog=MyCatalog
db_name=bacula
db_driver=
db_user=bacula
db_password=
db_address=
db_port=0
db_socket=
db_type=PostgreSQL
working_di
