hi,
I have to location databases - one called 'location' used for saving REGISTERs and one called 'aliases' used for aliases. usrloc insists on expiring entries from 'aliases' even though the expires field is set to NULL. is this desirable? I would prefer if NULL expire values where left alone for manual expire.
if we like to change this, I can create a patch.
jakob
Sounds like a reasonable sanity suggestion.
It is unlikely to show in the current SER branch soon though. Our major objective now is to keep SER stable and limit any changes to SER to code fixes. Till then, I think people can live with maximum value (which will expire in something like 14 years I guess).
-jiri
At 02:33 PM 9/14/2003, Jakob Schlyter wrote:
hi,
I have to location databases - one called 'location' used for saving REGISTERs and one called 'aliases' used for aliases. usrloc insists on expiring entries from 'aliases' even though the expires field is set to NULL. is this desirable? I would prefer if NULL expire values where left alone for manual expire.
if we like to change this, I can create a patch.
jakob
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-- Jiri Kuthan http://iptel.org/~jiri/
Hello,
Actually I plan to move aliases away from usrloc completely. We use usrloc for aliases only because it was the fastest solution.
Jan.
On 14-09 14:33, Jakob Schlyter wrote:
hi,
I have to location databases - one called 'location' used for saving REGISTERs and one called 'aliases' used for aliases. usrloc insists on expiring entries from 'aliases' even though the expires field is set to NULL. is this desirable? I would prefer if NULL expire values where left alone for manual expire.
if we like to change this, I can create a patch.
jakob
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers