Greets all; A very small amount of progress, and what I would call a bug that really ought to be a showstopper, causing ./configure to bail out and report the missing dependency right then and there.
It seems amanda's make, or the configure step, is dependant on having swig2 installed and available. It was not, and now is. Then it at least gets the paths in the configure driver script, which I have previously posted, correct enough that it will successfully do an "amcheck Daily" with no errors, However, I must still specify the full path to the amcheck executable in /usr/local/sbin. I don't recall its ever needing swig2 to configure and build this same code tree, copied from the old drive before. However, locate says theres about 300 bits & pieces of swig installed on the old drive. However if a successfull build is dependant on swig2, why does the ./configure stage NOT exit with the error? To me, thats at least an 8 lb bug. To be filed against configure. Now, since the .bashrc is the same as before becuase its the same file copied, I'll go see if I can sort the lack of a working $PATH despite it looking ok when I use amanda to echo that $PATH and get this; su: Authentication failure (Ignored) $ echo $PATH /usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games Which is wrong as there is not a /usr/local/sbin in that list. BUT from that simple su amanda prompt, doing a . ../.bashrc fixes it to be: $ . ../.bashrc $ echo $PATH /usr/local/sbin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games And then this works: $ amcheck Daily Amanda Tape Server Host Check ----------------------------- Holding disk /usr/dumps: 752700 MB disk space available, using 752200 MB Searching for label 'Dailys-20':found in slot 20: volume 'Dailys-20' Will write to volume 'Dailys-20' in slot 20. NOTE: skipping tape-writable test Server check took 0.205 seconds Amanda Backup Client Hosts Check -------------------------------- Client check: 3 hosts checked in 2.627 seconds. 0 problems found. The su amanda -c "command" syntax has been working for well in excess of 10 years. What has changed to make it fall apart? My own wrapper script uses an identical syntax to set some other env vars the rest of my script uses, so I would imagine the failure of .bashrc to set it correctly is related to the original auth failure as shown about 33 lines above. Does anyone have an idea what to look at next? The passwd and group files are, for amanda, identical to the old Lucid based install. This girl is getting hard to love. I can remember that 2 weeks ago, it Just Worked(TM). Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene> US V Castleman, SCOTUS, Mar 2014 is grounds for Impeaching SCOTUS
