In message <002101c8b4a1$49d3a2c0$dd7ae840$@firstname.lastname@example.org> on 05/13/08(11:30:19)
you "David Wang" <email@example.com> wrote:
|Thanks a lot for information.
|But I tested for a while, and found when I add new IP address/hostname
|prefix with '-', it will bypass name resolution, but it's not working,
|client side get "unmatch PERMIT" error.
I don't know the reason why the error occurs and can't reproduce it.
|I still need to remove the prefix
|'-', then restart delegate, then working. The new IP address added must be
|resolved, otherwise no working, please see the permit config file and
|error.log: 05/13 12:00:45 -P443 E-P: No permission:
|CPE-58-160-64-204.vic.bigpond.net.au:46502 => http://127.0.0.1:8080 (unmatch
|If the name resolution (or reverse resolution) is necessary, how can I avoid
|long time taken by restarting delegate when adding new IP address permitted?
|Is that possible not to do name resolution (don't refresh them) for the
|IP/hostnames already existed in Hostlist? Only do name resolution for new IP
|address added to save restarting time?
Maybe the easiest solution is resolving your clients not with DNS but
with local /etc/hosts file. If the /etc/hosts file is not desirable
to be added, you can use your own hosts file (/tmp/myhosts for example)
and specify like RESOLV="file:/tmp/myhosts,nis,dns,sys".
9 9 Yutaka Sato <firstname.lastname@example.org> http://delegate.org/y.sato/
( ~ ) National Institute of Advanced Industrial Science and Technology
_< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
Do the more with the less -- B. Fuller