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.6 required=5.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 E494E23D83 for ; Tue, 7 May 2024 00:20:21 +0200 (CEST) Received: from mail.cock.li ([37.120.193.123]) by 9front; Mon May 6 18:18:19 -0400 2024 Date: Tue, 7 May 2024 00:18:14 +0200 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=firemail.cc; s=mail; t=1715033896; bh=zcmdrVjC45KtdI812xnkipJIT0OgsFfzbR7ksFshRQg=; h=Date:From:To:Cc:Subject:Reply-To:References:In-Reply-To:From; b=M5CK4032ww8Br4n3a/LfcfgefMEwoVX7Csz3S9ebbuPYcmM23CU1xvj6sNN7qwcPL qQecATyTsve0Mcnhwjr3Qr7pc4RPQ16gxl60Oddh1QVU3uRYYg7QAKulqapvAm2361 CuzWYuVJjltLOWLfgMAfmqbyD7RdMPSNAWdGvTzWTwJLaPsJJ7GmF0KYKrE9L4JKmH sLYW4kZ7zvZ3Y3PG0+WSFTtiqenUVw8Ts7YcBp6xdpsZuAoacKVWF4Xe9vLDrJjsz4 I2q7139xBRrx9V/HZpfp2XVhM3YS/BUha7Y/axgUO3jwO3it5Vx8HfkY8TO9acMIEp g2oGgQIlByHfA== From: Rocky Hotas To: 9front@9front.org Cc: ori@eigenstate.org Message-ID: <4azdxd3t3x3whti6dlyfn75pl4wzodvs3gzsbu5t7xcnqmnuuc@kxfwuan7u5mw> References: <7D3BF4392AC2C46E8146B2A18FA14471@eigenstate.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7D3BF4392AC2C46E8146B2A18FA14471@eigenstate.org> List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: immutable patented software app-aware optimizer Subject: Re: Re: [9front] Enabling a service Reply-To: 9front@9front.org Precedence: bulk On mag 06 8:43, ori@eigenstate.org wrote: > > yes, listen(1) is only started on cpu servers by default. > you can run it manually if you want. Ok, instead of creating a CPU server I would prefer (if possible) to launch listen manually on my current machine. But it is listen(8), not listen(1), isn't it? Which is the correct syntax to create a tcp listener on port 7 which is an echo service (basically, what performs /rc/bin/service/!tcp7)? I couldn't find any example. Bye, Rocky