On 06/30/2012 01:42 PM, Reindl Harald wrote:
dirty workaorund != solution
You and I don't always agree, but on this we're on the same page.
Running a service as root without trying to find out what's wrong is
just as bad as turning off SELinux whenever a program crashes, even
though there ar
Am 30.06.2012 22:33, schrieb Erik P. Olsen:
> On 30/06/12 21:41, Reindl Harald wrote:
>> this is NOT a solution
>
> Well, since it makes bacula run, it IS a solution allthough I admit it IS bad.
dirty workaorund != solution
>> NEVER let any service run as ROOT
>> really NEVER!
>
> May be the
On 30/06/12 21:41, Reindl Harald wrote:
Am 30.06.2012 21:36, schrieb Erik P. Olsen:
On 30/06/12 02:35, Bill Shirley wrote:
Is there any information in /var/log/messages or bacula's log?
Nothing decisive.
What does 'Starting bacula-dir manually' mean? From systemd vs upon boot?
From the
On 06/30/2012 12:41 PM, Reindl Harald wrote:
this is NOT a solution
NEVER let any service run as ROOT
really NEVER!
Yes! These services create special user/group combos to use because
they have to be owned by some regular user without special privileges to
limit the potential damage a bug ca
Am 30.06.2012 21:36, schrieb Erik P. Olsen:
> On 30/06/12 02:35, Bill Shirley wrote:
>> Is there any information in /var/log/messages or bacula's log?
>
> Nothing decisive.
>>
>> What does 'Starting bacula-dir manually' mean? From systemd vs upon boot?
>
> From the command line launch bacula-di
On 30/06/12 02:35, Bill Shirley wrote:
Is there any information in /var/log/messages or bacula's log?
Nothing decisive.
What does 'Starting bacula-dir manually' mean? From systemd vs upon boot?
From the command line launch bacula-dir
However, I've solved the problem. When launching bacula-
