From: Michael Tremer <michael.tremer@ipfire.org>
To: network@lists.ipfire.org
Subject: Re: [PATCH] config: remove old hashes
Date: Tue, 04 Jul 2017 17:05:03 +0100 [thread overview]
Message-ID: <1499184303.2362.3.camel@ipfire.org> (raw)
In-Reply-To: <1499183882-24548-1-git-send-email-jonatan.schlag@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1402 bytes --]
Hi,
could we also drop the ipv6_hash function or is that used somewhere
else, too?
-Michael
On Tue, 2017-07-04 at 17:58 +0200, Jonatan Schlag wrote:
> With the new id feature the old hashes are not necessary anymore.
>
> Signed-off-by: Jonatan Schlag <jonatan.schlag(a)ipfire.org>
> ---
> src/hooks/configs/ipv4-static | 3 +--
> src/hooks/configs/ipv6-static | 2 +-
> 2 files changed, 2 insertions(+), 3 deletions(-)
>
> diff --git a/src/hooks/configs/ipv4-static b/src/hooks/configs/ipv4-
> static
> index cb00252..c395200 100644
> --- a/src/hooks/configs/ipv4-static
> +++ b/src/hooks/configs/ipv4-static
> @@ -106,8 +106,7 @@ hook_new() {
> warning "You did not configure a gateway for a non-
> local zone"
> fi
>
> - # XXX maybe we can add some hashing to identify a
> configuration again
> - zone_config_settings_write "${zone}" "${HOOK}.$(uuid)"
> + zone_config_settings_write "${zone}" "${HOOK}"
>
> exit ${EXIT_OK}
> }
> diff --git a/src/hooks/configs/ipv6-static b/src/hooks/configs/ipv6-
> static
> index 2a5e8e2..f43ef7e 100644
> --- a/src/hooks/configs/ipv6-static
> +++ b/src/hooks/configs/ipv6-static
> @@ -59,7 +59,7 @@ hook_new() {
> GATEWAY=$(ipv6_format "${GATEWAY}")
> fi
>
> - zone_config_settings_write "${zone}" "${HOOK}.$(ipv6_hash
> ${ADDRESS}).${PREFIX}"
> + zone_config_settings_write "${zone}" "${HOOK}"
>
> exit ${EXIT_OK}
> }
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2017-07-04 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-04 15:58 Jonatan Schlag
2017-07-04 16:05 ` Michael Tremer [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1499184303.2362.3.camel@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=network@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox