From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 210AC158083 for ; Sat, 14 Sep 2024 00:50:25 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A4017E29AC; Sat, 14 Sep 2024 00:50:17 +0000 (UTC) Received: from mout.gmx.net (mout.gmx.net [212.227.17.21]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (prime256v1) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 0D476E29A5 for ; Sat, 14 Sep 2024 00:50:16 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmx.de; s=s31663417; t=1726275010; x=1726879810; i=warp_7@gmx.de; bh=bAO8ZCIT2T8krc51/s8bXENUh7q4lsAOVf2O1/oV8Mc=; h=X-UI-Sender-Class:Date:From:To:Subject:Message-ID:References: MIME-Version:Content-Type:In-Reply-To:cc: content-transfer-encoding:content-type:date:from:message-id: mime-version:reply-to:subject:to; b=t44IBV4mfLFALZidwnZM2MoNkIvJo0OWkL0dlij6eum9RzIx123wuT6pP3E12f0T fuGyc2W7pB82TPk9JSJJ/jdiOXRID2eA3h4xrFJ9lwYbKnfwsl4cmZi03ktUvoR2S 5TSB3Rb661QYQa8wAQ1mijUbqDC0ENmLhGw1wdwSFWVSUfb8wLWDyc+0Jreem9Bvc WEDTyObDc1Ig1vBLhY2NZHO3Xd5fUlJSvm9Eco2WwueMqFlrNHdzmu7w7eqm/tuUt QOTDbqLW6049iaWgJtykSrC+DvIhpuZwopmOG6wE60QrulhH/hmUFXp+qjpCOs7vG HQGKNVO+GKS2tEdvVA== X-UI-Sender-Class: 724b4f7f-cbec-4199-ad4e-598c01a50d3a Received: from kern ([94.134.20.85]) by mail.gmx.net (mrgmx104 [212.227.17.168]) with ESMTPSA (Nemesis) id 1N7R1J-1rvFRH1LuX-017lSp for ; Sat, 14 Sep 2024 02:50:10 +0200 Date: Sat, 14 Sep 2024 02:50:08 +0200 From: Frank Steinmetzger To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Dolphin confusing different run instances. Message-ID: Mail-Followup-To: gentoo-user@lists.gentoo.org References: <3e29dec5-eb09-8c19-bff4-7110e1df65e8@gmail.com> <5654a65a-33bd-9914-4af3-95cc0f97a1de@gmail.com> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="LMP1u3Wv4QIlZVsE" Content-Disposition: inline In-Reply-To: User-Agent: Mutt 2.2.13; VIM - Vi IMproved 9.1 X-Provags-ID: V03:K1:ioSKzLNRb1bFj903TdK9E0o3pUW5ZAI7PAQN79rEF0b5EwtBQtn 3Fn6I+P8HNgkXK0aFNQQgC/3jbLrA6/yk7NDrXD+NxhJNrikRE375pVBS7Da6WAnzCibc0k 4Ukx62Gm9M+WBAmJtRnNmVc2HKPhZo90cRRaDG7l4zrtksuGCYm8/2hGW9Lh6EKG7rlXU/k 84km5RKXPNnMzs0C9xImA== X-Spam-Flag: NO UI-OutboundReport: notjunk:1;M01:P0:/aJdIztbDEU=;M8p7f859DfQBc8aKpRgBXpG97cG j5YXUM/+dpV2ipRtdSg1p7YMYOE3YTWsHnv/21uT87ur2U/o7hFNodXKNV53GwkKtmEqTzAUD Dg0u5nTe+7K2Cn0Jg5HNLAC4a7xSN0YzGQM98Onv88JgTPm+Av/WfnP50GcmciEYoWeJGe0LM L1IGlR4642300gHu1B4RT9WV1JPWNdiJuyn3tVdRm7E7AqD/nQprgkyr26jJ1lnS5btPIKV4P sCvt+RIO6JQwVGp1snrdR9RVCbvvKiNgZXsDZgboPPLaL/1c++WPxvh7NK3wt8LgChrJrXp/i X56wQMlNQ+6o3FmPVXvH4xHk6mkXLeoFlEwxHmMrn9cGC8choIPbwX1zoeKil2nGOswoYyRsd zmx9+gRd3QKooZXQk1ipPj1B9/CZflKUWj7oQl4KL02hvgl49UNfH1TapIqBz4zna9YCEBqm7 WMokIhMN3rWzM6kmny0ItlOrQlXUIWBpdR5e5uY25AD80vV9iqPiQv6iw6W/pS1rK6bLRXGqr mw90YUiCBThc0JnzMYX6OQEJa3W9qIIg6/7zUBvAJRre4bScPjuJprGHHDWyVOnvKuyxGZnAR UC9Jh2/tFwUquUwEoEvpWbl1/K0DjQqP2A43HXygkZ76MMw9MuRucOqWi1q8NLEhAJ8HGlY8l q1KUTOknOjWfSul0qsFwqTLw6kdKdslCkSSvHDWcjx4wB5KVZuzNtIDrJmbEPDmGaqHghxAxV SoVIziw4Xd2H5bWXqskxtQ8BrPDXV5bkCcqfGI7ctPioIMA8pbeyrWL+c4aEDyTkiQIm21m6r R5/PwTfALqk1bF7O2znTGFrQ== X-Archives-Salt: 8cf4a425-6d4d-4173-8164-df2fd87e1844 X-Archives-Hash: 22b86a3967de8d04dbab01133f3d2be0 --LMP1u3Wv4QIlZVsE Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Am Fri, Sep 13, 2024 at 01:19:00AM -0500 schrieb Dale: > >> P. S.=C2=A0 Planning to try that checksum script soon.=C2=A0 It's a la= rge number > >> of files so it will take a long time to run.=C2=A0 I think you mention= ed that > >> if stopped, it will resume where it left off. > > Only if it creates checksums, because it knows by the existence of chec= ksums=20 > > where to resume. But if you want to read checksums and verify them, you= need=20 > > to use arguments to tell it how many directories to process and how man= y to=20 > > skip at the beginning. > > > > Perhaps try it first with a few small directories to get a feel for its= =20 > > behaviour. The normal way to go is: > > > > dh -u [DIR] to create the checksum files > > dh [DIR] do read it back > > Use the --skip option to skip the given number of dirs at the beginning. > > > > Remember that by default it will not create checksums in directories th= at=20 > > have subdirectories. I know this sounds a little strange, but for a=20 > > hierarchy of music albums, this seemed sensible 10 years ago. > > >=20 > Well, I read through the help page and settled on this.=C2=A0 I might have > did this wrong.=C2=A0 ;-) >=20 > /root/dh -c -F 1Checksums.md5 -v >=20 > Right now I have the command in /root.=C2=A0 I just did a cd to the parent > directory I wanted it to work on and then ran that command.=C2=A0 Right n= ow, > it is working on this bit. >=20 >=20 > (dir 141 of 631) >=20 > and >=20 > (file=C2=A0 8079 of 34061) I am thinking about adding filesize information, but that would require=20 updating the status line during the processing of a file instead of only=20 between files. That=E2=80=99s not trivial, as it involves timers and thread= s. > I was wondering tho, is there a way to make it put all the checksum > files in one place, like a directory call checksums, and they just all > go in there? Hm =E2=80=A6 from an algorithmic point of view, it would actually not be th= at=20 complicated by creating a shortened filename from the source directory, but= =20 the real-world use seems a bit far-fetched. Checksums should be close to=20 their data. If you have read errors for either, then the other is useless= =20 anyways. :D > Or just a single file in the parent directory?=C2=A0 That way > the files aren't in each directory. That=E2=80=99s what the -s option is for. This will create only one checksu= m file at=20 the root level for each directory argument. So if you run `dh -us foo/ bar/= `,=20 then it will go into foo/, create one checksum file there and put all lines= =20 into that one file, even for subdirectories, and do the same in bar/. However, at the moment automatically detecting and properly verifying those= =20 files is still in the works. So I think you have to use the -s option or -F= =20 all to read them. > Thing is, can I still just run it > on one directory if I have a suspected bad one? Not with one checksum file at the root level for an entire tree. The way I= =20 would handle this case: run dh -u on the directory of interest and then=20 compare the checksums in the root-level file and the newly created file wit= h=20 a diff tool. Or copy the lines from the existing checksum file, create a ne= w=20 file in the directory of interest, remove the directory part of the paths= =20 and then run dh on just that directory. --=20 Gr=C3=BC=C3=9Fe | Greetings | Salut | Qapla=E2=80=99 I don=E2=80=99t have a problem with alcohol, just without! --LMP1u3Wv4QIlZVsE Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQIzBAABCgAdFiEEVbE9o2D2lE5fhoVsizG+tUDUMMoFAmbk3b4ACgkQizG+tUDU MMqN3w/+IlBhkltO3YQQ1tFB3zpK14GuKm8bqpaZ441n3QOIFqznxoJWpQD8Foik XjbSrieFEd7E+09F0fKUJ2jguh95EIBv8S2CzSaEEZ2oVBI4L5qaX/wgy7rO228s s+d6ekXrnxntQCyHDCiONPcI2yl1zzm7X6DE/JeFCbfNESu2XyiCvaO4gscyA3nY vfOebu1eH42dG4N77+MIzCl0PKB/QVXzKxOUGtn1nAEVB4PZtpdEkDwNqPkg3sdz JKoOYX3MT46lj8mt8+WhlM+LACFPRs7kGGq7vR6Kk32X6mJXGtiwNHLPii0Nvq/G uGkCgFbtQhubRthuzaaoA1WvdfwotRVEK6ScfeSDOSwmHUm0EKWIxBQ9s+izUo/V IXZceDUjSOO3riUUcX9vepLNVg488oIeyWureO3v8cr/1Kg1QFOgzYQor93CWnMH xcvV3INPIaUIO+aSkAkQFhedGjgMd+1HuaOYhSVgBlsvD+hObCtduwf/Wynp5lwG Op6SVyAC0FdL8govzlzCNPs4vgc/4oF1Wb1sIaon7Nu89NBZE1RDAuZi+/q5bhyD nnYm0QmDYLO4qIOB1nlgbl7IDzSs9cI3UhgWbL30hwSLSXj5xG0b/zM2CmB4UJ9N 60njmZFiAh8uOzeSye2WT51pQFcaPh9aH8O6Jnf9B9Z+FfRL82k= =gPha -----END PGP SIGNATURE----- --LMP1u3Wv4QIlZVsE--