Github messages for voidlinux
 help / color / mirror / Atom feed
From: sbromberger <sbromberger@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] void-socklog: ucspi is configured to use tcpsvd which doesn't exist.
Date: Mon, 26 Dec 2022 17:19:13 +0100	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41300@inbox.vuxu.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 1339 bytes --]

New issue by sbromberger on void-packages repository

https://github.com/void-linux/void-packages/issues/41300

Description:
### Is this a new report?

Yes

### System Info

Void 6.0.13_1 x86_64 AuthenticAMD uptodate FF

### Package(s) Affected

void-socklog

### Does a report exist for this bug with the project's home (upstream) and/or another distro?

_No response_

### Expected behaviour

`socklog-conf ucspi-tcp nobody log` creates a ucspi-tcp configuration for soclog, but the `/etc/sv/socklog-ucspi/run` script refers to `tcpsvd`:

```
exec tcpsvd -vllogserver -unobody 0 "$PORT" socklog ucspi TCPREMOTEIP
```
which doesn't exist (as far as I can tell) for Void. Using `tcpserver` from s6-networking or from ucspi-tcp might work.

I expected the default installation of socklog-ucspi to reference a utility that exists on my system (or that can be installed).

### Actual behaviour

```
bash-5.1# head /var/log/socklog-ucspi-tcp/main/current
@4000000063a9c4ee2b51dddc ./run: 4: exec: tcpsvd: not found
@4000000063a9c4ef2b67cb24 ./run: 4: exec: tcpsvd: not found
@4000000063a9c4f02b843494 ./run: 4: exec: tcpsvd: not found
```

### Steps to reproduce

1. `xbps-install socklog-void xtools` (if not present)
2. `socklog-conf ucspi-tcp nobody log`
3. `head /var/log/socklog-ucspi-tcp/main/current`
4. `xlocate tcpsvd`

             reply	other threads:[~2022-12-26 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-26 16:19 sbromberger [this message]
2022-12-27 21:59 ` kruceter
2022-12-27 22:00 ` kruceter
2023-01-02 15:19 ` [ISSUE] [CLOSED] " leahneukirchen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-41300@inbox.vuxu.org \
    --to=sbromberger@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).