Date: Mon, 10 Jul 2017 19:38:59 +0200 From: Polytropon <freebsd@edvax.de> To: Matthias Apitz <guru@unixarea.de> Cc: <freebsd-questions@freebsd.org> Subject: Re: Unusual Question Message-ID: <20170710193859.3841a624.freebsd@edvax.de> In-Reply-To: <4eff21f6-84f2-4cc5-8b92-b7e787be8853@unixarea.de> References: <888578F8-AD68-4993-823C-152789F3C929@mail.sermon-archive.info> <52627.76.193.16.95.1499645892.squirrel@cosmo.uchicago.edu> <BF16E1CF-A889-4734-981E-2B68115FCD3C@mail.sermon-archive.info> <20170710052228.GA2338@c720-r314251> <20170710090547.15ee3afc07c09955ba621ae1@sohara.org> <4eff21f6-84f2-4cc5-8b92-b7e787be8853@unixarea.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 10 Jul 2017 17:36:19 +0200, Matthias Apitz wrote: > The OP should just compile an own version of dd(1) which punches lets say > every thousand blocks the current block number to see how far (or better > how less) it will walk through before the kernel halts/crashes. To extend this idea: I'd add a few continuous diagnostic messages (comparable to the ^T status display), so when the SSH connection finally drops, it's possible to see how far the dd process went. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20170710193859.3841a624.freebsd>