->>In response to your message<<- --received from Dustin J. Mitchell-- > > On Thu, May 22, 2008 at 7:34 PM, Paul Yeatman > <[EMAIL PROTECTED]> wrote: > > ./configure --with-user=amanda --with-group=wheel --prefix=/usr/local > > --without-server --with-config=laptops --with-gnutar=/usr/bin/tar > > --libexecdir=/usr/local/libexec --localstatedir=/Users > > LDFLAGS=-L/opt/local/include > > > > Hmmm, what's going on here?! > > You'll need to use --with-amlibexecdir=/usr/local/libexec. Sorry about that > :) >
Okay, now that I have more properly recompiled and I am certain I am using 2.6.0 (I thought for grins I would see if this alone would have resolved the issue as originally tried), I cannot connect to the client at all. An amcheck asks if the host is down. Unlike the usual case when this occurs, an amandad.* log file was actually generated on the client related to this (many many amandad.* log files, in fact) that all say the same thing 1211573838.146757: amandad: security_getdriver(name=bsdudp) returns NULL 1211573838.146772: amandad: critical (fatal): no driver for security type 'bsdudp' I believe this "'bsdudp' driver" is specified in the plist file, right? Why am I lacking a "driver of security type 'bsdudp'"? Thanks! Paul
