On Thursday 29 December 2005 14:19, Timo Neuvonen wrote:
> > Someone wiser than me needs to decide, if it's ok simply to change back
>
> user
>
> > to root. Or is there a reason why not to do this? Are there some other
> > changes that would really require a non-root user?
>
> Btw, this applies not
> On Thu, 29 Dec 2005 22:40:23 +0200, "Timo Neuvonen" <[EMAIL PROTECTED]>
> said:
>> DIR as non-root:
>> I suspect that the configuration files were not accessible by user
>> bacula. You can easily check this using the ls command (like ls -l
>> /etc/bacula ) and see if user bacula
Hello,
On 12/29/2005 9:40 PM, Timo Neuvonen wrote:
...
For now, 1.38.3 is beta and it's understandable that there may be things to
fix. However, building a binary rpm from a source rpm with build_fc4 option
doesn't now produce a working rpm for FC4, so from my point of view there is
something th
> DIR as non-root:
> I suspect that the configuration files were not accessible by user
> bacula. You can easily check this using the ls command (like ls -l
> /etc/bacula ) and see if user bacula has read access to the necessary
files.
> strace can help a lot when tracing that sort of problem.
> Pe
Hello,
On 12/29/2005 2:19 PM, Timo Neuvonen wrote:
Someone wiser than me needs to decide, if it's ok simply to change back
user
to root. Or is there a reason why not to do this? Are there some other
changes that would really require a non-root user?
DIR as non-root:
I suspect that the conf
> On Thu, 29 Dec 2005 15:01:19 +0200, "Timo Neuvonen" <[EMAIL PROTECTED]>
> said:
>> Try to figure out why it doesn't start. Find what command line args are
Timo> being
>> passed to bacula-dir e.g. by
>>
>> sh -x /etc/init.d/bacula start
>> Then run bacula-dir with the same
> Someone wiser than me needs to decide, if it's ok simply to change back
user
> to root. Or is there a reason why not to do this? Are there some other
> changes that would really require a non-root user?
>
Btw, this applies not only to the director, but also to the storage daemon.
It also had been
> Try to figure out why it doesn't start. Find what command line args are
being
> passed to bacula-dir e.g. by
>
> sh -x /etc/init.d/bacula start
> Then run bacula-dir with the same command line args to see if it reports
> auything.
>
It very shy... reports very nothing before dying.
1.38.2 start
> A further note: I installed mtx from FC4 repo with
And one more further note:
I tried building 1.38.0 by myself too, got it running after
replacing build_fc4 with build_fc3.
Then I tried building 1.38.2, no problems this time either.
So, this is something that happens only with 1.38.3 beta.
-
> Packages build and install nicely. SD and FD start also nicely,
> and stay alive too.
>
A further note: I installed mtx from FC4 repo with
yum install mtx
to fullfill dependencies with 1.38.3
To return back to 1.38.0, I removed package mtx
1.38.0 then runs ok again.
--
TiN
--
10 matches
Mail list logo
