From owner-freebsd-hackers@freebsd.org Wed Nov 29 18:37:42 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 154FBE6556F for ; Wed, 29 Nov 2017 18:37:42 +0000 (UTC) (envelope-from leres@ee.lbl.gov) Received: from fun.ee.lbl.gov (fun.ee.lbl.gov [IPv6:2620:83:8000:102::ca]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "fun.ee.lbl.gov", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 0498A8007E for ; Wed, 29 Nov 2017 18:37:41 +0000 (UTC) (envelope-from leres@ee.lbl.gov) Received: from ice.ee.lbl.gov (ice.ee.lbl.gov [IPv6:2620:83:8000:102:0:0:0:d5]) (authenticated bits=0) by fun.ee.lbl.gov (8.15.2/8.15.2) with ESMTPSA id vATIbPK2094967 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 29 Nov 2017 10:37:28 -0800 (PST) (envelope-from leres@ee.lbl.gov) Subject: Re: sort(1) sorting IP (v4) addresses (INET_ATON?) To: bsd-lists@BSDforge.com, FreeBSD Hackers References: <1f2d985d685f66ad01ff2810cbb941c9@udns.ultimatedns.net> From: Craig Leres Message-ID: <5bdff83a-52c2-ddfb-3d8a-9d260a6e62da@ee.lbl.gov> Date: Wed, 29 Nov 2017 10:37:25 -0800 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <1f2d985d685f66ad01ff2810cbb941c9@udns.ultimatedns.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-Mailman-Approved-At: Wed, 29 Nov 2017 18:59:56 +0000 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Nov 2017 18:37:42 -0000 On 11/29/17 10:35, Chris H wrote: > I'm constantly dealing with IPv4 addresses (millions). Sorting the mass > is never perfect, and I'm forced to *visually* fix those out of order. > Yet I continue to (later) find some I've missed -- I'm sick of it! > Thus far, I've found I attain the best results with sort(1): > > sort -t . -k 4,4n -k 3,3n -k 2,2n  ./TCPLIST | sort -g>./SORTED > > Which ends up pretty damn close. But not perfect. % grep sortip ~/.cshrc a sortip "sort -t. +0 -1n +1 -2n +2 -3n +3 -4n" Craig