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=4.5 required=5.0 tests=BULK_RE_SUSP_NTLD, DATE_IN_PAST_12_24,DKIM_INVALID,DKIM_SIGNED,FROM_SUSPICIOUS_NTLD, PDS_OTHER_BAD_TLD autolearn=no autolearn_force=no version=3.4.4 Received: (qmail 25756 invoked from network); 1 Jun 2021 04:21:05 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 1 Jun 2021 04:21:05 -0000 Received: from out0.migadu.com ([94.23.1.103]) by 1ess; Mon May 31 10:58:55 -0400 2021 Message-ID: DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=a-b.xyz; s=key1; t=1622473130; 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-type: content-transfer-encoding:content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to; bh=R220uaboDKLvZ6tGq/4fM0pM5YhzEOnDgcV5ZoeN32M=; b=CiUHBBlADPkVBhly/peAHks8GDOvr38QfRCDdRsaPHdHWGbI7Z6vZbH5dbIayCGZTkL0XM XZh0V05ZtZcua82al4OypeXXQGN9r3uRPkX6x2n9RbjIeVWUSCIXLTG0GulheS/RhrH6lK rC3fj2WOzyWn/h+NDcyJYflRavOEYLGv+XIjj6TrqtjIBl9xTEaXfY+jrAieEIroRjWgCk jc2dlxq5KtjmZga1ZCLIwj9wuzB6nV0WGzFgEqALOF5gaEHqEsChSFTEAqrxl/x1Zl2ZvB RAIDwyeJfdl22RLbsvs16yqqO0SqhTzVU8C3gEzo/B0B9zL1Dml2yX7A5H3t2Q== Content-Type: text/plain; charset="UTF-8" To: 9front@9front.org Date: Mon, 31 May 2021 16:58:47 +0200 X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers. From: kvik@a-b.xyz In-Reply-To: <14875E53238A4C869B47B23B95272195@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Migadu-Flow: FLOW_OUT X-Migadu-Auth-User: kvik@a-b.xyz List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: persistence-scale strategy-aware generator Subject: Re: [9front] Shared env in child scripts Reply-To: 9front@9front.org Precedence: bulk Quoth kjn@9project.net: > I understand that it allows a child script to change env > values for its parent, but is that desirable? That's the idea but it's not how it works in practice due to rc caching the environments variable as its own variables, writing back the changes but never reloading after initial load. If you want two-way communication via environment the procs must make special arrangements, with env(3) being nothing more than a slightly convenient (and shitty) ramfs(4). In any case, making `rfork e` a default now is sure to break a lot of scripts in horrible ways -- which doesn't seem worth it. In theory the proposed default makes way more sense.