-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation for lease file syntax #74
base: master
Are you sure you want to change the base?
Conversation
Hey, Thank you for submitting a documentation improvement! I can't review the contents myself, but I am really glad to see a doc contribution. |
Is there a way to view this as HTML ? |
If accepted, it will appear at https://jenkins.isc.org/job/Kea_doc/guide/kea-guide.html Otherwise, you can clone this pull request and do:
And you'll find it under |
@nchaigne Follow the steps outline by @andrei-pavel, I understand from the |
Mmh... I'm having trouble building the guide. :/ I/O error : Attempt to load network entity http://docbook.sourceforge.net/release/xsl/current/html/docbook.xsl |
Documentation 3.3 Building Requirements
It basically says what you need to install, specifically Try it and report back? |
Thanks. (The "configure" does not check for docbook-xsl, it would be better if it did!) Now I have other issues though: Don't know what gentext to create for xref to: "section", ("read-only-database-configuration4") (etc, many such lines "no template matches") |
Maybe what I did is not correct? I tried to start from Kea 1.3 tarball and patched the modified xml files. |
Alright, so I can't read the formatted documentation, but I can still review the xml you've modified. :) I do appreciate the effort, but I feel this pull request cannot be merged in its current state. There are many typos which need to be corrected ("assinged", "clien_id", "arquire", etc.) ; one section is commented out... it sounds like you did not double-check your work. You put two unrelated commits in the same pull request. You should have done two distinct pull requests, so maintainers have an easier job merging them. (tip: before starting on a pull request, always create a branch where you will make your changes, that way you can work on different topics at the same time) And I still don't know how the last field (state) works, which is what prompted me to create the ticket in the first place... looking at the lease file I see "0", which I assume is "active". Maybe "1" is expired, "2" is released ? that's the kind of information I wanted to see. |
Thanks for the review @nchaigne , I will double check, I'll fix the 1 and 3 you raised, for 2 I should have created the branch to the project here instead than in my fork. |
Added documentation for DHCPv4/DHCPv6 lease fields, It solves ticket #5164