FYI, I was interested in this post since I had just restricted my amanda account to only logon to my backup server but none of the backup clients. amcheck ran fine yesterday right when this post showed up. amdump ran fine last night.
I think you may have found your culprit with IPCHAINS. Doug > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]]On Behalf Of Toomas Aas > Sent: Friday, October 26, 2001 12:31 AM > To: [EMAIL PROTECTED] > Subject: Re: Does Amanda need shell? > > > Previously I wrote: > > > Amanda server running 2.4.2p1 on FreeBSD 4.3 > > Amanda client running 2.4.2p2 on Linux 2.4.12 (Slackware 8) > > > > In an attempt to tighten up security a bit I changed the amanda > > user's shell from /bin/bash to /nonexistent on the Slackware > > machine. Ran su amanda -c "amcheck -c MYCONFIG" on FreeBSD machine, > > it reported that everything was fine. But when the actual backup > > process ran, I got the report indicating that connection to > > Slackware machine cannot be established. > > Additional bit of information: even after reverting the shell to > /bin/bash, the backup still fails. I suspect it has something to do > with my colleague modifying IPCHAINS configuration on the Slackware > machine. It's strange, though, that amcheck doesn't see any > problems. > -- > Toomas Aas | [EMAIL PROTECTED] | http://www.raad.tartu.ee/~toomas/ > * How much net work could a network work, if a network could net work? >
