From nobody Sun Aug 6 01:34:30 2023 X-Original-To: hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJMSZ1Jp0z4m8l9 for ; Sun, 6 Aug 2023 01:34:38 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJMSZ0kKkz4G6Z for ; Sun, 6 Aug 2023 01:34:38 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691285678; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=ebB82ZvSiCSqgtTyAN41jDRo86QjPP9NEtGq+u60pHk=; b=E7pUmrF47cGk3FNscpPS5viujDSEXaFRKmDYmNHUu1LXmQYLN/7hSk/DL5AiNZ0MSurenJ nqvecdLTUBLXm+Hlg4DVcBDmu9DswIhwLE1zgJo9oKEE23G52/HajcfZ6x/f4XqNoqhV2n C6gRrOsW1s+L5zBJ0Ahz3xbZWdO2UuQkmM+X58rjjjFoR9/9BFhwGLHyLqkbLlzpe0JeVL NfgewYHz0MGwSNiv8eegTensFpk6WmTEwYGf+j63/bo2i4ESBoKglpD2Mb3skXSgM+S+iX o9mc9a3AbXdiG0naxeacvceBv4amgNqZJ4n38/HypDKPwUY6LjpOcgdbshh8Xw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691285678; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=ebB82ZvSiCSqgtTyAN41jDRo86QjPP9NEtGq+u60pHk=; b=ojpGAVNFBEuYLv5yeKcLg2+9lEAwAhj9wNtZ/Ao5JXbMi5Mh1AogZnEYkEoe87T4Y/q1PI GEDNdOD8NN5HBYOQX4MKGC8Yga9gpnCiLKZy8bPBfz86JssROgbM7AiMBj6cYMxyDpPq67 3BKXif8/KmHHQzgy+NhAozUB5+FKuDnj4Mdu/bzlGmiA/2ZWq6N0VNGyhifNQ3SIDeL8ZH IGnM64vcxlvdb2z9F2fPLiZ4PcJ73qBD0bVrH2Ag0x3wy1BTbwhBhE2fMqxnJFpN4HHQCj 3Xtg5SqO6CF1Le0biHb1J/209p8u8QUaW1aWB229di+deuN80AUWb3hO+ficIA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1691285678; a=rsa-sha256; cv=none; b=R31kPN3XQEmfs/Rdbm1FKfTVPi2MuBKvEW0kn3DlZ4UwAGqWgaOSeoFE0QvnlnOc19PcBV Y2gDvhvZ2vzW7huJ63Wln4rgs2LaKZacRJ5+cc8tP61Vhlwi1dYKZJ+ey6OKgaHefUs4LO 5oTO24chQMM7fnwzIxkdsPcehtX5NNvmPaBEiUGMrljdu6P5yUeF3RBR8Mx8K3AtSBZTcQ JNTcDJefJcS6y13GC54aZX/n6b2lpdsBtyoZsQZZxiWa8hzXZcYBw2j0lt0InTmbeq+gTT fAePDXMfdkjq0zVJqiFwyKShF6IE3bRqWXCNWEvBi0boQRBYuLHPb59E3QsbTw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from [192.168.1.10] (80-42-66-93.dynamic.dsl.as9105.com [80.42.66.93]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4RJMSY4zmgz1hp9 for ; Sun, 6 Aug 2023 01:34:37 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> Date: Sun, 6 Aug 2023 02:34:30 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.1 To: freebsd-hackers Content-Language: en-US From: Graham Perrin Subject: demandoc(1) Organization: FreeBSD Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------RlJeTkBhGcxpRPHTwLqgz0fa" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------RlJeTkBhGcxpRPHTwLqgz0fa Content-Type: multipart/mixed; boundary="------------3GmuISvQG1dAqXGl0YRheG9L"; protected-headers="v1" From: Graham Perrin To: freebsd-hackers Message-ID: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> Subject: demandoc(1) --------------3GmuISvQG1dAqXGl0YRheG9L Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 PGh0dHBzOi8vbWFuZG9jLmJzZC5sdi9tYW4vZGVtYW5kb2MuMS5odG1sPg0KDQpBZGRlZCBp biAyMDE0LCByZW1vdmVkIGluIDIwMTU6DQoNCjxodHRwczovL2dpdGh1Yi5jb20vZnJlZWJz ZC9mcmVlYnNkLXNyYy9jb21taXQvMjQyMWI5MGY0Nzc1MGNiNjM0ZWZlZjcwM2M1Zjg4YjNk MzBiMmVlMT4NCjxodHRwczovL2dpdGh1Yi5jb20vZnJlZWJzZC9mcmVlYnNkLXNyYy9jb21t aXQvN2IwODk2ZDg4MjhjNGJhZDllZDExOTBkYTVmNjIwNGEzNDkyMzFmMz4NCg0KSSBhZGRl ZCB3aGF0IHdhcyByZW1vdmVkLCBidXQgaXQgZGlkbid0IGJ1aWxkLg0KDQpIb3cgZGlmZmlj dWx0IHdvdWxkIGl0IGJlIHRvIGhhdmUgZGVtYW5kb2MgaW4gYmFzZSwgYWdhaW4/DQoNCkZv ciBub3c6IEkgaW5zdGFsbGVkIGZyb20gc291cmNlLCBpZ25vcmluZyBhIGNvbmZsaWN0IHdp dGggDQovdXNyL2xvY2FsL2Jpbi9zb2VsaW0sIHRoZW4gcmVpbnN0YWxsZWQgZ3JvZmYuDQoN Cg== --------------3GmuISvQG1dAqXGl0YRheG9L-- --------------RlJeTkBhGcxpRPHTwLqgz0fa Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmTO+KYFAwAAAAAACgkQt2dIb0oY1AvZ YBAAkTzmrxc99o/LpQrRtyMae0U4WN5Kl0rKH+Wq9eZ+NjP5T2sGCvc5cWYgM462Hb/RSS3EpwaR /lW89pxGjn8qSgGmTYL/5HdqURSyxnns3h0wYUZ9Af7groKET+3Mb4Xvg9lb7qaXmHGfvUZZDSjU GSgI6H1cMS84cQR9q4IFBRGWBucIgoXv4exH2Ffqvt+AJ9UX02J1LUowEMEv4qHMcITRWzM+/O7n owq3nbXmq88NNUdYjqsVjnyVvT8wFtSEEp8RICeyrKzknPLkci1niHfP+VEJTLkjEfpWztGI6UHM Yxw0PV/ovdhKYfBdkpMY8pPOzy+o8tl55vnspgqK+J79lSCykswvfX5zvr34pwrt2S4o/06634P5 HtkuIkzRxZ4jHH5Ln5uDNNZrzI8bA+ZQeQuRL+KVUu4P4/Rx2DkqPNvotAfMcrhZBUgkBfYtRrbH iwSnKaHzMaGJ39uo+JeTGGm8t9PIa1i/9JYUIHhxEditzkh4SkYyUs4YKiqx9hE610P4rHg6Rgog yNwYuWu84PnMwBqTJVrcZkM6yvTynGjuco00z19BO/sbSvBeMyaDQ6HdbJ4uwqoILCxlQbL70SMU fdTBy26x5j4bZdmSGfO0wOQY3Uol7iddbdDgSlMWbV0V9MwXdduNSVf+tcP4M2iJ9URThEHkHVvl Ac0= =zoSv -----END PGP SIGNATURE----- --------------RlJeTkBhGcxpRPHTwLqgz0fa-- From nobody Sun Aug 6 05:13:47 2023 X-Original-To: hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJSKj0kSGz4mQS0 for ; Sun, 6 Aug 2023 05:14:01 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pf1-x429.google.com (mail-pf1-x429.google.com [IPv6:2607:f8b0:4864:20::429]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJSKh578fz4X3k for ; Sun, 6 Aug 2023 05:14:00 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x429.google.com with SMTP id d2e1a72fcca58-686be3cbea0so2982099b3a.0 for ; Sat, 05 Aug 2023 22:14:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20221208.gappssmtp.com; s=20221208; t=1691298839; x=1691903639; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=VyHKLgqsaHmw/sli2BgEkMODE6xG0kDd0+9Qucx3mLc=; b=o8U7+VcgzBYpMtviTCCSzPaAHD76HNJcd5ZbtVakxcAXKnW2iiqoeFr8b3MeuShA5B pVybP+3SpXhFrqr4jJV+KBgtj26A/vZwih18NF4ms0OY3QC0ZlkwM0kXsmEOaIe7T0Br aLqgFdVewcJxtZofigL93Ip7G8pfB0FkNmDEnzBO77xxnXRY4KtzeOUkSgweXYqfmFEy 2Nsv+b5WX6XU5W54ZfavJQmQf3tZ+sSHKgZYRmedfQNJC7tQGXaTWX3BwajXvT645IbN ZUrk07IlCK7LX2wx1pXeUIqtdvVLeg84IoiX1foF89zgPSg3P3Q6FqmwxBzKpTS5UfzO mvtA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691298839; x=1691903639; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=VyHKLgqsaHmw/sli2BgEkMODE6xG0kDd0+9Qucx3mLc=; b=aXwKbKnVMmD6NG8uu28dBPcRIdHrXF6ooNvYymH/u+1Ep+GVJn7RMs+SFdpILEn613 vJ91Y+Azwh8DV3yxeyKIjSTlTj6/JU+TJzPZ2ySWqSyzDwdcchLmjTdtLghjWrtB3PEm TU/6bwznGkSNf45FU9PElkD51u4MCJUN9vbdqyhg/Y+Q8GfVw7UREdmQ4GqVtqnNTr0e ZxqvGt1a4e/RS8kPd+atubc5BZ8hbySLXC1KiQtPAcAJaK25Pphp+zeQ73K6M1gm0/q/ kBEdXxzuvcsQo0+jq5FeV9f7YSylM9+LRweeZ4OQSAC9ZW1iKH7dQTY7EuinsoPIyU29 45MA== X-Gm-Message-State: AOJu0YxmElsJuk4EoARTZWxvgoM1x/iIO4PySXbYnTo3/dMv1Xf7eR0Z 29ew1qyLgC7OaAf/lECJ8uCfUogi0me3TzdJZ2Q= X-Google-Smtp-Source: AGHT+IHbz7K0nfMbthTqbJtvpEGvBnA13x1MBoc2t+/diaTUtkEJU+C9ghxuMpwRY1Xt08X6zgK11w== X-Received: by 2002:a17:90a:4f81:b0:268:e30e:e92f with SMTP id q1-20020a17090a4f8100b00268e30ee92fmr4833156pjh.18.1691298839059; Sat, 05 Aug 2023 22:13:59 -0700 (PDT) Received: from smtpclient.apple (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id l12-20020a17090aec0c00b002677739860fsm3717835pjy.34.2023.08.05.22.13.58 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 05 Aug 2023 22:13:58 -0700 (PDT) Content-Type: text/plain; charset=us-ascii List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: demandoc(1) From: Bakul Shah In-Reply-To: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> Date: Sat, 5 Aug 2023 22:13:47 -0700 Cc: freebsd-hackers Content-Transfer-Encoding: quoted-printable Message-Id: <79117D20-0A32-4548-9250-27CCF6650403@iitbombay.org> References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> To: Graham Perrin X-Mailer: Apple Mail (2.3731.600.7) X-Rspamd-Queue-Id: 4RJSKh578fz4X3k X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On Aug 5, 2023, at 6:34 PM, Graham Perrin = wrote: >=20 > >=20 > Added in 2014, removed in 2015: >=20 > = > = >=20 > I added what was removed, but it didn't build. >=20 > How difficult would it be to have demandoc in base, again? Isn't deroff good enough? From nobody Sun Aug 6 10:12:04 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJZxk5WPmz4pnFR for ; Sun, 6 Aug 2023 10:12:10 +0000 (UTC) (envelope-from yuri@aetern.org) Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJZxk1qJ8z3d2M for ; Sun, 6 Aug 2023 10:12:09 +0000 (UTC) (envelope-from yuri@aetern.org) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=aetern.org header.s=fm3 header.b=PDReqlHi; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=FRPvnPvP; spf=pass (mx1.freebsd.org: domain of yuri@aetern.org designates 64.147.123.19 as permitted sender) smtp.mailfrom=yuri@aetern.org Received: from compute6.internal (compute6.nyi.internal [10.202.2.47]) by mailout.west.internal (Postfix) with ESMTP id AEDE7320090E for ; Sun, 6 Aug 2023 06:12:07 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute6.internal (MEProxy); Sun, 06 Aug 2023 06:12:07 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aetern.org; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1691316727; x=1691403127; bh=uf DX7gsDJlEKuyrf0CEYtVQyXwP5NenMP+BfkUd1B2E=; b=PDReqlHiSJG0zIJMQZ RrGpkd9DyXa7JDQj1blXjsfLhTggmFY+c5dZGmkqIRDiZfetHsQsplXMJauS9Dyw 85HQi9M4W90KpaFaVJ4dvTCcMQhjhMZEJ9L4YmwEKTHOSD2u+YL52PdiKj/8TOen Opzmny8UGADjimMMlkxzEe4noo7GspcdL+7NK6CpatfWbH3Wi+W15bITsJeOdHMw 2oBqHrjxFquuth7odYMOK6GuSLMibwibnjQW/aAtybGcFI4Blpy37tKtqDjmQVmI /U8oOLMiQtk7tXOUu1ILEZxcMa6oWLWLdhvkm0zD0N1Fmh0cBwzq4lqsDEzCN6NR HqUg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1691316727; x=1691403127; bh=ufDX7gsDJlEKu yrf0CEYtVQyXwP5NenMP+BfkUd1B2E=; b=FRPvnPvP/bAgwfmPYfcJ06Eurk5G3 hD0dTFzNXW1ozjkaweFGrdyLW/6uQvE1/Euo+qmyz1Qgc0w5771M0o90JOcWZN0q 2BcbSXYRYTnUPpjXeUdKyruUUX7mYlwaWfY+liV1Mtnu6Xrk5XEDe8j0vGtLxUO6 6oa2/0+PfqN9Anyi06iPlIRmMrYroKSQHVhzU9vankZXA86oqIEWktmmqRHF+IPA ifx71lOmidn5O4IC6LDDPlfytj/KpkKUH2UYE0jQGLq4paXCSpiQyTxHpXfdgvsD PZSegysYmCvzzexU4qfLIZ8Oxh7gzczj6M5NeZWHa1KW4EJZ5iij9Yo/w== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrkeekgddvhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptgfkffggfgfuvfhfhfgjsehmtderre dtvdejnecuhfhrohhmpegjuhhrihcuoeihuhhrihesrggvthgvrhhnrdhorhhgqeenucgg tffrrghtthgvrhhnpeeivdehiedvleffvedvuedvudfggeevteegueehvddujeeggeeile ffjeejfeffleenucffohhmrghinhepsghsugdrlhhvpdhgihhthhhusgdrtghomhenucev lhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpeihuhhrihesrg gvthgvrhhnrdhorhhg X-ME-Proxy: Feedback-ID: i0d79475b:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Sun, 6 Aug 2023 06:12:06 -0400 (EDT) Content-Type: multipart/mixed; boundary="------------zwQrspEXgbAcWJpqtf5y047W" Message-ID: Date: Sun, 6 Aug 2023 12:12:04 +0200 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: demandoc(1) Content-Language: en-US To: freebsd-hackers@freebsd.org References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> From: Yuri In-Reply-To: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> X-Rspamd-Queue-Id: 4RJZxk1qJ8z3d2M X-Spamd-Bar: / X-Rspamd-Pre-Result: action=no action; module=multimap; Matched map: local_wl_from X-Spamd-Result: default: False [0.71 / 15.00]; MIME_BASE64_TEXT_BOGUS(1.00)[]; R_DKIM_ALLOW(-0.20)[aetern.org:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.19]; MIME_BASE64_TEXT(0.10)[]; XM_UA_NO_VERSION(0.01)[]; HAS_ATTACHMENT(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; local_wl_from(0.00)[yuri@aetern.org]; FREEFALL_USER(0.00)[yuri]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; DKIM_TRACE(0.00)[aetern.org:+,messagingengine.com:+]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US] This is a multi-part message in MIME format. --------------zwQrspEXgbAcWJpqtf5y047W Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Graham Perrin wrote: > > > Added in 2014, removed in 2015: > > > > > I added what was removed, but it didn't build. usr.bin/mandoc now builds everything in instead of having a separate library, so usr.bin/demandoc has to do that as well, sample usr.bin/demandoc/Makefile attached. > How difficult would it be to have demandoc in base, again? > > For now: I installed from source, ignoring a conflict with > /usr/local/bin/soelim, then reinstalled groff. --------------zwQrspEXgbAcWJpqtf5y047W Content-Type: text/plain; charset=UTF-8; name="Makefile" Content-Disposition: attachment; filename="Makefile" Content-Transfer-Encoding: base64 LlBBVEg6CQkke1NSQ1RPUH0vY29udHJpYi9tYW5kb2MKClBST0c9CQlkZW1hbmRvYwoKV0FS TlM/PQkJMQpDRkxBR1MrPQktSSR7U1JDVE9QfS9saWIvbGlib3BlbmJzZAoKU1JDUys9CQlh cmNoLmMKU1JDUys9CQlhdHQuYwpTUkNTKz0JCWNoYXJzLmMKU1JDUys9CQljb21wYXRfcmVj YWxsb2NhcnJheS5jClNSQ1MrPQkJZGVtYW5kb2MuYwpTUkNTKz0JCWVxbi5jClNSQ1MrPQkJ bGliLmMKU1JDUys9CQltYW4uYwpTUkNTKz0JCW1hbl9tYWNyby5jClNSQ1MrPQkJbWFuX3Zh bGlkYXRlLmMKU1JDUys9CQltYW5kb2MuYwpTUkNTKz0JCW1hbmRvY19hdXguYwpTUkNTKz0J CW1hbmRvY19tc2cuYwpTUkNTKz0JCW1hbmRvY19vaGFzaC5jClNSQ1MrPQkJbWFuZG9jX3hy LmMKU1JDUys9CQltZG9jLmMKU1JDUys9CQltZG9jX2FyZ3YuYwpTUkNTKz0JCW1kb2NfbWFj cm8uYwpTUkNTKz0JCW1kb2NfbWFya2Rvd24uYwpTUkNTKz0JCW1kb2Nfc3RhdGUuYwpTUkNT Kz0JCW1kb2NfdmFsaWRhdGUuYwpTUkNTKz0JCW1zZWMuYwpTUkNTKz0JCXByZWNvbnYuYwpT UkNTKz0JCXJlYWQuYwpTUkNTKz0JCXJvZmYuYwpTUkNTKz0JCXJvZmZfdmFsaWRhdGUuYwpT UkNTKz0JCXN0LmMKU1JDUys9CQl0YWcuYwpTUkNTKz0JCXRibC5jClNSQ1MrPQkJdGJsX2Rh dGEuYwpTUkNTKz0JCXRibF9sYXlvdXQuYwpTUkNTKz0JCXRibF9vcHRzLmMKCkxJQkFERD0J CW9wZW5ic2QgegoKLmluY2x1ZGUJPGJzZC5wcm9nLm1rPgo= --------------zwQrspEXgbAcWJpqtf5y047W-- From nobody Sun Aug 6 11:32:51 2023 X-Original-To: hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJckt1Fkjz4ptfp for ; Sun, 6 Aug 2023 11:32:54 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJckt0Ycrz4G5h for ; Sun, 6 Aug 2023 11:32:54 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691321574; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UxrVNwKTFyR3USCgcWo7qXgGAMFVDyNZSy7tGDpUMLk=; b=BJJ3x1EXImPM0H/xt3GwRI/MmIax/OA8z4661ZUcxXVKndPEjGo8Zzte/BzSC8QWsocmFm sG5JmR0Ydi1jVbC16g3AbF+o62X9nKCgAr5/ypy/FSSGRHS01a9x6ySCSxvmUw9SAPV7sV ZadEpyWZUECopplknVrmR0v8+VT11l2/0TqXqTCY4eoEoN6wryQwTRr84ff7701PWXbSAv 2hUVcVCEeh4lDguANKjbU8JLz8AqPjUR410Prvhk4LDOhGbnNLfp9apR5YPxdGvJmPn3jj RLKVskqD+qIYBeAMuIFpPwjzmYSQ4UYXCEfxtCnQfDhz3qvBizL5YsyMTflDEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691321574; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UxrVNwKTFyR3USCgcWo7qXgGAMFVDyNZSy7tGDpUMLk=; b=NRsey5E1NzbN2So1lQZN3KFte8sOZFhO103XENAchvKqqmPDplQTH0fU4weA2l1iKw23td DVMQOx7WUqeUlcKckvmtelcTUACmBrXVQQBYUmTzqMH1RDpXWmLGclMiVKhK56dlcx3Nmz fIEFK38jFW2Wxp2pBrNdl5Yc2PnsqicdsnjUE4GCRZTkMYWhfDy1SSPupfLYLZ0C6fy3li 9ruY2VgdYckvSjdezVOolSPQgaLiLHOYasOiQ0Y745OwQkbGY79PJdDBtMTycOsb1qYkoU hi1QSk62UMPi77AI976PpggWIHg/B1sxQuWiSSFrgPxaEMlMmMzx6lASV4AaXg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1691321574; a=rsa-sha256; cv=none; b=ga9QxnVQaaH/YmPlr8hTMZMDTWzPeCjhAZb26/3la4Rq7s6C0L8sfe5daW5vuJzNfzv1VT oM9WcnAlKcuKFslaMWtKWX/Kzi19RfmliXamHaq5cacCveCXbj0UKE49QpUbNz+sJw/VWK BP8ErONqR8Y/Rq6E2z3N0cOtlzGLkpOHrw9QO2eRqBZG5aLWshYDcF5mpOEeNLEYFA5KQg xAcuEBr9Gd1xLozNfbflhdV2sM+MxKxVkiUKW57YtKTIR+GpmlkyPzAJ7W/26b5b4TjK+K cBgMMusW+uhf6E9l7B01pw1SCxO6bYntoTjIa7gXbIWKpAn/8klJC/0aDeQQlQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from [192.168.1.10] (80-42-66-93.dynamic.dsl.as9105.com [80.42.66.93]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4RJcks5GLyz8q7 for ; Sun, 6 Aug 2023 11:32:53 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <238083d9-c937-930c-9f15-7f8708c4205a@freebsd.org> Date: Sun, 6 Aug 2023 12:32:51 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.1 Subject: deroff(1) and deroff (1b) with mdoc(7) (was: demandoc(1)) To: freebsd-hackers References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> <79117D20-0A32-4548-9250-27CCF6650403@iitbombay.org> Content-Language: en-US From: Graham Perrin Organization: FreeBSD In-Reply-To: <79117D20-0A32-4548-9250-27CCF6650403@iitbombay.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit >From : > … Most existing FreeBSD manual pages, and all new ones, use the > mdoc(7) form … On 06/08/2023 06:13, Bakul Shah wrote: > … > > Isn't deroff good enough? Interesting, thanks. deroff(1) /usr/local/heirloom/usr/5bin/deroff is potentially more useful than deroff(1b) /usr/local/heirloom/usr/ucb/deroff however deroff(1) removes a little too much; . deroff(1) in Plan 9 from User Space has: - a manual page that differs from deroff(1) and deroff(1b) in the Heirloom Toolchest - the same glitch (below). % cat /usr/src/share/man/man8/rc.8 | grep Operation\ of .Ss Operation of Nm .Ss Operation of Nm rc.shutdown % /usr/local/plan9/bin/deroff /usr/src/share/man/man8/rc.8 | grep Operation Operation Operation   rc.shutdown % From nobody Sun Aug 6 12:36:20 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJf863sfpz4q037 for ; Sun, 6 Aug 2023 12:36:22 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJf863L6tz4QJy for ; Sun, 6 Aug 2023 12:36:22 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691325382; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SUM5tgle6dSJVZVb46fn3MI2GkiCrg2CfAHCeg9H1OY=; b=yZq/m64i2jyfTnDJQmG5x4atWJR4aDE6kvCKe1sUr8cCNoEEYGyg+DsvHWFV0askHrAhUx h5sMeAoIi3ybJQFvrU79X1z0F/XQZZ98ehHtWktVAf1HVxSkYmm7qKp60m9TC9vJ9hGPF0 V+EnoBtpsHVHEBGaOrBKZROaQrO7aDKFQblzMgvs4533/bY69/aBg6sw6D92BjEGekWphB t8Terg8/DsT2l+G/sC4qNhxvqKmJr02RvTG1zvh50KCHqlZR7EHLVqnAeGJQ11fBCTTXV0 Zhf7sXFWis5Z0T6KfuesTg1Bu27wFMT7CKpeob8uvii3j1WdYcYhBN/x20bTXQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691325382; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=SUM5tgle6dSJVZVb46fn3MI2GkiCrg2CfAHCeg9H1OY=; b=bGM+fKRMiHBpz2wAiuo7KQ7UeNH/z5ITCmDJ1H4C1InLwGfOnl5bNUjNTQAbpuLKsq1EJ8 VY3luJX28Uc93ofvIKKVgcBWjOleNyt4vc9nKh5nprfZcBIqxPZJaEBMf7Bj4p8fOXfQeo zO/Mv6TzUEPWlO1wJ81kieZtWcHvYck0o2A4XEx+8i2CM//+xEiR8eN0zf6E2+5b7MkRAu PYWyF7lwV3OGZ98+H0aobk642PBLi8eZVeDbUrh6P4/ozuo6HsfqncIFbym3kk+QiJsWPQ 3d4egjGSb1ix30s+Gw9V/PzIWHlpOkP7eHOzbuKsoFIuLku4l1rV1P8xyBQXvg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1691325382; a=rsa-sha256; cv=none; b=ufpDY5jOe1HZ7v9YTbZIN1MSog/V9Wy+tjD/0xlDX0EDOHHmDkrCIgKg2cqxlWrEda/1Uu WSkkwz4eJWOh3u6e3FsZIWV6v0j1nKD09W6asf4RNAMGkkM7zVR4r59OmOATxQ+/O8eg6h dGwKPc4HzOz2qLr6SfKQisi2n3f0sR7Z//fMi0yWgCNoZOHA027oCYtXmqxcBmKbuvtpCg aWFFuSF1MmKXycS6Lvur+MFqVizTrjpbAUtDlfXdnHaaTlJcQsmEYQv2loVTKny35/Mjde KuAcJIPrrWsm6VNhpaAx3OzzbetHwHtQ6BEp+V+hhLH7HUBOLq15QlqMBRyS0g== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from [192.168.1.10] (80-42-66-93.dynamic.dsl.as9105.com [80.42.66.93]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4RJf860Twdz9g0 for ; Sun, 6 Aug 2023 12:36:21 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <9911e4cf-3498-4221-6ba4-e7cea34f7606@freebsd.org> Date: Sun, 6 Aug 2023 13:36:20 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.1 Subject: Re: demandoc(1) To: freebsd-hackers@freebsd.org References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> From: Graham Perrin Organization: FreeBSD Content-Language: en-GB In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 06/08/2023 11:12, Yuri wrote: > … sample usr.bin/demandoc/Makefile attached. Success, thanks: % man -P less 1 demandoc % which demandoc /usr/bin/demandoc % file /usr/bin/demandoc /usr/bin/demandoc: ELF 64-bit LSB pie executable, x86-64, version 1 (FreeBSD), dynamically linked, interpreter /libexec/ld-elf.so.1, for FreeBSD 14.0 (1400093), FreeBSD-style, stripped % demandoc -w /usr/src/share/man/man9/intro.9 | spell -b | less % demandoc -w /usr/src/share/man/man9/intro.9 | aspell list --encoding utf-8 | sort | uniq | less % Re: – where the '--mode=nroff' part of the aspell(1) example will have little or no effect in most cases – it will be preferable to have aspell present everyday language, without markup. For as long as there'll be no aspell filter mode for mdoc, demandoc might be the best workaround. I can, for example: demandoc /usr/src/share/man/man9/intro.9 | xclip – and then use the context menu of the system tray icon for my local LanguageTool server. The result, pictured: . I spent a few hours searching, can't find a way to make combined use of demandoc with the check command of aspell; for aspell to be interactive with a markup-free, human-friendly view of an mdoc page (not a word list). If anyone has a solution in mind, I'll raise the question in Stack Exchange. From nobody Sun Aug 6 15:27:46 2023 X-Original-To: hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJjy82cBSz4Ttl7 for ; Sun, 6 Aug 2023 15:28:00 +0000 (UTC) (envelope-from bakul@iitbombay.org) Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJjy75Nl2z3LQJ for ; Sun, 6 Aug 2023 15:27:59 +0000 (UTC) (envelope-from bakul@iitbombay.org) Authentication-Results: mx1.freebsd.org; none Received: by mail-pf1-x431.google.com with SMTP id d2e1a72fcca58-6873a30d02eso2431452b3a.3 for ; Sun, 06 Aug 2023 08:27:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=iitbombay-org.20221208.gappssmtp.com; s=20221208; t=1691335678; x=1691940478; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=tlE/zy0zrbtJFVJaawo7xKVVCLdnvTtImB/9UVJSF/A=; b=FRZyCjvNui4MwHpcy6iRlh6wQWarf6WFab2S/wBH0HV4ztR1JDIGcMXRluYbfPdmYO 2xjHL1cne8cTsyFjjSC2Ne6y/aO8I7uPBsvu9QEUye2wsBccJFwgIYQYkGPcyAVXeuGB hzVnTlvq4PA6uhMdDJcj3R2m+lE4rsIM97UzPXO2dw62ycK6weCcR4PeTjC4Gs+kCBxz sWGUbN+dYhzOsyd7bjyQWFza5SLf1U/dwFX/2UsCBXMAyQ+ibpQhM1M/cDZ+LKzCoRkm KrXHsQh6ZE92azVF5sKId6JgZestsFwM+7FKTA/6ZFMxogd1ie8TRCBlvSWniHbFx0UQ Jqkg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691335678; x=1691940478; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=tlE/zy0zrbtJFVJaawo7xKVVCLdnvTtImB/9UVJSF/A=; b=fHsdbE6t2E4v2mAOXpw7JSHGBjr57faRU3x+q3mUQHhVVO7iSYf/JIHff9uQqxvPH4 uy7sTokf+H5Re1eOtb+3ZYgy8O20HaGTR6GlwZl/Txc5Rilmse/APRqBx/QxV9JNt5pO nf2wqlwxKEbL30KhTdKaSpb5UJ3v9vqPsqXI1LW7ejC8j6Lj1FliebcI8xxl1LJpz4F8 zuCtI1bhowh0P+31YEM635wGS8HMZYF2kk4mj4ep/ELWcj63sd9IrVPP2hy0tuDhxZDk dnZeqdKUktyHPmbqFPJY5LrfDnYceymIGX22mNTDOqL8r0FvZYUPARfp/LCWD2UOwK07 Kk+g== X-Gm-Message-State: AOJu0YzGtOVkGZ+7+YPn0yHd3NOWAuf5xKOHlWQ+6J2X+2rjo1QD5m4m n/69VJYwNa8nzNihWbpKU7Frs7wJwpOQgWk8vnU= X-Google-Smtp-Source: AGHT+IG6wkPzkPzY/USFaBNgj1yEkxF7hXGRuDoQUdKcfmIfidx/a1R/8A7+Yr0rnme94x/sno0w7g== X-Received: by 2002:a05:6a00:2305:b0:686:2b60:3348 with SMTP id h5-20020a056a00230500b006862b603348mr6899572pfh.21.1691335677849; Sun, 06 Aug 2023 08:27:57 -0700 (PDT) Received: from smtpclient.apple (107-215-223-229.lightspeed.sntcca.sbcglobal.net. [107.215.223.229]) by smtp.gmail.com with ESMTPSA id t7-20020aa79387000000b00687087d3647sm4679985pfe.142.2023.08.06.08.27.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sun, 06 Aug 2023 08:27:57 -0700 (PDT) Content-Type: text/plain; charset=utf-8 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.600.7\)) Subject: Re: deroff(1) and deroff (1b) with mdoc(7) (was: demandoc(1)) From: Bakul Shah In-Reply-To: <238083d9-c937-930c-9f15-7f8708c4205a@freebsd.org> Date: Sun, 6 Aug 2023 08:27:46 -0700 Cc: freebsd-hackers Content-Transfer-Encoding: quoted-printable Message-Id: References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> <79117D20-0A32-4548-9250-27CCF6650403@iitbombay.org> <238083d9-c937-930c-9f15-7f8708c4205a@freebsd.org> To: Graham Perrin X-Mailer: Apple Mail (2.3731.600.7) X-Rspamd-Queue-Id: 4RJjy75Nl2z3LQJ X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US] On Aug 6, 2023, at 4:32 AM, Graham Perrin = wrote: >=20 > deroff(1) /usr/local/heirloom/usr/5bin/deroff is potentially more = useful than > deroff(1b) /usr/local/heirloom/usr/ucb/deroff however > deroff(1) removes a little too much; = . Heirloom deroff was derived from plan9 deroff. >=20 > >=20 > deroff(1) in Plan 9 from User Space has: >=20 > - a manual page that differs from deroff(1) and deroff(1b) in the = Heirloom Toolchest >=20 > - the same glitch (below). >=20 >=20 > % cat /usr/src/share/man/man8/rc.8 | grep Operation\ of > .Ss Operation of Nm > .Ss Operation of Nm rc.shutdown > % /usr/local/plan9/bin/deroff /usr/src/share/man/man8/rc.8 | grep = Operation > Operation > Operation rc.shutdown > % Why not try to fix deroff to also support mdoc just as it supports mm = and ms macros? I hope you are not talking about adding demandoc to the base! Incidentally FreeBSD man fails at properly formatting deroff.1 man page. It produces -mm Remove titles, attachments, etc., as well as ordinary = troff constructs, from or mm documents. nroff -man produces this: -mm Remove titles, attachments, etc., as well as ordinary = troff con=E2=80=90 structs, from ms(7) or mm(7) documents. 9 man -mm Remove titles, attachments, etc., as well as ordinary troff constructs, from ms(7) or mm documents.=20 =09 mandoc man page says: By default, the input language is automatically detected for each file: if = the first macro is Dd or Dt, the mdoc(7) parser is used; = otherwise, the man(7) parser is used. With other arguments, -m is = silently ignored. So either it is using the wrong parser or the parser is doing the wrong = thing!= From nobody Sun Aug 6 15:46:17 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJkMH4fj9z4TvtW for ; Sun, 6 Aug 2023 15:46:19 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [IPv6:2610:1c1:1:606c::24b:4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJkMH3xtqz3N8L for ; Sun, 6 Aug 2023 15:46:19 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691336779; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+jvLuPFNSdWZYzniE1ZrylagVevhSgxSmr/ofgUoUO0=; b=GcfKeZYkG5mDxBRuY0MeePe+65a0ZOxduKDb6V2hXuR5oF4Y8xXziYNjv+i0GJa/WLZ2mR EX9ZwTSF661KL9fM1E3WD+pELpdOg6RQi8BfuYqYGiKfxYluPj1LLeXdhr/0q6KgppfdS0 ZrO/sN8Da/NMxF3TJmUdn+1Z03dF/dWh4Dw2zvTiUdHYxZBHx0wer2Cw4czO/RWpTLSmnP X0MtHDt4b5yT/VQOSbR7DkmihXuyiyjrIAcd9O0JdONMvDezTi/NCgopvYQFZ8pjfSqp5m uv/1aDbENjC7NV3yoHeRK09zYI2GlfDjwryc+35+XKyiQSqfKo0LUgjD3DiO7Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691336779; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=+jvLuPFNSdWZYzniE1ZrylagVevhSgxSmr/ofgUoUO0=; b=sKi6UT5+65tKi/2bpBMD8B6ghF+OCZhQZwSiwWWDaQbFEnd6NTXfCdQKIdi9vMDHGB8/H1 DkCxTodQqaSLAXEG18xt18Hm29+PlOtcoopYB7fS6gbDEWG8SsLkg7LmKBeBOWTJ0UZzRL k7S5MzOPQcapoHxlmE3p3EnXjfVLzwEkcvkrHW+sU+dQcbo135S5t4X/mNX8k0NrGMQBhd pr0qyNx+0NJKgIYfcP3Vkw5G2nVA5a4RnVsJZ4xs6VnTUdPgGXl4cbqUIQB/FiIuuwFKpH /5wDRQMCHptT2KbOBSGsXPM3Ne2o+of4Rc49CudJFxwV13YmV8CezPRAU0yFDA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1691336779; a=rsa-sha256; cv=none; b=L+LvFjytf7HMzgqbg/StgAqRlVVlhoNzLM4rb6pp4Ml6C0ZILz3GOO9c36EhDoWh/x3iQw OuNNNz+oqUrQsGiK8k5pnHrL6KrnOtqqoVcmEO7UbpVbBQLGF8JVxx9N/LexwlDG0Gicu7 t7EaVZA5Yo7Xy1HQz9nXbER531hyiOA1dwiqCG0aiG2a6+q4uSj+/2ki9ZgZk2vd7K6dB5 AIcQBxTe9IwW/tXcEQa3FwSHAdtg7sNZbp78kzPjsHl/G4VphHqFwbnactQJ99zDdqRIh7 k9Th7z3Mkce/L8RIXlAipEdqrchRgMrNNv2BGwZoSyw3PsVR8CzNT3dGK7qx9A== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from [192.168.1.10] (80-42-66-93.dynamic.dsl.as9105.com [80.42.66.93]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4RJkMH1kg9zl5v for ; Sun, 6 Aug 2023 15:46:19 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: Date: Sun, 6 Aug 2023 16:46:17 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.1 Subject: aspell(1) markup visibility and filtering (was: demandoc(1)) From: Graham Perrin To: freebsd-hackers@freebsd.org References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> <9911e4cf-3498-4221-6ba4-e7cea34f7606@freebsd.org> Content-Language: en-US Organization: FreeBSD X-Priority: 5 (Lowest) In-Reply-To: <9911e4cf-3498-4221-6ba4-e7cea34f7606@freebsd.org> Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------G6gycJKiAyY90IuW4ajWPtnX" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------G6gycJKiAyY90IuW4ajWPtnX Content-Type: multipart/mixed; boundary="------------0RucdQ450CufjlAeMo7oXKbM"; protected-headers="v1" From: Graham Perrin To: freebsd-hackers@freebsd.org Message-ID: Subject: aspell(1) markup visibility and filtering (was: demandoc(1)) References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> <9911e4cf-3498-4221-6ba4-e7cea34f7606@freebsd.org> In-Reply-To: <9911e4cf-3498-4221-6ba4-e7cea34f7606@freebsd.org> --------------0RucdQ450CufjlAeMo7oXKbM Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMDYvMDgvMjAyMyAxMzozNiwgR3JhaGFtIFBlcnJpbiB3cm90ZToNCj4g4oCmIGhhdmUg YXNwZWxsIHByZXNlbnQgZXZlcnlkYXkgbGFuZ3VhZ2UsIHdpdGhvdXQgbWFya3VwLiDigKYN Cg0KU29ycnksIGlnbm9yZSB0aGF0Lg0KDQpJIGFzc3VtZWQsIHdyb25nbHksIHRoYXQgbWFy a3VwIHdhcyB2aXNpYmxlIGJlY2F1c2UgdGhlIG5yb2ZmIGZpbHRlciB3YXMgDQpub3QgZWZm ZWN0aXZlIHdpdGggbWRvYyBtYXJrdXAuDQoNCkV2ZW50dWFsbHkgSSByZWFsaXNlZDogaXQn cyBub3JtYWwgZm9yIGFzcGVsbCB0byBzaG93IGZpbHRlcmVkIG1hcmt1cCwgDQphbmQgdGhl cmUgX2lzXyBhIHNsaWdodCBkaWZmZXJlbmNlIHdpdGggdGhlIGZpbHRlci4NCg0KDQolIGNh dCAvdXNyL3NyYy9zaGFyZS9tYW4vbWFuNy9oaWVyLjcgfCBhc3BlbGwgbGlzdCAtLW1vZGU9 bnJvZmYgDQotLWVuY29kaW5nIHV0Zi04IHwgc29ydCB8IHVuaXEgfCB3YyAtbA0KIMKgwqDC oMKgIDEyMQ0KJSBjYXQgL3Vzci9zcmMvc2hhcmUvbWFuL21hbjcvaGllci43IHwgYXNwZWxs IGxpc3QgLS1lbmNvZGluZyB1dGYtOCB8IA0Kc29ydCB8IHVuaXEgfCB3YyAtbA0KIMKgwqDC oMKgIDEzMw0KJSBjYXQgL3Vzci9zcmMvc2Jpbi9iZWN0bC9iZWN0bC44IHwgYXNwZWxsIGxp c3QgLS1lbmNvZGluZyB1dGYtOCB8IHNvcnQgDQp8IHVuaXEgfCBncmVwIC1lIENtIC1lIE5z IC1lIFBhDQpOcw0KJSBjYXQgL3Vzci9zcmMvc2Jpbi9iZWN0bC9iZWN0bC44IHwgYXNwZWxs IGxpc3QgLS1tb2RlPW5yb2ZmIC0tZW5jb2RpbmcgDQp1dGYtOCB8IHNvcnQgfCB1bmlxIHwg Z3JlcCAtZSBDbSAtZSBOcyAtZSBQYQ0KTnMNCiUNCg0KDQpJIGd1ZXNzLCBDbSBpcyBpbnRl cnByZXRlZCBhcyBzaG9ydCBmb3IgQyBtaW5vciwgYW5kIFBhIGFzIHNob3J0IGZvciANCmZh dGhlci4NCg0K --------------0RucdQ450CufjlAeMo7oXKbM-- --------------G6gycJKiAyY90IuW4ajWPtnX Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmTPwEkFAwAAAAAACgkQt2dIb0oY1Avz ww/9E7trkma9anaj4EMQ+jZLPyscQrgYy2jxU6wC8h9CMNW5uDaBDT8sGtRLV/Z3/eIrGTNJQepd Hgmn0KB61EjFta4KiCFuUDUGB7yb3b40MwiQvTUVW++JzLNszZXwm/MUAJtFEKV+gLId52qlHoPg o0C++8uEH8kL2EGZzP5wYQ2XTlbKV8GDcuWr4lRMHDYYEQjXg8rThiWlyisWkLrYzqDxzzgxG4Be 6mk6+u6uORV0RIv24mhK0ea94YED5QidtzVN6JLwvvA5qEX7u8W2ZDe+E06G/5Gu/rQuZ9xbE3nC 6pxju5YSBvf8NNqg+BfWZkFShA5zK++yYOZBFFuqSfaJQvv4VE3AJK3XUQC2Kr0h95714MOStlBp Vzt86007m4smBzEebfa0HwZrYuklM1hJMzKRtqFZKR9o1T6fAruT0JXlsAmrKG7vCusarL+yoLco Tftkh/Pz0Gu4/1cyj7zUpFrAL2DXSAOQ4FNzSV/ZeOajbrl3IKr99kBMSw440A9taGRN9ohUpcqI ve2eg72jlV5+/i5XBc/xIAd1TOxUr5VFATAZWz0o6I8LIEa/OhEoPgRre56XaJxxqsO669t27XYT 0SDw01R98JjdVF4MQOe43LhMckZnNwhR+BRZRDClctFfhb88jNh5Xn7ChYB5qP1mcUyLgmDl5xyS qd4= =RDLU -----END PGP SIGNATURE----- --------------G6gycJKiAyY90IuW4ajWPtnX-- From nobody Sun Aug 6 15:59:01 2023 X-Original-To: hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RJkf01FhDz4TwVX for ; Sun, 6 Aug 2023 15:59:04 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RJkf00SxQz3R81 for ; Sun, 6 Aug 2023 15:59:04 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691337544; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Zn19kfGJWQ+I86n393f4eOHHQtQ8/yEVXGYlBaw0Nus=; b=cAI0UiTvEqfO8RN1a3UER86QRFAwzvhfaZiHE5d18V2oNdEQlBwDSlsXwJVQ/U8Aoav58J KRm9mU1nIkRh8c1S29ormIwILUCdW9rP1GAVeno8YHfvuoBEs86bTTwET462BKehkg2yHE OwoA1yPCux1Dnj5MrFgJtdBNwEGj68IWuz7ych/z+wTkUILGssrCIl6v66Nvk+gnpfzksu qjPGjmCwstvYUAIs4V/ajnyoqyzyPrhkP0hXIlMIHaCVcMKPPMu1mkCHmt2lAZoZYY7Nfx c4PbQcSFMcpJY+80F8aYe90BF+4wvUwn/L3F3NYgeiEvXBFpLE6p/Pb+ClZhNg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691337544; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=Zn19kfGJWQ+I86n393f4eOHHQtQ8/yEVXGYlBaw0Nus=; b=DKRFtWd/uQtOkc/vOfPwTj0b3AuF0M1dLyHB6Wy2HF0Oy9GXbjadddo3whBO7FTszmjT8f ovIE2UrmClCQu6pJLGXOs6EoaZoxULnyu1xAJILmpVxkP7mwd0dnm+/ngi1lU5HlkY4sWb 56Pgg4VNqALeWtWQrqMQd4TluTzo+R1bcmfSgWaLVGOW/gjBtCNDAtO/i5B8b8xXqB5nxq Tq7XBM9bv9MvE4H+l7sWXIP+Nny6xtlk8j1IC4WdS5klyQ/5Kqm8NYla2jquqORoblF40G GlW6NoYHBf2XCpoMPMYoLQ/kfGz3sZbpdSDKFWJD6IFLrv/Pc9CW7oUucWrnWA== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1691337544; a=rsa-sha256; cv=none; b=DWJf1ZTdgRkuBcNcTtjJbzhgYhBIjntnBH4S6TEGDwGPhQQWWUU/cNUrci3bzh1vjMdc9z 9N6awS7szF69KC8trREPc5/u559ANsqio5rp+fOadjEejjhjGZy6LNvoWUFtM3PXdf5HZl yvLYNQ0F3f965GSf+i5DDl52B/Ph3KBGdUo2Rs4Y2xBZRwaaHU1kwYB+5SJBqVfmEqmeaV TuWLc1epw5m+4eo59ouJLD5KEPNGHq16eqZ5VeqSbZ/rUejMT94b6+qxobf63+Di938IH/ 2/hZNaWpxVpRBgsnje+KiOm+U+0CIpqDlQZ/ZEaH5Nl0TqTj6vGWfjJCHm39yQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from [192.168.1.10] (80-42-66-93.dynamic.dsl.as9105.com [80.42.66.93]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (Client did not present a certificate) (Authenticated sender: grahamperrin) by smtp.freebsd.org (Postfix) with ESMTPSA id 4RJkdz5NnKzl1s for ; Sun, 6 Aug 2023 15:59:03 +0000 (UTC) (envelope-from grahamperrin@freebsd.org) Message-ID: <8b8e9624-080d-50b3-40c1-35d9a6716ed4@freebsd.org> Date: Sun, 6 Aug 2023 16:59:01 +0100 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:102.0) Gecko/20100101 Thunderbird/102.13.1 Content-Language: en-US To: freebsd-hackers References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> <79117D20-0A32-4548-9250-27CCF6650403@iitbombay.org> <238083d9-c937-930c-9f15-7f8708c4205a@freebsd.org> From: Graham Perrin Subject: Re: deroff(1) and deroff (1b) with mdoc(7) (was: demandoc(1)) Organization: FreeBSD In-Reply-To: Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="------------K4Yl7SB0id0beQPCF82VeK4B" This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --------------K4Yl7SB0id0beQPCF82VeK4B Content-Type: multipart/mixed; boundary="------------TMMFTfPHQejxlsvr0XTBE1EV"; protected-headers="v1" From: Graham Perrin To: freebsd-hackers Message-ID: <8b8e9624-080d-50b3-40c1-35d9a6716ed4@freebsd.org> Subject: Re: deroff(1) and deroff (1b) with mdoc(7) (was: demandoc(1)) References: <0345d177-0da2-e41b-6a49-b3fe06e52be0@freebsd.org> <79117D20-0A32-4548-9250-27CCF6650403@iitbombay.org> <238083d9-c937-930c-9f15-7f8708c4205a@freebsd.org> In-Reply-To: --------------TMMFTfPHQejxlsvr0XTBE1EV Content-Type: multipart/alternative; boundary="------------txYRpAZKr4sfz7JublsUFqXx" --------------txYRpAZKr4sfz7JublsUFqXx Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: base64 T24gMDYvMDgvMjAyMyAxNjoyNywgQmFrdWwgU2hhaCB3cm90ZToNCj4+IOKApg0KPiBXaHkg bm90IHRyeSB0byBmaXggZGVyb2ZmIHRvIGFsc28gc3VwcG9ydCBtZG9jIGp1c3QgYXMgaXQg c3VwcG9ydHMgbW0gYW5kIG1zDQo+IG1hY3Jvcz8NCg0KDQpJIHdvdWxkbid0IGtub3cgd2hl cmUgdG8gc3RhcnQgKGFuZCBJJ20gbm90IGluY2xpbmVkOyBJJ20gbm90IGEgZGV2ZWxvcGVy KS4NCg0KDQo+IEkgaG9wZSB5b3UgYXJlIG5vdCB0YWxraW5nIGFib3V0IGFkZGluZyBkZW1h bmRvYyB0byB0aGUgYmFzZSENCg0KSSdtIGluY2x1ZGluZyBpdCBmb3IgbXlzZWxmLCA8aHR0 cHM6Ly9yZXZpZXdzLmZyZWVic2Qub3JnL1A2MDEkMjAtMjE+Lg0KDQpXaHkgd2FzIGl0IHJl bW92ZWQ/IFRoZSBjb21taXQgd2FzIHRlcnNlIChubyByZWZlcmVuY2UgdG8gYSBidWcgcmVw b3J0LCANCnJldmlldyBvciBkaXNjdXNzaW9uKToNCg0KN2IwODk2ZDg4MjhjIFJlbW92ZSBk ZW1hbmRvYygxKSBmcm9tIHRoZSBidWlsZA0KDQo= --------------txYRpAZKr4sfz7JublsUFqXx Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On 06/08/2023 16:27, Bakul Shah wrote:=

      
=E2=80=A6
Why not try to fix deroff to also support mdoc just as it supports mm and=
 ms
macros? 


I wouldn't know where to start (and I'm not inclined; I'm not a developer).


I hope you are not talking a=
bout adding demandoc to the base!

I'm including it for myself, <https://reviews.freebsd.org/P601$20-21>.

Why was it removed? The commit was terse (no reference to a bug report, review or discussion):

7b0896d8828c Remove demandoc(1) from the build

--------------txYRpAZKr4sfz7JublsUFqXx-- --------------TMMFTfPHQejxlsvr0XTBE1EV-- --------------K4Yl7SB0id0beQPCF82VeK4B Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEWT/lssMHB+28ly8Kt2dIb0oY1AsFAmTPw0UFAwAAAAAACgkQt2dIb0oY1AuB fg//ZH056M26IAJw6CMsEKoKaNETftr1FKEuY8wwuBCaf2cVNTbAla4Gsqzs73bJJEPHfG4hivaY 32gI4/2ySmbQt00SslQUhsur+FMOu+zO2ZkqYPoPm9YFrxsDzcKBLwMkzd4bRmKmUZYTAS4EA42O UkYFtt5Dy7AclPtSa3/bd6veiNesV4pfJU1lT6PgQTaYovjdNMw7nypn3uKsueq547jAwlKh4YSt FunPLtIfuoDqDVTCAVBcsgsLIdMd27dR1wbYMO7FMqjsLFPG2AoAylHWanZgMwcl2uR1A+RWlIH+ 1y+ZdqPNd4g/Cf9Sb+fnLljaNG+AUhrAsBX/V8OzMFPQy74LpDqCBLCbNGL0Y68bu8S3WD6dxZIB iNxLgoBVkGgFjiEQ5T8EgqQ5aLMkp+GgwQyAOxOaoNg6huem89qa3PrGxmRtDBRYOsyKCeycd52u vnwRUlwejE/5HD+TlHvA0tjlFmS/NFpOiq1XBD8RZDQGUe8qHBJyqafhwJyLLOISNC5/xgSwRGtl 9xiV1M9c4j2kw+zSpEpe4akog2tOP2mG7U9RgdpvexSNZsMz51Q77UMLycJOqjXh4HW9KlB0PF7F u6rXgyiXMsfhM7YuwIEH8yJQu5Grv4+p9/mUcx3uh9MFc0nvtKOVkQVHk6jpQz+jcf5cnxEe8Q6N 11A= =F8se -----END PGP SIGNATURE----- --------------K4Yl7SB0id0beQPCF82VeK4B-- From nobody Wed Aug 9 12:40:49 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RLV6005HZz4pvQp for ; Wed, 9 Aug 2023 12:40:56 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RLV5z0t1tz3b45 for ; Wed, 9 Aug 2023 12:40:55 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=RWojPRDR; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=KlB3PabC; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.20 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 32A2432003CE for ; Wed, 9 Aug 2023 08:40:53 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Wed, 09 Aug 2023 08:40:53 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :message-id:mime-version:reply-to:sender:subject:subject:to:to; s=fm3; t=1691584852; x=1691671252; bh=++1kqpKWgQtIC0xY0bfOUHc8z dehyE8iwdcPa06ZSXg=; b=RWojPRDR9wThKJLy4Ew6hjucU0TYDLu4t6vB4VRXZ AAK5QoM5cjlXWlfoA+n0vi6qSBCgjlNUaNUxcudZfdZMYxG9aquD+N2VxVjPeogk B2cPovUA4fdk1L7UcPDNwJfWq4uhLJfNM+0tdIXTxECfRXNUoJ1DfDI74INEfYeN Q/09/nrJMK+6JhNfLvSbljBR/I+ycYIVSRZ3+fuSSs7Fso+OEDOnPCnaN/g0tvVH 4K52lKR8E8Onu1AlEjlQbbfst45nimSgApQ3RelD7kXNhE0BiD8DUnB/N8lI7F9V pmp+yJAEczR9uqZYEWnOje/0zobossxo4pEFbqbVAyxIQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:message-id :mime-version:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t= 1691584852; x=1691671252; bh=++1kqpKWgQtIC0xY0bfOUHc8zdehyE8iwdc Pa06ZSXg=; b=KlB3PabCV9Y8AVmhPvmFl40IkIFY/ETqBQX41VEoubNRJxE8EBm j3Rq2MGeUz22B33bhWzd8FvDTV1mz/2ADaaZ59qXJ7gCP26iY3EQ8Mu93gUVkLu6 kvCiuM+pBF9LeA0TJwtgv+6QHf2j7v2jBaYd5Y5A50/eI3N2yz3ygYWDKAnFAUgG 7NlWOX5bK3ZIO15q40Yl+ZnbZlPBoi9M1qQSVPco1imsuGZC/nbUXmFjrG5ggDIT SfT3LOtpZzIweymBm87+GX83m3PW64xOJ4iij6gQHM6CZ7ygMF6BhvzAyH5TXl8i QgQFhC31LWJ8sVPltNvv0o4XUpAJ3I7wx3g== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrleeggdehfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfggtggusehttdertddttd dvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrghtthgv rhhnpeevudffiedvffffgffhgeefjeefffdtieetheetkeefhfdvfefgtedtueehgeffue enucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehvohhi ugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 9 Aug 2023 08:40:52 -0400 (EDT) Date: Wed, 9 Aug 2023 13:40:49 +0100 From: void To: freebsd-hackers@freebsd.org Subject: can sftp be made multi-threaded? Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline X-Spamd-Result: default: False [-3.07 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; RWL_MAILSPIKE_EXCELLENT(-0.40)[64.147.123.20:from]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; MIME_GOOD(-0.10)[text/plain]; NEURAL_HAM_SHORT(-0.07)[-0.070]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; ARC_NA(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4RLV5z0t1tz3b45 Hello hackers@ Can sftp be made multi-threaded? Would rsync-over-ssh accomplish the same thing? The issue I'm having is with large backups taking ages to transfer even with both source and destination being on gigabit fibre. It looks like sftp is single-threaded and the bandwidth per thread is something like 5-50 Mbps and it's nowhere near saturating the bandwidth. Would multi-threaded sftp (if it were possible) or rsync-over-ssh work multi-threaded on a single huge backup file? In my example, the ssh systems are both OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023 ty -- From nobody Wed Aug 9 12:49:48 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RLVJc6cKXz4pwC0 for ; Wed, 9 Aug 2023 12:50:08 +0000 (UTC) (envelope-from otis@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RLVJc65Tbz3dYq; Wed, 9 Aug 2023 12:50:08 +0000 (UTC) (envelope-from otis@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691585408; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=H2fVsmoqLwev+y1MmKhqLRIrvoAffyjdoDWO53yrr7s=; b=bV8Xo/8miPY29AmyyHOo6mmuweit2FdekzutXcuBtWdzYFWj+spUDf+Q5xLRrL8LdojDY/ ma/O8eVhuTn7GSULSorYjEylcYFUVOlD7ZFjaP3ZtMNI3G/MioTGok9WBxeh2Fpl8u/3Va Dxa8pOVTKg2KH5jO0fHQSczhARew4wwKgBpTpgln9CB1izaO7e9I3qbk4RLnsbtWAaPtUL I84+Ll++4TK/IaNNaCKheRk9VT/j76vKO9fRotd03TpTBxPAjepYzor6G3HU4WM+rVKelX mRQBvqb/pp47a95iU4djHob76qMgSs696E+csVA2+0paMANYFX53LTMky+eSCA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1691585408; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=H2fVsmoqLwev+y1MmKhqLRIrvoAffyjdoDWO53yrr7s=; b=KKAgdQgBUW7LPC2B/Wijctg6ab+YeNRbXOW/HdKszWYLGLLnPjROzlsEqI3BGn10hkSZwe SLB14uZwS6TSF+qU4RkTID/UosCMD36mN6fdNBxhidBoWz0VHLLCJFy97epj7sU0CVnIf5 vEO8FTSQWwYGoeczp+o+1/KidcBpM53tqVjgPL1fkRANawgtZj3awcJVRwz69PNi5YonEg RTmgOO4n1ux7LqLd65r1uDXP/zaOXWASWZY3JxLEPISNUf3mRJsHtnQLVN3g1Wqj185Ycy vtYwRmjmRkZ3ZDaFfZ5qyDlLL+OyNgeWLcTf1t4YpPyXcO1/a2dMX02f7mZ0JQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1691585408; a=rsa-sha256; cv=none; b=AE0X2clCDEF+1RaPn1zzGhiG025SL/PQu3nHug5uGcLCZIZLjADMQZM5kOWKOleJC5ClZR 3sDI7p3ltno8sognJbLlCyZ7GVsOUfDVOOajuSLep3ks251LVzSCbKeDE4X3E9GgsnSLgf i+FuK5tAmHfu3oK4ue6ot5oIFRY8O+xPFcHMbDowRrYffDGpOkDxAVWE4nqWi5iHWJh8a8 wB4qXxMXq8CVsoOGh0lLe/1+O09gW/HLKTsPtUO5jnri8pZwo8ho3uu7JH9pse/bs8R/EG lGSllfnlL/iebxqjngFr19R1gquwcOS6tMRRlHIvLzIa4Uq45eq//whIxXXXjQ== ARC-Authentication-Results: i=1; mx1.freebsd.org; none Received: from ns2.wilbury.net (ns2.wilbury.net [IPv6:2a01:b200:0:1:f816:3eff:fecd:13e6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature ECDSA (P-256) client-digest SHA256) (Client CN "svc.wilbury.net", Issuer "R3" (verified OK)) (Authenticated sender: otis) by smtp.freebsd.org (Postfix) with ESMTPSA id 4RLVJc4N6jz13yL; Wed, 9 Aug 2023 12:50:08 +0000 (UTC) (envelope-from otis@FreeBSD.org) Received: from smtpclient.apple (unknown [217.73.28.193]) (Authenticated sender: juraj@lutter.sk) by svc.wilbury.net (Postfix) with ESMTPSA id DD56B61F98; Wed, 9 Aug 2023 14:49:59 +0200 (CEST) Content-Type: text/plain; charset=utf-8 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\)) Subject: Re: can sftp be made multi-threaded? From: Juraj Lutter In-Reply-To: Date: Wed, 9 Aug 2023 14:49:48 +0200 Cc: freebsd-hackers@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <3639ADD0-3715-4B2B-9C25-EBF367FC09A0@FreeBSD.org> References: To: void X-Mailer: Apple Mail (2.3731.700.6) X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00 autolearn=ham autolearn_force=no version=4.0.0 X-Spam-Checker-Version: SpamAssassin 4.0.0 (2022-12-14) on ns2.wilbury.net > On 9 Aug 2023, at 14:40, void wrote: >=20 > Hello hackers@ >=20 > Can sftp be made multi-threaded? Would rsync-over-ssh accomplish the = same thing? >=20 > The issue I'm having is with large backups taking ages to transfer > even with both source and destination being on gigabit fibre. >=20 > It looks like sftp is single-threaded and the bandwidth per thread is > something like 5-50 Mbps and it's nowhere near saturating the = bandwidth. Would multi-threaded sftp (if it were possible) > or rsync-over-ssh work multi-threaded on a single huge backup file? Have you played with misc/mbuffer from ports? It might do what you are = looking for (provided that sftp alone isn=E2=80=99t sufficient). =E2=80=94 Juraj Lutter otis@FreeBSD.org From nobody Wed Aug 9 13:51:11 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RLWg939ssz4q1Bw for ; Wed, 9 Aug 2023 13:51:17 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RLWg82ymFz4Qsy for ; Wed, 9 Aug 2023 13:51:16 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=jNsf7TyO; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="w CTFkaA"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.20 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 6C47632002F9 for ; Wed, 9 Aug 2023 09:51:14 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Wed, 09 Aug 2023 09:51:14 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1691589073; x=1691675473; bh=Yrxjf1e6xo/iGLkAGqo1EguNT5894/sk00b sXgBHtEA=; b=jNsf7TyOeRwvgI3rZna2SAuqOPKr2/sj2AyS/eqxwtgdE238/6k CbCGeh3nTbBNn/Vj6FhSIJL38IEuBIz79zW37zgQQ9yWnGfjQFD9eYzakc1BDV0f t1kNsN0PaYC0W3SqiUGq6iX7DIHq2ixPTOSm5g10TQIUxbKQWb45ELBs5uM+gTwh WdnmvUqEVTISb51dVeusSzG4zb/+rXxlRjlJ9LahVXFwe+UlV13jBbBoPosUieVv nI7XNMzIUSBd67ZARBPFiHl7NPOUyZJvwn0/QDPouSMn1yqUbg8ZI9soDc2TVEud vu3iUqQQ9NtVTn9yTmQ7uJZdg5oT1hVEpxg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1691589073; x= 1691675473; bh=Yrxjf1e6xo/iGLkAGqo1EguNT5894/sk00bsXgBHtEA=; b=w CTFkaAeyVUqY2OFx3vgpdD4y1TKwOB1DcABIfrYYJX8dvIP5gn0avg0KDwchm4zf bG1jwDb2UVIr3qvpViLQrbEc9IvTWDN6fmjW/I6AxYykwALb8f1vQIGDM8KCoZIH fvgfIp5acoYvpNcXscgtyBTzKCe028q9hmYCUAFHKe5gBQ4fWEWFgR9hSDwzqDYb lTosuMQHhT580KTbejc0VZXy+yAedPM9c3mc/xRotyy3D1c7TpyuwRiASRu4yJSi /QcUEZW1Hmmkq6AI70ud7Wu2Dfo3Kh6gMzIHnQfCruVeu5TmwQ5draxzazB1ad7j BqeEU1EbvXffwiFuFxySQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrleeggdeikecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtugfgjgesthekre dttddtjeenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepudetveeggeegveeitedvudduteffffffhfetjefggfegveejffeiudetfe etvdeknecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Wed, 9 Aug 2023 09:51:13 -0400 (EDT) Date: Wed, 9 Aug 2023 14:51:11 +0100 From: void To: freebsd-hackers@freebsd.org Subject: Re: can sftp be made multi-threaded? Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <3639ADD0-3715-4B2B-9C25-EBF367FC09A0@FreeBSD.org> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <3639ADD0-3715-4B2B-9C25-EBF367FC09A0@FreeBSD.org> X-Spamd-Result: default: False [-3.95 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_SHORT(-0.95)[-0.951]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; RWL_MAILSPIKE_EXCELLENT(-0.40)[64.147.123.20:from]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4RLWg82ymFz4Qsy On Wed, Aug 09, 2023 at 02:49:48PM +0200, Juraj Lutter wrote: >Have you played with misc/mbuffer from ports? It might do what you are >looking for (provided that sftp alone isn’t sufficient). I've used mbuffer in a remote zfs snapshot context before but I thought that was to account the bursty nature of sending zfs backups because reading from the disks was bursty. This isn't the case here, as disks are all m.2 nvme connected to pci4 risers. The problem I'm seeing I can see through a tool like speedtest-go and running the test in single-thread mode. If 10 threads are used, I can saturate the connection. If 1 thread is used, the connection speed reported is a small fraction of the actual. I'm hypothesising that throughput-per-thread might be limited either by the ISPs and/or by for example sysctls on the two freebsd systems. I know there's something like third-party patches like HPN(?) that *might* do what I want but for a start I'm not sure they will work with openssh v3. I'm interested how others accomplish secure backup over long distances at near-line-speeds. If they need to recompile base openssh to accomplish it, if they're using v3 and any sysctls or other settings in ssh_/sshd_config -- From nobody Fri Aug 11 11:21:33 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RMhFk1Qdgz4pwdT for ; Fri, 11 Aug 2023 11:21:46 +0000 (UTC) (envelope-from jamie@catflap.org) Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [IPv6:2001:19f0:7400:8808:123::1]) by mx1.freebsd.org (Postfix) with ESMTP id 4RMhFh5zGcz3ZtP for ; Fri, 11 Aug 2023 11:21:44 +0000 (UTC) (envelope-from jamie@catflap.org) Authentication-Results: mx1.freebsd.org; dkim=none; spf=pass (mx1.freebsd.org: domain of jamie@catflap.org designates 2001:19f0:7400:8808:123::1 as permitted sender) smtp.mailfrom=jamie@catflap.org; dmarc=pass (policy=none) header.from=catflap.org X-Catflap-Envelope-From: X-Catflap-Envelope-To: freebsd-hackers@FreeBSD.org Received: from donotpassgo.dyslexicfish.net (donotpassgo.dyslexicfish.net [209.250.224.51]) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5) with ESMTP id 37BBLXqD064264; Fri, 11 Aug 2023 12:21:33 +0100 (BST) (envelope-from jamie@donotpassgo.dyslexicfish.net) Received: (from jamie@localhost) by donotpassgo.dyslexicfish.net (8.14.5/8.14.5/Submit) id 37BBLX0J064263; Fri, 11 Aug 2023 12:21:33 +0100 (BST) (envelope-from jamie) From: Jamie Landeg-Jones Message-Id: <202308111121.37BBLX0J064263@donotpassgo.dyslexicfish.net> Date: Fri, 11 Aug 2023 12:21:33 +0100 Organization: Dyslexic Fish To: void@f-m.fm, freebsd-hackers@FreeBSD.org Subject: Re: can sftp be made multi-threaded? References: In-Reply-To: User-Agent: Heirloom mailx 12.4 7/29/08 List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (donotpassgo.dyslexicfish.net [209.250.224.51]); Fri, 11 Aug 2023 12:21:33 +0100 (BST) X-Spamd-Result: default: False [-0.33 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_SPAM_SHORT(0.94)[0.942]; NEURAL_HAM_MEDIUM(-0.81)[-0.806]; NEURAL_HAM_LONG(-0.77)[-0.767]; DMARC_POLICY_ALLOW(-0.50)[catflap.org,none]; R_SPF_ALLOW(-0.20)[+mx:dyslexicfish.net]; RCVD_NO_TLS_LAST(0.10)[]; MIME_GOOD(-0.10)[text/plain]; FREEMAIL_TO(0.00)[f-m.fm,FreeBSD.org]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:20473, ipnet:2001:19f0:7400::/38, country:US]; MIME_TRACE(0.00)[0:+]; MLMMJ_DEST(0.00)[freebsd-hackers@FreeBSD.org]; TO_MATCH_ENVRCPT_SOME(0.00)[]; R_DKIM_NA(0.00)[]; FREEFALL_USER(0.00)[jamie]; RCPT_COUNT_TWO(0.00)[2]; FROM_HAS_DN(0.00)[]; HAS_ORG_HEADER(0.00)[]; TO_DN_NONE(0.00)[]; RCVD_COUNT_TWO(0.00)[2] X-Spamd-Bar: / X-Rspamd-Queue-Id: 4RMhFh5zGcz3ZtP void wrote: > Hello hackers@ > > Can sftp be made multi-threaded? Would rsync-over-ssh accomplish the same thing? > > The issue I'm having is with large backups taking ages to transfer > even with both source and destination being on gigabit fibre. > > It looks like sftp is single-threaded and the bandwidth per thread is > something like 5-50 Mbps and it's nowhere near saturating the bandwidth. > Would multi-threaded sftp (if it were possible) > or rsync-over-ssh work multi-threaded on a single huge backup file? > > In my example, the ssh systems are both OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023 rsync just spawns an ssh command, so would probably behave similarly. Another thing, scp transfers from my test Rpi2 are much slower than the network can handle due to the CPU use, which hits 100% on one cpu whilst it's running. So, check that CPU isn't the bottleneck too. As for the speed, I just tested sftp to transfer a file of random data, 2 GB in size from one FreeBSD box in London to another in France: The final result was: 100% 2000MB 43.5MB/s 00:46 (Note, that's MegaBYTES/s) That is WITHOUT HPN. I have compiled ssh both sides with HPN, but in this case, at least, enabling it makes no difference. The London box is pretty old, and is a virtual host scheduled to be decomissioned. It is running an old openssl 1.X, openssh 8.8 and is a single core 2.4Ghz amd64 box. The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 and openssl 1.1.1 Anything more I can tell you that may help? Cheers, Jamie From nobody Fri Aug 11 14:10:29 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RMm0W2y3fz4TrcT for ; Fri, 11 Aug 2023 14:10:35 +0000 (UTC) (envelope-from void@f-m.fm) Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RMm0V35xyz4QQT for ; Fri, 11 Aug 2023 14:10:34 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=Qd1Xdw+q; dkim=pass header.d=messagingengine.com header.s=fm3 header.b=EDExSBba; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 64.147.123.20 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute5.internal (compute5.nyi.internal [10.202.2.45]) by mailout.west.internal (Postfix) with ESMTP id 679EA3200939 for ; Fri, 11 Aug 2023 10:10:32 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute5.internal (MEProxy); Fri, 11 Aug 2023 10:10:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-type:content-type:date:date:from:from:in-reply-to :in-reply-to:message-id:mime-version:references:reply-to:sender :subject:subject:to:to; s=fm3; t=1691763031; x=1691849431; bh=1N XmXoXAIDYfM1WRFtzhPvJwl8X+21Zz7tlnYrl73M8=; b=Qd1Xdw+q6yesuPZP0u 5pXvVrzxi2ZxgnNsByMzmdF1XaJQHOJRSFh3mUQWjYduwpuiADs7PaesdHRjXaEH XfZxkFt91XbNNXYyEWmNkGZSZlAXKgtIuJ5WHwm7QPIpDlTbxokDrOyi3yY6X4JL MM/uSLDfhgQX88fr0bnJ9EMO3t0KOxMpm53jLKTBu5rCJSJp7CJQfjPXSJjtuK+A glNr1DsFCD2Og3/sCxcqIfcMxnRmJRlAstuurgkZi0UDOZ+khNnVpftNqIz3gxAD /1c+oYxqFlIbBx9KBoK+iXlMNClsXEXYMKWTO81R3ObJg9bpgsVRROEhN6Yil9Ds RR1A== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:content-type:date:date :feedback-id:feedback-id:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm3; t=1691763031; x=1691849431; bh=1NXmXoXAIDYfM 1WRFtzhPvJwl8X+21Zz7tlnYrl73M8=; b=EDExSBbaJqhNWn0U6ILdPfcy0A/93 8z05n0f2pCOHpvnb+Ko8cFuf4xF8H/gVZVaEe2whpp/TK5gzgPKYeqs8EGNvfCqy 6VBYBOckjQbQHc3uUGoGbXmiMDyD/qdBeN9/rK2j8G3ATk9YJVm32W01jqmc5nEJ EilVhTiJP+SxnwcJEIzM38Uas8vGGs5EV4EVqcsItPLGf6/FZ16yo2N3SM4+VhXK XYfKETH6lKOtj5gzLx9fcXpNzx0Sivhbe+yk2uKwl3u4+m7vxsC/pmaKHQvIm79X gplePwdmWE8GyqfIN58Udrrw0pxact3qXywX3q7VShN4DZnPkmJ7mAmUQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrleekgdejudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtuggjsehttdertd dttddvnecuhfhrohhmpehvohhiugcuoehvohhiugesfhdqmhdrfhhmqeenucggtffrrght thgvrhhnpeekleduvdelhfeileefgffghfffkedtheellefgudfgvdegkeejjedutdehhe fgueenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehv ohhiugesfhdqmhdrfhhm X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 11 Aug 2023 10:10:31 -0400 (EDT) Date: Fri, 11 Aug 2023 15:10:29 +0100 From: void To: freebsd-hackers@freebsd.org Subject: Re: can sftp be made multi-threaded? Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <202308111121.37BBLX0J064263@donotpassgo.dyslexicfish.net> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <202308111121.37BBLX0J064263@donotpassgo.dyslexicfish.net> X-Spamd-Result: default: False [-3.36 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.98)[-0.981]; MID_RHS_NOT_FQDN(0.50)[]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; RWL_MAILSPIKE_EXCELLENT(-0.40)[64.147.123.20:from]; NEURAL_HAM_SHORT(-0.38)[-0.382]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; R_SPF_ALLOW(-0.20)[+ip4:64.147.123.20]; RCVD_IN_DNSWL_LOW(-0.10)[64.147.123.20:from]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; ARC_NA(0.00)[]; ASN(0.00)[asn:29838, ipnet:64.147.123.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4RMm0V35xyz4QQT On Fri, Aug 11, 2023 at 12:21:33PM +0100, Jamie Landeg-Jones wrote: >rsync just spawns an ssh command, so would probably behave similarly. I'm hoping that rsync will spawn many ssh. Need to look at max sessions on both ends of the connection. Since encountering the described problem, the person at the other end is away for the week so have not been able to test thoroughly. What I have been able to test shows that there is spiky latency in the connection, as well as slow speed, single-threaded. >Another thing, scp transfers from my test Rpi2 are much slower than the network >can handle due to the CPU use, which hits 100% on one cpu whilst it's running. >So, check that CPU isn't the bottleneck too. Yup. That won't be happening here. Dual xenon with 56 cores at remote end and same (but with 32 cores) at this end >As for the speed, I just tested sftp to transfer a file of random data, 2 GB in >size from one FreeBSD box in London to another in France: > >The final result was: > > 100% 2000MB 43.5MB/s 00:46 (Note, that's MegaBYTES/s) I ran a similar test. Sending system is on synchronous gigabit fibre on US east coast, receiving system is near London on 110/21 fibre (so, gigabit in the sending direction): 100% 2000MB 7.2MB/s 04:36 using rsync -azP : 2,097,152,000 100% 6.81MB/s 0:04:53 (xfr#1, to-chk=0/1) the speed fluctulates a lot. Both systems are quiet in a network and OS sense for the duration of the test. >The London box is pretty old, and is a virtual host scheduled to be decomissioned. >It is running an old openssl 1.X, openssh 8.8 and is a single core 2.4Ghz amd64 box. > >The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 and openssl 1.1.1 both ends here are running very recent -current, so ssl/ssh is OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023 >Anything more I can tell you that may help? Thanks very much for your input. I'm certain it's not a freebsd problem. -- From nobody Fri Aug 11 16:25:17 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RMq0C1BPYz4m6fX for ; Fri, 11 Aug 2023 16:25:31 +0000 (UTC) (envelope-from joesuf4@gmail.com) Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RMq0B0W1Lz4cL8 for ; Fri, 11 Aug 2023 16:25:30 +0000 (UTC) (envelope-from joesuf4@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=izsWl2Qu; spf=pass (mx1.freebsd.org: domain of joesuf4@gmail.com designates 2a00:1450:4864:20::436 as permitted sender) smtp.mailfrom=joesuf4@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-wr1-x436.google.com with SMTP id ffacd0b85a97d-31771bb4869so1966567f8f.0 for ; Fri, 11 Aug 2023 09:25:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691771128; x=1692375928; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=QKzK6Vp0W6hCtBp/ZcMfIWyK5k1bfoKX4SdTb8FX2NA=; b=izsWl2QuqBFMC46uDWgp0Xh//sCxYRsrE+jOuWaBLLWDxWbAdMrZic7DzACPnF/ZOD sC5xaC4Km2EWyG/rCKzrzhUoLHOWSzHm9hRZ32AtDHCwF5M7VZ0jh7ZSqWgmka7iYYZA hcdJGDdvDgwqzN0ycLO5eAG3hvrhO9xlC28PzkBIa4rAZy4sFej92k3QTWK7oMMyKE9X /jbkVjss/F8pzvXv9kw7yaqmrkDgMKumbpV2JJCeggYcdedzmrNQISHpInX6akGfGaF+ vOdUbwVPNTj37JWZhwMkMnBVZ+FMtP3GMNH2vx8/wE5N+Wn6MsrPh1EXe+VjjyaeG+Dw mTaA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691771128; x=1692375928; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=QKzK6Vp0W6hCtBp/ZcMfIWyK5k1bfoKX4SdTb8FX2NA=; b=C0vNhtLTZShEkkwUiLYTKrg2r+KBJiGygGnx8KHa3OKBgbh9W5lBDQaQOheofEV1Lx YUo3tf0iySo2SyzomNz4r9LLZrHTy9fXOtAZV1wFfH8ph2XQ5eQMJ0lSnQf/c2uveCHf IYFEbV+mhYLDVcQ3jzn6G53z2pidVzNJhil0HETj92CFxTAwRnWvVr0cFFw6AqqMog5H wNb3JpP2FWxhnfxYAHo/WtpkNnOimJnATE4b1vNNY999YHkV3gwwVNTmYX4q8CD11YxW Vlv2BhM/onOL7Pfsb3p4dzrGeHa3uC++DZNPG44nnbJ9t+8AhrnJWRTMwoxn2BHbjIZx 5W4g== X-Gm-Message-State: AOJu0YzDIptBGebTLIwqjxZEA9VW4NMi15dyXM/R5Bd+XcblTBe40rYg 73xppSd9lqgZu2IjC9n7yj6qBBWZb1ww0eMkW0c/RudY X-Google-Smtp-Source: AGHT+IHOx9WcuNLCA9hP33ricDhTXAf7ruPl4PbY8eq8v2KbmkAgy6JKTGBKIJBcCDwMToFrIbHCDvq7W3p0tDHh/qs= X-Received: by 2002:a5d:4ecf:0:b0:314:824:3788 with SMTP id s15-20020a5d4ecf000000b0031408243788mr1802360wrv.27.1691771128439; Fri, 11 Aug 2023 09:25:28 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <202308111121.37BBLX0J064263@donotpassgo.dyslexicfish.net> In-Reply-To: From: Joe Schaefer Date: Fri, 11 Aug 2023 12:25:17 -0400 Message-ID: Subject: Re: can sftp be made multi-threaded? To: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="00000000000026ea2f0602a829c9" X-Spamd-Result: default: False [-2.95 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.997]; NEURAL_HAM_MEDIUM(-0.98)[-0.984]; NEURAL_HAM_LONG(-0.97)[-0.973]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::436:from]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org] X-Spamd-Bar: -- X-Rspamd-Queue-Id: 4RMq0B0W1Lz4cL8 --00000000000026ea2f0602a829c9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Why don=E2=80=99t you just use xargs -P until you=E2=80=99ve exhausted your= CPU capacity? On Fri, Aug 11, 2023 at 10:10 AM void wrote: > On Fri, Aug 11, 2023 at 12:21:33PM +0100, Jamie Landeg-Jones wrote: > > >rsync just spawns an ssh command, so would probably behave similarly. > > I'm hoping that rsync will spawn many ssh. Need to look at max sessions > on both ends of the connection. > > Since encountering the described problem, the person at the other > end is away for the week so have not been able to test thoroughly. > What I have been able to test shows that there is spiky latency > in the connection, as well as slow speed, single-threaded. > > >Another thing, scp transfers from my test Rpi2 are much slower than the > network > >can handle due to the CPU use, which hits 100% on one cpu whilst it's > running. > >So, check that CPU isn't the bottleneck too. > > Yup. That won't be happening here. Dual xenon with 56 cores at remote > end and same (but with 32 cores) at this end > > >As for the speed, I just tested sftp to transfer a file of random data, = 2 > GB in > >size from one FreeBSD box in London to another in France: > > > >The final result was: > > > > 100% 2000MB 43.5MB/s 00:46 (Note, that's MegaBYTES/s) > > I ran a similar test. > Sending system is on synchronous gigabit fibre on US east coast, > receiving system is near London on 110/21 fibre (so, gigabit in the sendi= ng > direction): > > 100% 2000MB 7.2MB/s 04:36 > > using rsync -azP : 2,097,152,000 100% 6.81MB/s 0:04:53 (xfr#1, > to-chk=3D0/1) > > the speed fluctulates a lot. Both systems are quiet in a network and OS > sense > for the duration of the test. > > >The London box is pretty old, and is a virtual host scheduled to be > decomissioned. > >It is running an old openssl 1.X, openssh 8.8 and is a single core 2.4Gh= z > amd64 box. > > > >The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 > and openssl 1.1.1 > > both ends here are running very recent -current, so ssl/ssh is > OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023 > > >Anything more I can tell you that may help? > > Thanks very much for your input. I'm certain it's not a freebsd problem. > > -- > > --00000000000026ea2f0602a829c9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Why don=E2=80=99t you just use xargs -P until you=E2=80= =99ve exhausted your CPU capacity?

On Fri, Aug = 11, 2023 at 10:10 AM void <void@f-m.fm> wrote:
On Fri, Aug 11, 2023 a= t 12:21:33PM +0100, Jamie Landeg-Jones wrote:

>rsync just spawns an ssh command, so would probably behave similarly.
I'm hoping that rsync will spawn many ssh. Need to look at max sessions=
on both ends of the connection.

Since encountering the described problem, the person at the other
end is away for the week so have not been able to test thoroughly.
What I have been able to test shows that there is spiky latency
in the connection, as well as slow speed, single-threaded.

>Another thing, scp transfers from my test Rpi2 are much slower than the= network
>can handle due to the CPU use, which hits 100% on one cpu whilst it'= ;s running.
>So, check that CPU isn't the bottleneck too.

Yup. That won't be happening here. Dual xenon with 56 cores at remote end and same (but with 32 cores) at this end

>As for the speed, I just tested sftp to transfer a file of random data,= 2 GB in
>size from one FreeBSD box in London to another in France:
>
>The final result was:
>
> 100% 2000MB=C2=A0 43.5MB/s=C2=A0 =C2=A000:46=C2=A0 (Note, that's M= egaBYTES/s)

I ran a similar test.
Sending system is on synchronous gigabit fibre on US east coast,
receiving system is near London on 110/21 fibre (so, gigabit in the sending=
direction):

100% 2000MB=C2=A0 =C2=A07.2MB/s=C2=A0 =C2=A004:36

using rsync -azP : 2,097,152,000 100%=C2=A0 =C2=A0 6.81MB/s=C2=A0 =C2=A0 0:= 04:53 (xfr#1, to-chk=3D0/1)

the speed fluctulates a lot. Both systems are quiet in a network and OS sen= se
for the duration of the test.

>The London box is pretty old, and is a virtual host scheduled to be dec= omissioned.
>It is running an old openssl 1.X, openssh 8.8 and is a single core 2.4G= hz amd64 box.
>
>The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 = and openssl 1.1.1

both ends here are running very recent -current, so ssl/ssh is
OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023

>Anything more I can tell you that may help?

Thanks very much for your input. I'm certain it's not a freebsd pro= blem.

--

--00000000000026ea2f0602a829c9-- From nobody Fri Aug 11 16:27:04 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RMq2F3yhDz4m7KP for ; Fri, 11 Aug 2023 16:27:17 +0000 (UTC) (envelope-from joesuf4@gmail.com) Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RMq2D5KXwz4dSs for ; Fri, 11 Aug 2023 16:27:16 +0000 (UTC) (envelope-from joesuf4@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=IT0JB7h3; spf=pass (mx1.freebsd.org: domain of joesuf4@gmail.com designates 2a00:1450:4864:20::329 as permitted sender) smtp.mailfrom=joesuf4@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-wm1-x329.google.com with SMTP id 5b1f17b1804b1-3fe5c0e57d2so18991975e9.0 for ; Fri, 11 Aug 2023 09:27:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691771235; x=1692376035; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=UoG9BzQE3vI2ShFJ7KBy4dHZW4qgaONjSZFpxnPp4mM=; b=IT0JB7h3KzAmCGFA2wNejZbBGxSnTQQ8BIW7mpcy+JUQxpqwfzvjJL+Zmeoav9AFAy eq2H0NsNMbVZdIUSzhyJ2qAbgehB0TEhf48OMn3Cnzm861a+AqZfEOV26+rd4cD8S+S4 xHrz289v2sxJjyqnuhk3JNB8cCKy3a9TDiLyVjUBZ1/NKpbeFvSammNj864hC8sMarzL otUQlcSYZfHbvQWFi+xCMNtf+Cl4OclrGKe4aHEtfC3uvcLstvekOP5jF8yk0aCl9IOv vY3kHLOrdhHjgnWGRUepBPpfYhsOPTPeeAQWV5vmC2nKlYV/WuT/oVrVYcjGltTZyfcv 8WEw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691771235; x=1692376035; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=UoG9BzQE3vI2ShFJ7KBy4dHZW4qgaONjSZFpxnPp4mM=; b=gVSqHATDfmXoxXCVsQooM3ZDHlYhWUIR+s27Aja3HTG6Qy+2Gu/hrGJVBPfsJJVgvR RUtIcH6GxSlGStf1Xt4RvnD2pv4GIBFHvMspTBg2hte6/m2+jYh56Jt2UCt4Y9oc/PnH gr25sM4O/YcfewB0vbQi6vG09Hx9GjEqTl+0BI0RUgyw/gPwedXRxap6gyXuCiGb3SeE yBwMIurenUkLTKM6DvelMCdS7sp5S34WrsycR5PJrL4HL0yXDOsULIyJvpniBY5hVmSq XCdvnnGH9KiWPdVlS/4j4rZli1tylfTZCINWW3vhtV660KhfLi+SDUIzOu3My301+g2K M+Kg== X-Gm-Message-State: AOJu0Ywh02EQhAkHpqCc3o4Zlxh8DufhaF3MwwBOWDMT5/hG1kjpRwXS pgrKzuG6WgiCeovAJ+ta6OwPu5f6YvniPopBN3ko8kR7 X-Google-Smtp-Source: AGHT+IGh+nX7mczwCZ55UoCt7q1YPyUrSmTomNcOjl9tdsIIzPsTeceRquggr5QX4Ifcb4fnq86pAh4zxDbi1NWy4DM= X-Received: by 2002:adf:ef4a:0:b0:314:1b36:f440 with SMTP id c10-20020adfef4a000000b003141b36f440mr1770028wrp.70.1691771235045; Fri, 11 Aug 2023 09:27:15 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <202308111121.37BBLX0J064263@donotpassgo.dyslexicfish.net> In-Reply-To: From: Joe Schaefer Date: Fri, 11 Aug 2023 12:27:04 -0400 Message-ID: Subject: Re: can sftp be made multi-threaded? To: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="0000000000008197170602a82f15" X-Spamd-Result: default: False [-2.95 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.997]; NEURAL_HAM_MEDIUM(-0.98)[-0.983]; NEURAL_HAM_LONG(-0.97)[-0.973]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::329:from]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org] X-Spamd-Bar: -- X-Rspamd-Queue-Id: 4RMq2D5KXwz4dSs --0000000000008197170602a82f15 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable If it=E2=80=99s just a single file, split it into chunks. On Fri, Aug 11, 2023 at 12:25 PM Joe Schaefer wrote: > Why don=E2=80=99t you just use xargs -P until you=E2=80=99ve exhausted yo= ur CPU capacity? > > On Fri, Aug 11, 2023 at 10:10 AM void wrote: > >> On Fri, Aug 11, 2023 at 12:21:33PM +0100, Jamie Landeg-Jones wrote: >> >> >rsync just spawns an ssh command, so would probably behave similarly. >> >> I'm hoping that rsync will spawn many ssh. Need to look at max sessions >> on both ends of the connection. >> >> Since encountering the described problem, the person at the other >> end is away for the week so have not been able to test thoroughly. >> What I have been able to test shows that there is spiky latency >> in the connection, as well as slow speed, single-threaded. >> >> >Another thing, scp transfers from my test Rpi2 are much slower than the >> network >> >can handle due to the CPU use, which hits 100% on one cpu whilst it's >> running. >> >So, check that CPU isn't the bottleneck too. >> >> Yup. That won't be happening here. Dual xenon with 56 cores at remote >> end and same (but with 32 cores) at this end >> >> >As for the speed, I just tested sftp to transfer a file of random data, >> 2 GB in >> >size from one FreeBSD box in London to another in France: >> > >> >The final result was: >> > >> > 100% 2000MB 43.5MB/s 00:46 (Note, that's MegaBYTES/s) >> >> I ran a similar test. >> Sending system is on synchronous gigabit fibre on US east coast, >> receiving system is near London on 110/21 fibre (so, gigabit in the >> sending >> direction): >> >> 100% 2000MB 7.2MB/s 04:36 >> >> using rsync -azP : 2,097,152,000 100% 6.81MB/s 0:04:53 (xfr#1, >> to-chk=3D0/1) >> >> the speed fluctulates a lot. Both systems are quiet in a network and OS >> sense >> for the duration of the test. >> >> >The London box is pretty old, and is a virtual host scheduled to be >> decomissioned. >> >It is running an old openssl 1.X, openssh 8.8 and is a single core >> 2.4Ghz amd64 box. >> > >> >The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 >> and openssl 1.1.1 >> >> both ends here are running very recent -current, so ssl/ssh is >> OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023 >> >> >Anything more I can tell you that may help? >> >> Thanks very much for your input. I'm certain it's not a freebsd problem. >> >> -- >> >> --0000000000008197170602a82f15 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
If it=E2=80=99s just a single file, split it into chunks.=

Why don=E2=80=99t you just use xargs -P un= til you=E2=80=99ve exhausted your CPU capacity?

=
On Fri, Aug 11, 2023 at 10:10 AM void <void@f-m.fm> wrote:
On Fri, Aug 11, 2023 at 12:21:33PM +0100, Jamie Landeg-Jones wrote= :

>rsync just spawns an ssh command, so would probably behave similarly.
I'm hoping that rsync will spawn many ssh. Need to look at max sessions=
on both ends of the connection.

Since encountering the described problem, the person at the other
end is away for the week so have not been able to test thoroughly.
What I have been able to test shows that there is spiky latency
in the connection, as well as slow speed, single-threaded.

>Another thing, scp transfers from my test Rpi2 are much slower than the= network
>can handle due to the CPU use, which hits 100% on one cpu whilst it'= ;s running.
>So, check that CPU isn't the bottleneck too.

Yup. That won't be happening here. Dual xenon with 56 cores at remote end and same (but with 32 cores) at this end

>As for the speed, I just tested sftp to transfer a file of random data,= 2 GB in
>size from one FreeBSD box in London to another in France:
>
>The final result was:
>
> 100% 2000MB=C2=A0 43.5MB/s=C2=A0 =C2=A000:46=C2=A0 (Note, that's M= egaBYTES/s)

I ran a similar test.
Sending system is on synchronous gigabit fibre on US east coast,
receiving system is near London on 110/21 fibre (so, gigabit in the sending=
direction):

100% 2000MB=C2=A0 =C2=A07.2MB/s=C2=A0 =C2=A004:36

using rsync -azP : 2,097,152,000 100%=C2=A0 =C2=A0 6.81MB/s=C2=A0 =C2=A0 0:= 04:53 (xfr#1, to-chk=3D0/1)

the speed fluctulates a lot. Both systems are quiet in a network and OS sen= se
for the duration of the test.

>The London box is pretty old, and is a virtual host scheduled to be dec= omissioned.
>It is running an old openssl 1.X, openssh 8.8 and is a single core 2.4G= hz amd64 box.
>
>The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 = and openssl 1.1.1

both ends here are running very recent -current, so ssl/ssh is
OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023

>Anything more I can tell you that may help?

Thanks very much for your input. I'm certain it's not a freebsd pro= blem.

--

--0000000000008197170602a82f15-- From nobody Fri Aug 11 16:51:25 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RMqZL6JK4z4m8Zv for ; Fri, 11 Aug 2023 16:51:38 +0000 (UTC) (envelope-from joesuf4@gmail.com) Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RMqZL0zSpz3C0w for ; Fri, 11 Aug 2023 16:51:38 +0000 (UTC) (envelope-from joesuf4@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=Z+bMggWQ; spf=pass (mx1.freebsd.org: domain of joesuf4@gmail.com designates 2a00:1450:4864:20::32d as permitted sender) smtp.mailfrom=joesuf4@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-wm1-x32d.google.com with SMTP id 5b1f17b1804b1-3fe426b86a8so19937265e9.3 for ; Fri, 11 Aug 2023 09:51:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691772696; x=1692377496; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=l5yJe3bSSbRcrRv2T077YrLUW645NSzNNh+S2vPX7X4=; b=Z+bMggWQl0NryNIOPbNkpKijKtwyN2SPScMbuYBDkmyCE+MpyO8n0vf2gm39+Z4qw5 IG+EAE7vWP3WjfmwsuZyN7R5iOQJ+wIBpcKV9RVPndnwa9bwkd5F0A7teLlXII7JbEeg joDGJg7Lwzq/9JUlPvlvVfsP+7TL6p+JlU5GdxMNHrIbF9DPkqCyeYseFBdFIbqwUcVc JMhQtuOQ9aRsVaDjy0Fhh8FL3nwqS8HgZyhX8262w9ZG0//xYc6yUqNwDxfHtYodaWjJ ig9fo2m5M2zmYa+9KJtBn7XyJCzW1Uw4DHc7vSyokPRZG34pfYSwul3XVgTAcoteby9u 7egA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691772696; x=1692377496; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=l5yJe3bSSbRcrRv2T077YrLUW645NSzNNh+S2vPX7X4=; b=ixxi31lj68gw7LdAW3hkEmyG+JVnhZwyNgyPeD/Slv56ttYJTcKLpfgn+NzWAIZnzI bqQ0fvyGaAdswDR0rI/4WC81W7IHeMlnZBH6vZuNqLTbqkBeaFkL/lkI3UI0RGbKOAuy dbwaxyFgD336FSyQseKqvBcRocRbBNltFyUSWZ5racL+zQI3PItRIlZiJ0I7rdeIMDPE yPA6g7nTEPQOunDhxnRdF7pCqP2vNqf2Jr1bOaNCIHyEAjRMgJIMi9NUm2+tEazUmZ6x ypMvvde5VXO4cfkJFofOBwuOaMKFmjZ51WI90ugVg4/hX5WZsVdC0IRQS4OdmGxCRK5C syjg== X-Gm-Message-State: AOJu0YwhsPKaalNr7Cl2wTkaubvlY2PCwpMqZTaW/fNGtsI8AaoQe7d0 kpXEmuXSPlP6GXwX1UuODH2/SWuhnS6llQ6ws4aDnth8 X-Google-Smtp-Source: AGHT+IHVD3zQZFDwEl5gTVFMfyWMAjEMhWeXTSrpvjVEmVTeBVG2XHa486KRMcW/RukzjWC9F0VgCjfG1CI7AVK7w3Q= X-Received: by 2002:a05:600c:2301:b0:3fe:1f98:deb7 with SMTP id 1-20020a05600c230100b003fe1f98deb7mr2074223wmo.35.1691772696599; Fri, 11 Aug 2023 09:51:36 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <202308111121.37BBLX0J064263@donotpassgo.dyslexicfish.net> In-Reply-To: From: Joe Schaefer Date: Fri, 11 Aug 2023 12:51:25 -0400 Message-ID: Subject: Re: can sftp be made multi-threaded? To: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="0000000000009f218f0602a8864c" X-Spamd-Result: default: False [-2.95 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-0.997]; NEURAL_HAM_MEDIUM(-0.98)[-0.983]; NEURAL_HAM_LONG(-0.97)[-0.972]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::32d:from]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org] X-Spamd-Bar: -- X-Rspamd-Queue-Id: 4RMqZL0zSpz3C0w --0000000000009f218f0602a8864c Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable % split -n $(nproc) foo.pdf; ls x* | xargs -P 0 -J % scp % user@bar.example.com:%; rm x*; ssh user@bar.example.com sh -c =E2=80=9Ccat= x* > foo.pdf; rm x*=E2=80=9D On Fri, Aug 11, 2023 at 12:27 PM Joe Schaefer wrote: > If it=E2=80=99s just a single file, split it into chunks. > > On Fri, Aug 11, 2023 at 12:25 PM Joe Schaefer wrote: > >> Why don=E2=80=99t you just use xargs -P until you=E2=80=99ve exhausted y= our CPU capacity? >> >> On Fri, Aug 11, 2023 at 10:10 AM void wrote: >> >>> On Fri, Aug 11, 2023 at 12:21:33PM +0100, Jamie Landeg-Jones wrote: >>> >>> >rsync just spawns an ssh command, so would probably behave similarly. >>> >>> I'm hoping that rsync will spawn many ssh. Need to look at max sessions >>> on both ends of the connection. >>> >>> Since encountering the described problem, the person at the other >>> end is away for the week so have not been able to test thoroughly. >>> What I have been able to test shows that there is spiky latency >>> in the connection, as well as slow speed, single-threaded. >>> >>> >Another thing, scp transfers from my test Rpi2 are much slower than th= e >>> network >>> >can handle due to the CPU use, which hits 100% on one cpu whilst it's >>> running. >>> >So, check that CPU isn't the bottleneck too. >>> >>> Yup. That won't be happening here. Dual xenon with 56 cores at remote >>> end and same (but with 32 cores) at this end >>> >>> >As for the speed, I just tested sftp to transfer a file of random data= , >>> 2 GB in >>> >size from one FreeBSD box in London to another in France: >>> > >>> >The final result was: >>> > >>> > 100% 2000MB 43.5MB/s 00:46 (Note, that's MegaBYTES/s) >>> >>> I ran a similar test. >>> Sending system is on synchronous gigabit fibre on US east coast, >>> receiving system is near London on 110/21 fibre (so, gigabit in the >>> sending >>> direction): >>> >>> 100% 2000MB 7.2MB/s 04:36 >>> >>> using rsync -azP : 2,097,152,000 100% 6.81MB/s 0:04:53 (xfr#1, >>> to-chk=3D0/1) >>> >>> the speed fluctulates a lot. Both systems are quiet in a network and OS >>> sense >>> for the duration of the test. >>> >>> >The London box is pretty old, and is a virtual host scheduled to be >>> decomissioned. >>> >It is running an old openssl 1.X, openssh 8.8 and is a single core >>> 2.4Ghz amd64 box. >>> > >>> >The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 >>> and openssl 1.1.1 >>> >>> both ends here are running very recent -current, so ssl/ssh is >>> OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023 >>> >>> >Anything more I can tell you that may help? >>> >>> Thanks very much for your input. I'm certain it's not a freebsd problem= . >>> >>> -- >>> >>> --0000000000009f218f0602a8864c Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
% split -n $(nproc) foo.pdf; ls x* | xargs -P 0 -J % scp = % =C2=A0user@bar.example.com:%; rm x*; ssh user@bar.example.com sh -c =E2=80=9Ccat x* > foo.pdf; rm x*= =E2=80=9D

On Fri, Aug 11, 2023 at 12:27 PM Joe Schaefer <joesuf4@gmail.com> wrote:
If it=E2=80=99s just a single file, split i= t into chunks.

On Fri, Aug 11, 2023 at 12:25 PM Joe Schaefer <joesuf4@gmail.com> = wrote:
Why don=E2=80=99t you ju= st use xargs -P until you=E2=80=99ve exhausted your CPU capacity?

On Fri, Aug 11, 2023 at 10:10 AM void <void@f-m.fm> wrote:
On Fri, Aug 11, 2023 at 12:21:33PM +0100, Jamie Landeg-Jones w= rote:

>rsync just spawns an ssh command, so would probably behave similarly.
I'm hoping that rsync will spawn many ssh. Need to look at max sessions=
on both ends of the connection.

Since encountering the described problem, the person at the other
end is away for the week so have not been able to test thoroughly.
What I have been able to test shows that there is spiky latency
in the connection, as well as slow speed, single-threaded.

>Another thing, scp transfers from my test Rpi2 are much slower than the= network
>can handle due to the CPU use, which hits 100% on one cpu whilst it'= ;s running.
>So, check that CPU isn't the bottleneck too.

Yup. That won't be happening here. Dual xenon with 56 cores at remote end and same (but with 32 cores) at this end

>As for the speed, I just tested sftp to transfer a file of random data,= 2 GB in
>size from one FreeBSD box in London to another in France:
>
>The final result was:
>
> 100% 2000MB=C2=A0 43.5MB/s=C2=A0 =C2=A000:46=C2=A0 (Note, that's M= egaBYTES/s)

I ran a similar test.
Sending system is on synchronous gigabit fibre on US east coast,
receiving system is near London on 110/21 fibre (so, gigabit in the sending=
direction):

100% 2000MB=C2=A0 =C2=A07.2MB/s=C2=A0 =C2=A004:36

using rsync -azP : 2,097,152,000 100%=C2=A0 =C2=A0 6.81MB/s=C2=A0 =C2=A0 0:= 04:53 (xfr#1, to-chk=3D0/1)

the speed fluctulates a lot. Both systems are quiet in a network and OS sen= se
for the duration of the test.

>The London box is pretty old, and is a virtual host scheduled to be dec= omissioned.
>It is running an old openssl 1.X, openssh 8.8 and is a single core 2.4G= hz amd64 box.
>
>The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 = and openssl 1.1.1

both ends here are running very recent -current, so ssl/ssh is
OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023

>Anything more I can tell you that may help?

Thanks very much for your input. I'm certain it's not a freebsd pro= blem.

--

--0000000000009f218f0602a8864c-- From nobody Fri Aug 11 16:53:44 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RMqd14Zj8z4m8p4 for ; Fri, 11 Aug 2023 16:53:57 +0000 (UTC) (envelope-from joesuf4@gmail.com) Received: from mail-wm1-x335.google.com (mail-wm1-x335.google.com [IPv6:2a00:1450:4864:20::335]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4RMqd04LZxz3D0K for ; Fri, 11 Aug 2023 16:53:56 +0000 (UTC) (envelope-from joesuf4@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20221208 header.b=suOyNSpQ; spf=pass (mx1.freebsd.org: domain of joesuf4@gmail.com designates 2a00:1450:4864:20::335 as permitted sender) smtp.mailfrom=joesuf4@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-wm1-x335.google.com with SMTP id 5b1f17b1804b1-3fe8a158fcbso5603015e9.2 for ; Fri, 11 Aug 2023 09:53:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691772835; x=1692377635; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=aRR9+UzdGQ/bTD/iuZx3730jjbbieaXHuGn6F7fJC8s=; b=suOyNSpQ9z/MU7JNCtGzihbDif67situWFHcFzy9uQYy4i4Nb3A/dorv/8R0bUZSiJ 2p5b5mipnya+9SqYLtI2jxWJyRitxctuZfJnvK2h7F1PYa9Biv9X7/zXqEKF0rFNWBPn /QRccaT6lxDGvN9IDa7ZleUZGK+2eIC9nX6zLLFB+hYJ7zQ270iOSfruQaReNDX0IBhv 1GIp83A0trHRVzRyppKWrFUQ2QPh1nmn/Gifz/CKLjbZtOxf1jJrt+ODeT7l+LDWXgKN gNwb8iq6BXHbQYBsYrNqqeYXRU0zjy82AOD4PKbe/rJlaYCQp47WEc4dDNantPfDwsBm OEVA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691772835; x=1692377635; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=aRR9+UzdGQ/bTD/iuZx3730jjbbieaXHuGn6F7fJC8s=; b=STjILU0r9+gUVTdiErAGnnnmumnbeAZz1/73gZk1bPpt8O2Nx0RlA5PFCLATeGcP2+ 76DMPKOZIb3fvnxxlHv29Iis+JKJ1c/Dagj94QDc6ac4GhZ5USjoo59FXUDv5gKNFE7Z djuYuR7HuysYfdxIULrtxrL0XbPsaeosSU/Acyo+2d1WY8WImR5K3O9dH5QtN5Z0Iq0q b6dwOPHLRAMytc0sPi63S2rcbYTwTHh0cRwUaA/bU1spxUzygbCOPDC3JUYM/rC5oOQ8 s2xhf3WGCZIvsvPmQpCCZa5FrzOPj35MIAxTaE0TDzJoZMnKEv8iTyavxwP7XGu/9LWq KwVA== X-Gm-Message-State: AOJu0Yw/p3i0yu3bQya23N+5AciOkOoZD+drH8T5Y5oyRvQ1710ZyjCO plUuElrLwz1I2BDj2kZxf6T3f4bkTgsZLyHYNzZ3jKZw X-Google-Smtp-Source: AGHT+IFfzBzythsmXAO2dFpiNJl4NVehgmC1yBtzF9sgoj4PDRN58794HexOyozHFrojmmGy0FOM/7uBO/H0xFhojIM= X-Received: by 2002:adf:db0a:0:b0:314:2e95:1ec9 with SMTP id s10-20020adfdb0a000000b003142e951ec9mr1884434wri.10.1691772834760; Fri, 11 Aug 2023 09:53:54 -0700 (PDT) List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 References: <202308111121.37BBLX0J064263@donotpassgo.dyslexicfish.net> In-Reply-To: From: Joe Schaefer Date: Fri, 11 Aug 2023 12:53:44 -0400 Message-ID: Subject: Re: can sftp be made multi-threaded? To: freebsd-hackers@freebsd.org Content-Type: multipart/alternative; boundary="000000000000db4d3d0602a88e19" X-Spamd-Result: default: False [-2.90 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-0.97)[-0.971]; NEURAL_HAM_LONG(-0.97)[-0.969]; NEURAL_HAM_MEDIUM(-0.96)[-0.962]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20221208]; R_SPF_ALLOW(-0.20)[+ip6:2a00:1450:4000::/36:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ARC_NA(0.00)[]; ASN(0.00)[asn:15169, ipnet:2a00:1450::/32, country:US]; RCVD_IN_DNSWL_NONE(0.00)[2a00:1450:4864:20::335:from]; DKIM_TRACE(0.00)[gmail.com:+]; MID_RHS_MATCH_FROMTLD(0.00)[]; TO_DN_NONE(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_COUNT_ONE(0.00)[1]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org] X-Spamd-Bar: -- X-Rspamd-Queue-Id: 4RMqd04LZxz3D0K --000000000000db4d3d0602a88e19 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Put the split files on tmpfs for full effect On Fri, Aug 11, 2023 at 12:51 PM Joe Schaefer wrote: > % split -n $(nproc) foo.pdf; ls x* | xargs -P 0 -J % scp % > user@bar.example.com:%; rm x*; ssh user@bar.example.com sh -c =E2=80=9Cc= at x* > > foo.pdf; rm x*=E2=80=9D > > On Fri, Aug 11, 2023 at 12:27 PM Joe Schaefer wrote: > >> If it=E2=80=99s just a single file, split it into chunks. >> >> On Fri, Aug 11, 2023 at 12:25 PM Joe Schaefer wrote: >> >>> Why don=E2=80=99t you just use xargs -P until you=E2=80=99ve exhausted = your CPU capacity? >>> >>> On Fri, Aug 11, 2023 at 10:10 AM void wrote: >>> >>>> On Fri, Aug 11, 2023 at 12:21:33PM +0100, Jamie Landeg-Jones wrote: >>>> >>>> >rsync just spawns an ssh command, so would probably behave similarly. >>>> >>>> I'm hoping that rsync will spawn many ssh. Need to look at max session= s >>>> on both ends of the connection. >>>> >>>> Since encountering the described problem, the person at the other >>>> end is away for the week so have not been able to test thoroughly. >>>> What I have been able to test shows that there is spiky latency >>>> in the connection, as well as slow speed, single-threaded. >>>> >>>> >Another thing, scp transfers from my test Rpi2 are much slower than >>>> the network >>>> >can handle due to the CPU use, which hits 100% on one cpu whilst it's >>>> running. >>>> >So, check that CPU isn't the bottleneck too. >>>> >>>> Yup. That won't be happening here. Dual xenon with 56 cores at remote >>>> end and same (but with 32 cores) at this end >>>> >>>> >As for the speed, I just tested sftp to transfer a file of random >>>> data, 2 GB in >>>> >size from one FreeBSD box in London to another in France: >>>> > >>>> >The final result was: >>>> > >>>> > 100% 2000MB 43.5MB/s 00:46 (Note, that's MegaBYTES/s) >>>> >>>> I ran a similar test. >>>> Sending system is on synchronous gigabit fibre on US east coast, >>>> receiving system is near London on 110/21 fibre (so, gigabit in the >>>> sending >>>> direction): >>>> >>>> 100% 2000MB 7.2MB/s 04:36 >>>> >>>> using rsync -azP : 2,097,152,000 100% 6.81MB/s 0:04:53 (xfr#1, >>>> to-chk=3D0/1) >>>> >>>> the speed fluctulates a lot. Both systems are quiet in a network and O= S >>>> sense >>>> for the duration of the test. >>>> >>>> >The London box is pretty old, and is a virtual host scheduled to be >>>> decomissioned. >>>> >It is running an old openssl 1.X, openssh 8.8 and is a single core >>>> 2.4Ghz amd64 box. >>>> > >>>> >The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.= 2 >>>> and openssl 1.1.1 >>>> >>>> both ends here are running very recent -current, so ssl/ssh is >>>> OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023 >>>> >>>> >Anything more I can tell you that may help? >>>> >>>> Thanks very much for your input. I'm certain it's not a freebsd proble= m. >>>> >>>> -- >>>> >>>> --000000000000db4d3d0602a88e19 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Put the split files on tmpfs for full effect=C2=A0
<= div>
On= Fri, Aug 11, 2023 at 12:51 PM Joe Schaefer <joesuf4@gmail.com> wrote:
% split -n $(nproc) foo.pdf; ls x* | xargs -P 0 -= J % scp % =C2=A0user@bar.example.com:%; rm x*; ssh user@bar.example.com sh -c =E2=80=9Cc= at x* > foo.pdf; rm x*=E2=80=9D

On Fri, Aug 11, 2023 at 12:27 PM Joe= Schaefer <joesuf= 4@gmail.com> wrote:
If i= t=E2=80=99s just a single file, split it into chunks.

On Fri, Aug 11, 2= 023 at 12:25 PM Joe Schaefer <joesuf4@gmail.com> wrote:
Why don=E2=80=99t you just use xargs -P until you=E2=80=99ve= exhausted your CPU capacity?

On Fri, Aug 11, 2= 023 at 10:10 AM void <v= oid@f-m.fm> wrote:
On Fri, Aug 11, 2023 a= t 12:21:33PM +0100, Jamie Landeg-Jones wrote:

>rsync just spawns an ssh command, so would probably behave similarly.
I'm hoping that rsync will spawn many ssh. Need to look at max sessions=
on both ends of the connection.

Since encountering the described problem, the person at the other
end is away for the week so have not been able to test thoroughly.
What I have been able to test shows that there is spiky latency
in the connection, as well as slow speed, single-threaded.

>Another thing, scp transfers from my test Rpi2 are much slower than the= network
>can handle due to the CPU use, which hits 100% on one cpu whilst it'= ;s running.
>So, check that CPU isn't the bottleneck too.

Yup. That won't be happening here. Dual xenon with 56 cores at remote end and same (but with 32 cores) at this end

>As for the speed, I just tested sftp to transfer a file of random data,= 2 GB in
>size from one FreeBSD box in London to another in France:
>
>The final result was:
>
> 100% 2000MB=C2=A0 43.5MB/s=C2=A0 =C2=A000:46=C2=A0 (Note, that's M= egaBYTES/s)

I ran a similar test.
Sending system is on synchronous gigabit fibre on US east coast,
receiving system is near London on 110/21 fibre (so, gigabit in the sending=
direction):

100% 2000MB=C2=A0 =C2=A07.2MB/s=C2=A0 =C2=A004:36

using rsync -azP : 2,097,152,000 100%=C2=A0 =C2=A0 6.81MB/s=C2=A0 =C2=A0 0:= 04:53 (xfr#1, to-chk=3D0/1)

the speed fluctulates a lot. Both systems are quiet in a network and OS sen= se
for the duration of the test.

>The London box is pretty old, and is a virtual host scheduled to be dec= omissioned.
>It is running an old openssl 1.X, openssh 8.8 and is a single core 2.4G= hz amd64 box.
>
>The France box is a 4 core bare metal 3.1Ghz and64 running openssh 9.2 = and openssl 1.1.1

both ends here are running very recent -current, so ssl/ssh is
OpenSSH_9.3p1, OpenSSL 3.0.9 30 May 2023

>Anything more I can tell you that may help?

Thanks very much for your input. I'm certain it's not a freebsd pro= blem.

--

--000000000000db4d3d0602a88e19-- From nobody Sat Aug 12 01:06:40 2023 X-Original-To: freebsd-hackers@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4RN2Yf6Jfrz4q2tM for ; Sat, 12 Aug 2023 01:06:46 +0000 (UTC) (envelope-from void@f-m.fm) Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4RN2Yd2RP7z4RcY for ; Sat, 12 Aug 2023 01:06:45 +0000 (UTC) (envelope-from void@f-m.fm) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=f-m.fm header.s=fm3 header.b=jKTXRU8Y; dkim=pass header.d=messagingengine.com header.s=fm3 header.b="k SBaWWr"; spf=pass (mx1.freebsd.org: domain of void@f-m.fm designates 66.111.4.26 as permitted sender) smtp.mailfrom=void@f-m.fm; dmarc=pass (policy=none) header.from=f-m.fm Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 67AAB5C00A7 for ; Fri, 11 Aug 2023 21:06:43 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 11 Aug 2023 21:06:43 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f-m.fm; h=cc :content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to; s=fm3; t= 1691802403; x=1691888803; bh=VhUYFADou3b3thflTYt3o7n782V44iXxk5+ 2fabuE4g=; b=jKTXRU8YX99LJ/P6ff61GseE49US9oA+k3MI/qQvMthxaIBlDjB v4SsLCudpf13eyMLXzdqzAQOLzI1VCTZ621wpqVLQK8SbsLIyGNRhqFn5sLk2nyr ePDYYPrD1KlZamwQJINbys6k+u6Ju4L3eWRG11b5KPDDC+iY0gzE61F/lUILh2N1 VRxJEt/6JUw31ymktNyLc0Kg3Dukmo6ISodoj2WV/hA7fWn5p7xcjQdhyo6mrdtL Qva3nvIdZwJr3NFoXgN0HcrTbY2ezJPcIyrDI1vTc6It0tb5vjqqPnahC4jgsZgd FDAAAXoIarPZiOmwUnoI15cX1ZMYRk/cn0w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1691802403; x= 1691888803; bh=VhUYFADou3b3thflTYt3o7n782V44iXxk5+2fabuE4g=; b=k SBaWWr7ud02dffxX6ltO2K00i2iGxgz/RrPuinkeqGqfogIKzKwEsCTpPXvasgb5 HKo2atf8GoX3TOFYw0RTc2g4uCzFQ5uvI8W3010QR/cPOBaBuomm5oCI6TfQ4NGu z4MUrjPzJPdqnX+FS4O1tFaTpEBFsBmRskMiPgiJhdX7DcdwzmAdj1cvJKP5EHTv FSHJly4M3BHaqbW5pm9wHwCjGCrj3P+kWfzcopIt9B61cjRWtm3pwxOLmNoahYmz T35JLENr+WeND6JMQp2KbU8Imvw5v5I7Ox5iuqvkINFmaK7qyqYCsnP9YXe3u8ZD akAUXIxqHW2S3Py1gJISA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedviedrleelgdegvdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepfffhvffukfhfgggtugfgjgesthekro dttddtjeenucfhrhhomhepvhhoihguuceovhhoihgusehfqdhmrdhfmheqnecuggftrfgr thhtvghrnhepfeeltdegtdeuleffheehgeehgfelhfejvdevgeekkeeghfehhfekgedvle egvddunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhep vhhoihgusehfqdhmrdhfmh X-ME-Proxy: Feedback-ID: i2541463c:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA for ; Fri, 11 Aug 2023 21:06:42 -0400 (EDT) Date: Sat, 12 Aug 2023 02:06:40 +0100 From: void To: freebsd-hackers@freebsd.org Subject: Re: can sftp be made multi-threaded? Message-ID: Mail-Followup-To: freebsd-hackers@freebsd.org References: <202308111121.37BBLX0J064263@donotpassgo.dyslexicfish.net> List-Id: Technical discussions relating to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-hackers List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-hackers@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spamd-Result: default: False [-3.68 / 15.00]; DWL_DNSWL_LOW(-1.00)[messagingengine.com:dkim]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-0.999]; NEURAL_HAM_LONG(-0.99)[-0.986]; DMARC_POLICY_ALLOW(-0.50)[f-m.fm,none]; MID_RHS_NOT_FQDN(0.50)[]; R_SPF_ALLOW(-0.20)[+ip4:66.111.4.26]; R_DKIM_ALLOW(-0.20)[f-m.fm:s=fm3,messagingengine.com:s=fm3]; RWL_MAILSPIKE_GOOD(-0.10)[66.111.4.26:from]; RCVD_IN_DNSWL_LOW(-0.10)[66.111.4.26:from]; MIME_GOOD(-0.10)[text/plain]; FROM_HAS_DN(0.00)[]; PREVIOUSLY_DELIVERED(0.00)[freebsd-hackers@freebsd.org]; RCPT_COUNT_ONE(0.00)[1]; TO_MATCH_ENVRCPT_ALL(0.00)[]; ARC_NA(0.00)[]; ASN(0.00)[asn:19151, ipnet:66.111.4.0/24, country:US]; MLMMJ_DEST(0.00)[freebsd-hackers@freebsd.org]; RCVD_COUNT_THREE(0.00)[3]; TO_DN_NONE(0.00)[]; FREEMAIL_FROM(0.00)[f-m.fm]; MIME_TRACE(0.00)[0:+]; DKIM_TRACE(0.00)[f-m.fm:+,messagingengine.com:+]; RCVD_TLS_LAST(0.00)[]; FROM_EQ_ENVFROM(0.00)[]; FREEMAIL_ENVFROM(0.00)[f-m.fm]; RCVD_VIA_SMTP_AUTH(0.00)[] X-Spamd-Bar: --- X-Rspamd-Queue-Id: 4RN2Yd2RP7z4RcY On Fri, Aug 11, 2023 at 12:51:25PM -0400, Joe Schaefer wrote: >% split -n $(nproc) foo.pdf; ls x* | xargs -P 0 -J % scp % > user@bar.example.com:%; rm x*; ssh user@bar.example.com sh -c “cat x* > >foo.pdf; rm x*” Thanks for that, I'll try it. --