The amdump log file show that one backup was done, the IPv6 problem is
fixed.
Craig Dewick wrote:
Recompiling with the --without-ipv6 option didn't change anything
unfortunately, and I noticed in the report email that all of the file
systems targetted for backup are being reported as:
On 01/10/2007, Jean-Louis Martineau [EMAIL PROTECTED] wrote:
The amdump log file show that one backup was done, the IPv6 problem is
fixed.
That is what I was thinking too.
yoda /dev/dsk/c3t1d0s4 RESULTS MISSING
driver: FATAL infofile update failed (yoda,'/dev/dsk/c0t0d0s0')
The
Craig Dewick wrote:
On 01/10/2007, *Jean-Louis Martineau* [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
The amdump log file show that one backup was done, the IPv6 problem is
fixed.
That is what I was thinking too.
yoda /dev/dsk/c3t1d0s4 RESULTS MISSING
I recompiled Amanda on the three Solaris 9 systems today with the
'--without-ipv6' configure option added to the configure script I use,
which is currently:
sh ./configure --with-user=amanda --with-group=sys --with-amandahosts \
--with-tmpdir=/amanda/tmp --with-config=ORBnet
Recompiling with the --without-ipv6 option didn't change anything
unfortunately, and I noticed in the report email that all of the file
systems targetted for backup are being reported as:
FAILURE AND STRANGE DUMP SUMMARY:
jedi /dev/dsk/c0t0d0s6 RESULTS MISSING
jedi /dev/dsk/c0t0d0s3
I expect that will help you out.
IPv6 support is a little tricky -- ./configure detects libc- and
kernel-based IPv6 support -- as in, do the relevant socket functions
exist. Unfortunately, on a system where these pieces are in place,
but the actual admin-level configuration (either on the host
