I was just checking over the strace's for amcheck and planner, and noticed,
that amcheck makes a chdir call to change workin dir to /etc/amanda/DailySet1
when trying to open the amanda.conf file. Planner on the other hand makes no
such call, and therefore lacks the ability to see "amanda.conf" which is the
only thing it tries to open. If I could find out what variable is being set or
how this working dir is called I think I'll be ok, but it seems to me that a
standalone program like planner would have the ability to know *WHERE* it's
config files are, and if not, have a command line option to point at it. Not
just simply fail and dump to prompt. I'm thinking about manually editing the
planner.c to point specifically to /etc/amanda/amanda.conf but I don't
particularly *want* to do that nor do I have the time, nor am I a programmer.
If someone has a solution for this, you would be making my life MUCH
easier.
Thanks,
Tom Hudak
On Mon, Nov 13, 2000 at 11:03:41AM -0600, Tom Hudak wrote:
>Does anyone else have problem with planner not reading the config file? I can
>see in the planner output that it's looking in /etc/amanda which is 664 and
>has a copy of amanda.conf as well as /etc/amanda/DailySet1 which is where I'm
>assuming it's looking. Planner should be able to read and execute fine, it's
>+s and I'm running it as the backup user. --help and -h give me no info, and
>there's no manpage to read about, so I'm stuck guessing whats causing this.
>Any help would be greatly appreciated.
>Thanks,
>Tom Hudak
PGP signature
