3 msgamcheck reports amadad busy!
2 msg[Fwd: Debian predictable random number generator]
17 msg.amandahosts owned by id ## should be ##
4 msgHP/UX?
4 msgRe: Problem Restoring Files
2 msgRelease of Amanda-2.6.0p1
4 msgtapless config, rotating 2 ext hard drives

Portrange setting 2.5.2p1
\ Gunnarsson, Gunnar (14 May 2008)
. \ Dustin J. Mitchell (14 May 2008)
. . \ Jon LaBadie (14 May 2008)
. . . \ Dustin J. Mitchell (14 May 2008)

1 msgSourceForge CCA
2 msgProblem with a multi-homed client: amcheck: tim...
3 msgrequest for enhancement
4 msgproblem deleting DLE from backup
7 msgconfusing problem with NO-NEW-TAPE
5 msg/var/lib/amanda/gnutar-lists : huge !
4 msgAmcheck crashing on CentOS 5.1 x86_64
9 msgOut of space problem
2 msgamrecover: Extractor child exited with status 2
2 msgWindows Server 2003 cant execute amandad.exe vi...
3 msgCan't seem to disable software compression.
1 msgamanda 2.6.0 for CentOS
Subject:Re: Portrange setting 2.5.2p1
Group:Amanda-users
From:Dustin J. Mitchell
Date:14 May 2008


 
On Wed, May 14, 2008 at 4:44 PM, Jon LaBadie <jon> wrote:
>> > If portrange settings are changed in the server part with
>> >
>> > --with-tcpportrange=50000,50100 --with-udpportrange=840,860
>> >
>> > how does it effect the clients - do they need to be recompiled as well ?
>>
>> This affects the range of source ports used for "reverse" connections;
>> on the server, it will affect the source ports used for reverse
>> connections to amrecover. On the client, it will affect the source
>> ports used for reverse connections back to the server. As long as the
>> ranges are large enough to accomodate the parallelism used in Amanda,
>> the only implication of these ranges is for firewall rules.
>>
>> Dustin
>
> So, is that a "no, the clients need not be recompiled"?
> Or maybe "yes, unconditionally"?
> Or maybe "yes, if you want to use amrecover from the client"?

No, the clients need not be recompiled.

Sorry if I wasn't clear :)

Dustin

--
Storage Software Engineer
http://www.zmanda.com


© 2004-2008 readlist.com