On Fri, Oct 29, 2004 at 02:47:20AM -0700, Kevin Dalley wrote:
> "Stefan G. Weichinger" <monitor AT oops.co DOT at> writes:
> 
> > Hi, Kevin,
> >
> > on Freitag, 29. Oktober 2004 at 06:42 you wrote to amanda-users:
> >
> > KD> I figured out the problem, after modifying "amadmin disklist" so that
> > KD> it prints out the spindle number, at least in amanda-24.4p3.
> >
> > KD> I had lines in disklist which looked something like this:
> >
> > KD> localhost //bunting/c$ root-sambatar eth0
> >
> > KD> eth0 was parsed as a spindle number of 0, in addition to being parsed as
> > KD> an interface value of eth0.
> >
> > Errm, I could have seen this ... was late here ...
> >
> > KD> It looks like maxdumps is picked up correctly, but the spindle value
> > KD> of 0 may be preventing multiple dumpers from running.  I'll give it
> > KD> another try soon, and suggest a few patches to the amanda-hackers list.
> >
> > The file format for disklist is:
> >
> > hostname diskdev dumptype [spindle [interface]]
> >
> > which means that you have to define a spindle if you want to define an
> > interface. So I don't think this behavior is a bug.

This is simply a workaround, but I'd suggest you do define spindle numbers
for the samba clients even if the defect is repaired.  Perhaps do it so
each samba client is a unique spindle number.  That way you could have
multiple dumpers, but only one per client.

-- 
Jon H. LaBadie                  jon AT jgcomp DOT com
 JG Computing
 4455 Province Line Road        (609) 252-0159
 Princeton, NJ  08540-4322      (609) 683-7220 (fax)