Event ID source incorrect for BIND 8.2.3 NT port

[Joe Rhett]

I'm helping a site implement the 8.2.3 NT port, and I stumbled across a few
issues that should be simple to fix (but are beyond my NT programming skills)

1. The source sent to the Event system in NT is incorrect. The source being
sent is the full invocation path (which would be $0 in Unix) instead of
just the executible name. The source specified in the error message is:

	C:\WINNT\System32\dns\bin\named-xfer.exe

If one invokes it by hand it sends whatever the invocation path was, eg.
	named-xfer.exe
	.\named-xfer
	bin\named-xfer

The proper source should be 'named-xfer'. I have validated that the
installation program sets up the registry entries correctly - using a test
program that sends messages with a source 'named-xfer' produces the proper
output in the Event Viewer, as does executing the program on the command
line with only "named-xfer".

This should be a trivial fix.

2. Is there any reason why the BINDCtrl program isn't a Control Panel
applet? Setting up a program group for a single app doesn't make much sense.

3. Is there a reason why the BINDCtrl program doesn't have a 'restart' option?

-- 
Joe Rhett                                         Chief Technology Officer
JRhett at ISite.Net                                      ISite Services, Inc.

PGP keys and contact information:          http://www.noc.isite.net/Staff/