{"id":17258676,"url":"https://github.com/xiaq/dhcpd-pools","last_synced_at":"2025-03-26T09:21:44.136Z","repository":{"id":5693991,"uuid":"6904476","full_name":"xiaq/dhcpd-pools","owner":"xiaq","description":"My fork of dhcpd-pools, constantly pushing to upstream.","archived":false,"fork":false,"pushed_at":"2013-04-07T12:16:43.000Z","size":660,"stargazers_count":1,"open_issues_count":0,"forks_count":2,"subscribers_count":3,"default_branch":"master","last_synced_at":"2025-03-19T19:29:41.349Z","etag":null,"topics":[],"latest_commit_sha":null,"homepage":"dhcpd-pools.sourceforge.net/","language":"C","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"other","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/xiaq.png","metadata":{"files":{"readme":"README","changelog":"ChangeLog","contributing":null,"funding":null,"license":"COPYING","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null}},"created_at":"2012-11-28T15:36:26.000Z","updated_at":"2022-07-18T11:10:17.000Z","dependencies_parsed_at":"2022-08-24T21:30:12.509Z","dependency_job_id":null,"html_url":"https://github.com/xiaq/dhcpd-pools","commit_stats":null,"previous_names":[],"tags_count":0,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/xiaq%2Fdhcpd-pools","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/xiaq%2Fdhcpd-pools/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/xiaq%2Fdhcpd-pools/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/xiaq%2Fdhcpd-pools/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/xiaq","download_url":"https://codeload.github.com/xiaq/dhcpd-pools/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":245623141,"owners_count":20645702,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":[],"created_at":"2024-10-15T07:21:31.905Z","updated_at":"2025-03-26T09:21:44.108Z","avatar_url":"https://github.com/xiaq.png","language":"C","funding_links":[],"categories":[],"sub_categories":[],"readme":"This is dhcpd-pools which is made for ISC dhcpd pool range analysis.\n\n== Quick start\n\n\t./bootstrap\n\t./configure --prefix=/usr/local\n\tmake\n\tmake install\n\n\n== General information\n\n\tWith this command you can check usage of pool addresses\n\twhen address space is great. Command is designed so that\n\tit will not get slow even there is thousands of IPs in\n\tlease file. This kind of huge dhcpd installation can be\n\tnear by DSL DSLAMs or some other public access connection\n\tpoints.\n\n\tThis command will not print nice to know information like\n\tDHCPStatus does. Output is limited only to list only\n\tusage for ranges, shared network and total address space.\n\tLimiting what is printed is the right thing to do when\n\tthere is thousands of addresses. If your address space is\n\tsmall some other dhcp analyzer might be more suitable for\n\tyou.\n\n== Dependencies to other projects\n\n\thttp://www.gnu.org/software/gnulib/\n\n\t\tIf you have gnulib checked out somewhere at file\n\t\tsystem you can avoid download by setting\n\t\tGNULIB_SRCDIR environment variable.\n\n\thttp://uthash.sourceforge.net/\n\n== Test data wanted\n\n\tMaintainer is interested to get copy of your dhcpd.conf\n\tand dhcpd.leases file, with includes if you use them.\n\tIntention is to collect large set of data to build\n\trealistic regression test environment. By giving your\n\tdata to maintainer you can be sure that updates will work\n\tfor you.\n\n\tIf you are interested to help this way put all files into\n\ttar.gz, and send them to kerolasa@iki.fi. It would be nice\n\tthat email subject line would have 'dhcpd-pools test data'.\n\n\n== Instructions for developers\n\nAUTOTOOLS:\n\n\t* \"./bootstrap\" generates all files needed to compile and\n\t  install the code (run it after checkout from git)\n\n\t* \"make distclean\" removes all unnecessary files, but the\n\t  code can still be recompiled with \"./configure; make\"\n\nPATCHES:\n\n\t* First get familiar with git. In case you are completely\n\t  lost watch Greg Kroah-Hartman explaining the very\n\t  basics.\n\t  http://archive.fosdem.org/2010/schedule/events/linuxkernelpatch\n\n\t* Get up to date version of the code base.\n\n\t  $ git clone git://dhcpd-pools.git.sourceforge.net/gitroot/dhcpd-pools/dhcpd-pools\n\n\t* Don't include generated (autotools) stuff to your\n\t  patches (hint: use git-clean [-X])\n\n\t* Add a Signed-off-by line, use \"git commit -s\"\n\n\t* Patches are delivered via email only. The following\n\t  commands will do the correct thing.\n\n\t  $ git format-patch -C origin/master..yourbranch -o ~/patches\n\n\t  When you send only one patch use the following.\n\n\t  $ git send-email --to kerolasa@iki.fi 0001*\n\n\t  The command above expects you have configured email\n\t  sending properly. See git.wiki for help.\n\t  https://git.wiki.kernel.org/index.php/GitTips#Mail\n\n\t* One patch per email, with the changelog in the body of\n\t  the email.\n\n\t* When you send series of pathes include introductory\n\t  message.\n\n\t  $ git send-email --compose --to kerolasa@iki.fi ~/00*\n\n\t  Good introductory message will have at least\n\n\t  -- snip\n\t  Your Name (3):\n\t    firstfile.c: short description\n\t    secondfile.c: another description\n\n\t   firstfile.c                         |    2 +-\n\t   secondfile.c                        |    2 +-\n\t   secondfile.c                        |    2 +-\n\t   2 files changed, 3 insertions(+), 3 deletions(-)\n\t  -- snip\n\n\t  Above introductory can be generated with git.\n\n\t  $ git shortlog master..yourbranch\n\t  $ git diff --stat master..yourbranch\n\n\t* Subject: [PATCH] subsystem: description. Following\n\t  ~/.gitconfig will help you a little.\n\n\t  -- snip\n\t  [user]\n\t\t  name = Your Name\n\t\t  email = your.name@example.com\n\n\t  [format]\n\t\t  subjectprefix = PATCH\n\t\t  numbered = auto\n\t\t  signoff = yes\n\n\t  [sendemail]\n\t\t  chainreplyto = false\n\t\t  cc = your.name@example.com\n\t  -- snip\n\n\t* If someone else wrote the patch, they should be\n\t  credited (and blamed) for it. To communicate this, add\n\t  a line:\n\n\t     From: John Doe \u003cjdoe@wherever.com\u003e\n\n\t  The sign-off is a simple line at the end of the\n\t  explanation for the patch, which certifies that you\n\t  wrote it or otherwise have the right to pass it on as a\n\t  open-source patch. The rules are pretty simple: if you\n\t  can certify the below:\n\n\t      By making a contribution to this project, I certify\n\t      that:\n\n\t      (a) The contribution was created in whole or in\n\t\t  part by me and I have the right to submit it\n\t\t  under the open source license indicated in the\n\t\t  file; or\n\n\t      (b) The contribution is based upon previous work\n\t\t  that, to the best of my knowledge, is covered\n\t\t  under an appropriate open source license and I\n\t\t  have the right under that license to submit\n\t\t  that work with modifications, whether created\n\t\t  in whole or in part by me, under the same open\n\t\t  source license (unless I am permitted to submit\n\t\t  under a different license), as indicated in the\n\t\t  file; or\n\n\t      (c) The contribution was provided directly to me by\n\t\t  some other person who certified (a), (b) or (c)\n\t\t  and I have not modified it.\n\n\t      (d) I understand and agree that this project and\n\t\t  the contribution are public and that a record\n\t\t  of the contribution (including all personal\n\t\t  information I submit with it, including my\n\t\t  sign-off) is maintained indefinitely and may be\n\t\t  redistributed consistent with this project or\n\t\t  the open source license(s) involved.\n\n\t  then you just add a line saying\n\n\t  Signed-off-by: Random J Developer \u003crandom@developer.example.org\u003e\n\n\t  using your real name (sorry, no pseudonyms or anonymous\n\t  contributions.)\n\n\t* If the the business with git is too difficult just send\n\t  source code files as is as email attachment to\n\t  maintainer.\n\nCODING STYLE:\n\n\t* The preferred coding style is based on the linux kernel\n\t  Documentation/CodingStyle. For more details see:\n\n\t  http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob_plain;f=Documentation/CodingStyle\n\n\t* Source code is pretty printed by using two, and only\n\t  the two, indent command switches -kr -i8\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fxiaq%2Fdhcpd-pools","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fxiaq%2Fdhcpd-pools","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fxiaq%2Fdhcpd-pools/lists"}