* [ISSUE] void-socklog: ucspi is configured to use tcpsvd which doesn't exist.
@ 2022-12-26 16:19 sbromberger
2022-12-27 21:59 ` kruceter
` (2 more replies)
0 siblings, 3 replies; 4+ messages in thread
From: sbromberger @ 2022-12-26 16:19 UTC (permalink / raw)
To: ml
[-- 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`
^ permalink raw reply [flat|nested] 4+ messages in thread* Re: void-socklog: ucspi is configured to use tcpsvd which doesn't exist. 2022-12-26 16:19 [ISSUE] void-socklog: ucspi is configured to use tcpsvd which doesn't exist sbromberger @ 2022-12-27 21:59 ` kruceter 2022-12-27 22:00 ` kruceter 2023-01-02 15:19 ` [ISSUE] [CLOSED] " leahneukirchen 2 siblings, 0 replies; 4+ messages in thread From: kruceter @ 2022-12-27 21:59 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 515 bytes --] New comment by kruceter on void-packages repository https://github.com/void-linux/void-packages/issues/41300#issuecomment-1366200454 Comment: I could reproduce the issue. According to `socklog-conf(8)`, > socklog-conf arranges for tcpsvd(1) to run socklog(8) under the uid > and gid of acct and to listen on the TCP socket 0.0.0.0:10116. tcpsvd(1) comes from http://smarden.org/ipsvd/index.html. Either ipsvd has to be packaged or socklog should be patched to use a different piece of software as well. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: void-socklog: ucspi is configured to use tcpsvd which doesn't exist. 2022-12-26 16:19 [ISSUE] void-socklog: ucspi is configured to use tcpsvd which doesn't exist sbromberger 2022-12-27 21:59 ` kruceter @ 2022-12-27 22:00 ` kruceter 2023-01-02 15:19 ` [ISSUE] [CLOSED] " leahneukirchen 2 siblings, 0 replies; 4+ messages in thread From: kruceter @ 2022-12-27 22:00 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 520 bytes --] New comment by kruceter on void-packages repository https://github.com/void-linux/void-packages/issues/41300#issuecomment-1366200454 Comment: I could reproduce the issue. According to `socklog-conf(8)`, > socklog-conf arranges for tcpsvd(1) to run socklog(8) under the uid > and gid of acct and to listen on the TCP socket 0.0.0.0:10116. `tcpsvd(1)` comes from http://smarden.org/ipsvd/index.html. Either ipsvd has to be packaged or socklog should be patched to use a different piece of software as well. ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ISSUE] [CLOSED] void-socklog: ucspi is configured to use tcpsvd which doesn't exist. 2022-12-26 16:19 [ISSUE] void-socklog: ucspi is configured to use tcpsvd which doesn't exist sbromberger 2022-12-27 21:59 ` kruceter 2022-12-27 22:00 ` kruceter @ 2023-01-02 15:19 ` leahneukirchen 2 siblings, 0 replies; 4+ messages in thread From: leahneukirchen @ 2023-01-02 15:19 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 1369 bytes --] Closed 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 socklog, 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` ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2023-01-02 15:19 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-12-26 16:19 [ISSUE] void-socklog: ucspi is configured to use tcpsvd which doesn't exist sbromberger 2022-12-27 21:59 ` kruceter 2022-12-27 22:00 ` kruceter 2023-01-02 15:19 ` [ISSUE] [CLOSED] " leahneukirchen
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).