From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI autolearn=ham autolearn_force=no version=3.4.4 Received: from alyss.skarnet.org (alyss.skarnet.org [95.142.172.232]) by inbox.vuxu.org (Postfix) with SMTP id 4640F230FC for ; Tue, 6 Aug 2024 20:37:58 +0200 (CEST) Received: (qmail 65307 invoked by uid 89); 6 Aug 2024 18:38:23 -0000 Mailing-List: contact supervision-help@list.skarnet.org; run by ezmlm Sender: Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Received: (qmail 65300 invoked from network); 6 Aug 2024 18:38:23 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1722969475; x=1723574275; darn=list.skarnet.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=6JbGXKK2e0qOYDKcq4ReM5MPpaGtrBj6o0Plx3HFRc0=; b=bxl1TMdFWo4u0hLjuizbBripDnOq5QpsWefWlrouSeJCLBQtd0UrFQ/QME+OxDVUNo dz30qKI9tMql5iffXratyBmueLmlUFnkraGtUifhCFJxyHzv7geCvGXqamkb4l/n15em Elw16GkxpwSx1FY+Xquokj9F/t8gUtSDjW4MHgRTDHwYibVmu6ExzMXnns1rujDYHEgr okA1SdhhIlSgwbpLlgDT0fTHiaPs4Td9QJaoiblji1YQGwMdVkbftfP/lXMFW/qCccVd dnYlO7NwQVzCxCUtQhYygunD3gBlYQJYTon9vq278xRafSMEq3DXJT6G/GgumsC0qdw+ Q0CQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1722969475; x=1723574275; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=6JbGXKK2e0qOYDKcq4ReM5MPpaGtrBj6o0Plx3HFRc0=; b=KYg5UjreP1cbiJTTHsqkM0LDYrtwsNm32MZRp+oSJukgLCX2kj6o9zzXHx1HyXh2NY XU495RfncxH/6i+lUVkSVp5rrQjmzlNWAi6XFsBJbPCP5InTL4jADduZuo2mSzpRbE2A qOQtM76UuCLgD3ocISsqF1RWdDvVV2gFOtB5gfeTcyvHiALtN83iVJOvExuvXBF3dj7m /CyZ1W2i91Wvq8SS/lhapL6pIP60HtxUghNpgB5jXq1jQqGYDJ3WCPVuLcL7tsYVmse4 pSUNNl4j3nyWJ3eetSM2BELRXbgtqWAjMKzyPXimdEVxPZrzDXTriKk4KSZNwfPQ7N5r IITw== X-Gm-Message-State: AOJu0YyFX6w0wPXa1Sac6Qet9c9unRqn8gjqg4rE9+YCIVYAPetguzE8 O5zJ4FQU9/f9kJW0t6nhJqN4BZVP8Z06Wgdx5ZgLmy7SOJm95bZp8XoPGh4ABqe+wVJo3qC6nWu 9AratEd33gRtuZlJN1aBWPcvSKpxUdg9v X-Google-Smtp-Source: AGHT+IH2TJN/cBLrm8fwzt1/67hSjg54bxxw/rjOO81wnDhIQBidlf4TlfMNOu1CWXKfRXuel7MkdLvWDY96sVjBA28= X-Received: by 2002:a05:6902:18d3:b0:e0b:db06:18cc with SMTP id 3f1490d57ef6-e0bde2b11f8mr18965270276.12.1722969474670; Tue, 06 Aug 2024 11:37:54 -0700 (PDT) MIME-Version: 1.0 From: =?UTF-8?Q?Jan_K=C3=A4mpe?= Date: Tue, 6 Aug 2024 21:37:43 +0300 Message-ID: Subject: s6-socklog with -i ipport option To: supervision@list.skarnet.org Content-Type: multipart/alternative; boundary="0000000000007f28f6061f081715" --0000000000007f28f6061f081715 Content-Type: text/plain; charset="UTF-8" The clientip_clientport output seem incorrect in s6-socklog output when using "-i ipport" option. Example to reproduce; run $ s6-socklog -i 192.168.21.1:10514 Then send test syslog message to s6-socklog listening on the UDP port (here using "logger" on x86_64 debian linux) $ logger -n 192.168.21.1 -P 10514 "Sample log message" The (start of) s6-socklog produced log line "clientip_clientport" looks (usually) something like this: 5511368.21.1_: user.notice: Can anyone else try to re-produce/confirm? -J --0000000000007f28f6061f081715--