#119 JNameD: Automatic configuration file refresh

[Randolf C. Richardson]

Suggestion: Add the following command line parameter
to jnamed:

-a [[[[dd:]hh:]mm:]ss]

The "-a" parameter would indicate "auto-detect changes
to configuration and zone files."

Specifying a "time between refreshes" should be optional,
and allow the administrator to set the number of days
(dd), hours (hh), minutes (mm), and seconds (ss) to wait
before re-loading all configuration files (if any have
changed).

The default refresh time should be "1:00:00:00" (every 24
hours) a time frame is not specified.

Whenever this parameter is used, the "time between
refreshes" should be output on the console (e.g., "-a 2:4:
30:12): "Refresh will occur every: 2 days, 4 hours, 30
minutes, 12 seconds."

When changes are detected, the text "Changes to
configuration/zone file(s) detected. Refresh complete."
should be output to the console after the changes are
successfully implemented. If unsuccessful, error
messages should be output, with only valid changes
implemented, and still followed by the suggested
"Changes ... Refresh complete" message.

If the provision for a verbose mode (one suggested
command line parameter could be "-v") is ever seriously
considered, then refreshes should always be output even
when no changes are detected ("No changes to
configuration/zone file(s) detected.").

[Brian Wellington]

Logged In: YES
user_id=63197

jnamed is a proof-of-concept server, not something that
anyone would ever want to use in a production environment.
As such, there's no reason to add features that aren't
required for proper operation, since that might convince
people to use it where it is not appropriate.

[Randolf C. Richardson]

Logged In: YES
user_id=621016

That's too bad, but I understand.

Does anyone know of a DNS server that's written in Java?

[Ingo]

Ticket moved from /p/dnsjava/feature-requests/3/