Github messages for voidlinux
 help / color / mirror / Atom feed
From: benalb <benalb@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] dhcpcd: ipv6nd_recvmsg: No such process
Date: Sun, 26 Mar 2023 11:49:00 +0200	[thread overview]
Message-ID: <20230326094900.iaQHTGkiviQkmNlVaneOIxtM69qwIZVIABEBs_bf-m8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-43024@inbox.vuxu.org>

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

Closed issue by benalb on void-packages repository

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

Description:
### Is this a new report?

Yes

### System Info

Void 6.1.20_1 x86_64 GenuineIntel uptodate rFFFFFFF

### Package(s) Affected

dhcpcd-9.4.1_2

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

A web search for "dhcpcd: ipv6nd_recvmsg" yields nothing. 

### Expected behaviour

dhcpcd should "just work".

### Actual behaviour

dhcpcd is spamming the logs:

`
2023-03-26T09:12:37.54829 daemon.err: Mar 26 11:12:37 dhcpcd[23095]: ipv6nd_recvmsg: No such process
2023-03-26T09:12:51.16793 daemon.err: Mar 26 11:12:51 dhcpcd[23095]: ipv6nd_recvmsg: No such process
`

[benalb@t470 ~]$    
grep -i ipv6nd /var/log/socklog/everything/current|wc -l
573

For now I was able to stop the errors adding 
`ipv4only`
to /etc/dhcpcd.conf

### Steps to reproduce

Just start dhcpcd.

      parent reply	other threads:[~2023-03-26  9:49 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-26  9:33 [ISSUE] " benalb
2023-03-26  9:48 ` benalb
2023-03-26  9:49 ` benalb [this message]

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=20230326094900.iaQHTGkiviQkmNlVaneOIxtM69qwIZVIABEBs_bf-m8@z \
    --to=benalb@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).