From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham
	autolearn_force=no version=3.4.4
Received: (qmail 4139 invoked from network); 1 Oct 2023 00:40:00 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 1 Oct 2023 00:40:00 -0000
Received: from gaff.inri.net ([168.235.71.243]) by 9front; Sat Sep 30 20:35:12 -0400 2023
Message-ID: <DDF801119CF0AF7FA40847F2C54A7614@gaff.inri.net>
Date: Sat, 30 Sep 2023 20:35:12 -0400
From: sl@stanleylieber.com
To: 9front@9front.org
In-Reply-To: <792B28B1EF73B7760D012519D9DDAA5B@gaff.inri.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: distributed generic hosting replication 
Subject: Re: [9front] upas/fs lstk(), one more time
Reply-To: 9front@9front.org
Precedence: bulk

i backed up my mbox and added messages back in batches, checking after
each batch that upas/fs was still able to open it.  i did this until i
found a specific message upas/fs choked on.

sl