I think someone mentioned an exclude list as a possible solution to this
problem.
What about an include list instead (or in addition to the exclude list)?
I'm envisioning something like CellServDB, but without the actual DB info
-- that is effectively a list of robust and/or often-used cells
On 8/13/2014 10:35 AM, Stephen Joyce wrote:
I think someone mentioned an exclude list as a possible solution to this
problem.
What about an include list instead (or in addition to the exclude list)?
I don't think you are asking for an include list but a configuration
option to disable
On Wednesday 13 August 2014 11:05:02 Jeffrey Altman wrote:
On 8/13/2014 10:35 AM, Stephen Joyce wrote:
I think someone mentioned an exclude list as a possible solution to this
problem.
What about an include list instead (or in addition to the exclude list)?
I don't think you are
* Jeffrey Altman [2014-08-13 11:05:02 -0400]:
I believe that what you are asking for is not an include list but an
option to only perform DNS SRV/AFSDB queries for entries that exist in
the CellServDB without a server list.
Please remember to also fix bug #131895 if/when this is implemented.
On 8/13/2014 3:19 PM, Sergio Gelato wrote:
* Jeffrey Altman [2014-08-13 11:05:02 -0400]:
I believe that what you are asking for is not an include list but an
option to only perform DNS SRV/AFSDB queries for entries that exist in
the CellServDB without a server list.
Please remember to also
Well, what you describe isn't exactly what I was proposing, but I'm not
picky and what you describe seems like it could work okay and might even be
easier (dare I hope trivial?) to implement...
Cheers,
Stephen
On Wed, 13 Aug 2014, Jeffrey Altman wrote:
On 8/13/2014 10:35 AM, Stephen Joyce
On Wed, 13 Aug 2014 17:45:17 +0200
Markus Köberl markus.koeb...@tugraz.at wrote:
What about an option to change the behavior of 3. to:
3. If no server list was found in CellServDB and afsdb lookups are
enabled, use DNS SRV/AFSDB records to try to find a match only if
the search
