From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <9front-bounces@9front.inri.net> X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from 9front.inri.net (9front.inri.net [168.235.81.73]) by inbox.vuxu.org (Postfix) with ESMTP id 0FAC8208F9 for ; Tue, 7 May 2024 11:16:10 +0200 (CEST) Received: from sirjofri.de ([5.45.105.127]) by 9front; Tue May 7 05:14:57 -0400 2024 Received: from dummy.faircode.eu ([95.90.217.91]) by sirjofri.de; Tue May 7 11:14:52 +0200 2024 Date: Tue, 7 May 2024 11:14:51 +0200 (GMT+02:00) From: sirjofri To: 9front@9front.org Message-ID: In-Reply-To: References: <4azdxd3t3x3whti6dlyfn75pl4wzodvs3gzsbu5t7xcnqmnuuc@kxfwuan7u5mw> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Correlation-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: non-blocking RESTful map/reduce backend Subject: Re: [9front] Enabling a service Reply-To: 9front@9front.org Precedence: bulk Hi, Note that for single services that should run temporarily it's advised to use listen1 instead of listen. In the other case, where you want your machine to always serve services, that machine is most probably a cpu by definition. Nowadays there's no reason to not run a cpu if you need services. In the beginning there were different kernels if I remember correctly, which meant a big difference, but nowadays it's only a different configuration. Of course it all depends on your specific use case. Listen is btw one of the reasons I like Plan 9. It's much easier to configure services than on any linux system. sirjofri