If the configuration keywords are shifted into different order, the amcheck still reports the problem at the first line that has any keyword.  If I insert an invalid configuration keyword, the amcheck still reports the same error.

Running amrecover does connect back to the index_server from the config file entry. 

If I insert and invalid configuration parameter (w/o any additional data on that line), I get the following response. (line 6 is the invalid keyword):

# amrecover
"/usr/local/etc/amanda/amanda-client.conf", line 6: configuration keyword expected
amrecover: error reading conffile: /usr/local/etc/amanda/amanda-client.conf

If I include an invalid parameter and value I get a very similar response to the amcheck output that is complaining about "end of line expected".

# amrecover
"/usr/local/etc/amanda/amanda-client.conf", line 6: configuration keyword expected
"/usr/local/etc/amanda/amanda-client.conf", line 6: end of line is expected
amrecover: error reading conffile: /usr/local/etc/amanda/amanda-client.conf

The  amanda-client.conf file that I am using was pulled from a working amanda client system.


The 2.5.2p1 source tarball did not have a device-src module.  I do not find any device-src directory anywhere in the source code. There were no files or directories w/ the name "\*device\*".
This is a listing of all of the Makefile files in the source code.

# pwd
/wrk/michaelr/amanda/amanda-2.5.2p1
# find . -name Makefile -print
./amplot/Makefile
./changer-src/Makefile
./client-src/Makefile
./common-src/Makefile
./config/Makefile
./dumper-src/Makefile
./example/Makefile
./server-src/Makefile
./gnulib/Makefile
./amandad-src/Makefile
./tape-src/Makefile
./restore-src/Makefile
./recover-src/Makefile
./oldrecover-src/Makefile
./man/Makefile
./docs/Makefile
./Makefile

# find . -type f -name tape\*.c -print
./common-src/tapelist.c
./server-src/tapefile.c
./server-src/taperscan.c
./server-src/taper.c
./tape-src/tapeio.c
./tape-src/tapetype.c

The only changes that I have made to the source code to make everything compile are the following:

server-src/  and dumper-src/

Makefile.am and Makefile.in  -  remove the capital "W" option from the perl command options.  That option is not supported.
perl --version
Perl 5.005_03 This is perl, version 5.005_03 built for i386-sco

tape-src/

Makefile.in and Makefile.am - added the gnulib/libgnu.$(LIB_EXTENSION) to the list of libraries in order for the libamtape.la to be included in several of the tape-src compiles.
###
# Because libamanda includes routines (e.g. regex) provided by some system
# libraries, and because of the way libtool sets up the command line, we
# need to list libamanda twice here, first to override the system library
# routines, and second to pick up any references in the other libraries.
###
LDADD = ../common-src/libamanda.$(LIB_EXTENSION) \
        libamtape.$(LIB_EXTENSION) \
        ../common-src/libamanda.$(LIB_EXTENSION) \
        ../gnulib/libgnu.$(LIB_EXTENSION)

Michael R_

On Wed, 2008-07-23 at 15:02 -0400, Dustin J. Mitchell wrote:

On Wed, Jul 23, 2008 at 2:38 PM, Michael Reuland
<michael.reuland AT activant DOT com> wrote:
> I have stripped the ~etc/amanda/amanda-client.conf file to only the actual
> configuration keywords and options.  I still get the similar response
> reporting the first line of configuration data from the file.

What happens if you switch the order of lines so that the first line
is e.g., the second?

> Is there a utility that I can run on the client to see if the config file is
> being read correctly?  I'd like to narrow down the problem.  Since I have
> the host server running w/ a different client (not SCO), I'd like to focus
> on the client platform to start with.

You can run 'amrecover' on the client.  It should give the same error messages.

On a completely unrelated topic, I'd like to know whether your SCO
system uses POSIX tapes or the old "uware" driver.  Can you run
  grep 'tape-.*\.c' device-src/Makefile
and send me the result?  I'm considering removing native uware (and
aix and xenix) support, since most systems have POSIX these days, and
since we don't have a way to test these other systems.

Dustion

_________________________ Michael Reuland Senior Unix Systems Engineer Activant Solutions Inc.™ T: 512.278-5310 F: 512-278-5915 The opinions expressed here aren't even mine... To err is human...to really foul up requires the root password.

 

 

Notice: This transmission is for the sole use of the intended recipient(s) and may contain information that is confidential and/or privileged.  If you are not the intended recipient, please delete this transmission and any attachments and notify the sender by return email immediately.  Any unauthorized review, use, disclosure or distribution is prohibited.