-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You are not using the same lines that I tell you. AND ALWAYS COPY THE
MAILING LIST, unless as some members would say, you want to pay me in
support fees.
I don't know what the problem is, but you are not using the same lines I
give you. What I said to
I have not followed all the thread, so I'm sorry if I'm talking
about something else.
I have seen that in the "bacula" init script built by the
installation process this variables defined:
BACFDCFG=/bacula/scripts
BACSDCFG=/bacula/scripts
BACDIRCFG=/bacula/scripts
and then the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"dot-space" is correct -- you should not change that. I'm asking what
you get if you do that from the command line. That should source the
functions file and provide 'daemon' as well as other things.
Beren wrote:
> Yep, the bacula-dir startup script d
Yep, the bacula-dir startup script definitely has a "dot-space" before
/etc/rc.d/init.d/functions.
I removed the ". " from the bacula-dir startup script in /etc/init.d
and /etc/rc.d/init.d and it still can't find the daemon function...
On 15/02/07, Beren <[EMAIL PROTECTED]> wrote:
> Correction.
Correction... it does exist in rc.d/init.d
On 15/02/07, Beren <[EMAIL PROTECTED]> wrote:
> Right! Now we're getting somewhere:
>
> From bacula-dir.conf:
> # Source function library
> . /etc/rc.d/init.d/functions
>
> however, "functions" is located in /etc/init.d
>
> I tried:
>
> . ./etc/init.d/fun
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You wrote:
. ./etc/init.d/functions
Did you mean . /etc/init.d/functions (. is a command that loads files
into the environment) or did you actually do the above ('cuz that won't
work)?
Beren wrote:
> Right! Now we're getting somewhere:
>
>>From bac
Right! Now we're getting somewhere:
>From bacula-dir.conf:
# Source function library
. /etc/rc.d/init.d/functions
however, "functions" is located in /etc/init.d
I tried:
. ./etc/init.d/functions
and
/etc/init.d/functions
both still didn't work. Says it can't find the daemon command.
On 1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
That should be right. I don't have any EL3 machines (AS is just a
version of RHEL, like WS and ES).
The command 'daemon' probably DOES exist on your system though... in
fact, look at the top of the bacula-dir script; you probably have this:
# Source
I used bacula-mysql-2.0.2-1.el3.i386.rpm - It says "Enterprise Linux"
but in the past that has worked with Redhat AS.
Maybe I should just build it from source...?
On 14/02/07, Ryan Novosielski <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Which rpm did you use,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Which rpm did you use, though? If 'daemon' is not a command that exists
in RHEL3, the script should probably not try to use it.
=R
Beren wrote:
> Hi... I copied to the list this time... sorry about the last two times :)
>
> I'm using RedHat Advanced
Hi... I copied to the list this time... sorry about the last two times :)
I'm using RedHat Advanced Server v3. I think i've got the right RPM..
It installed fine anyway.
I've changed permissions of the bacula directory and its contained
files to owner "bacula" and group "bacula"
/etc/init.d/bacu
Howdy,
Please check the
permissions of the directories involved are set to user and group
bacula (check the compilation config file for the /working, /bin, etc,
paths). If they are not and you try chown it into bacula, and it fails,
it means your passwd file (or whatever authentication scheme
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Again, please copy the list. :)
I suspect you are not using the bacula that is specifically for your
distrobution of Linux. I believe daemon is an RHEL thing. You have not
mentioned your distro, but this is probably the problem. I'd make sure
there's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you are using a shell that supports it, add a 'set -x' or equivalent
near the top of the script and you'll see the execution of every command
and might see what goes wrong.
Beren wrote:
> Hi Everyone
>
> I've just upgraded from 1.38 to v2.0.1 and
Hi Everyone
I've just upgraded from 1.38 to v2.0.1 and changed my bacula-dir.conf
to accomodate.
I can't start the director bacula by typing /etc/bacula/bacula start
or by typing /etc/init.d/bacula-dir start or service bacula start
It says it completes successfully, but if I do "ps -ef" I can't
15 matches
Mail list logo
