Github messages for voidlinux
 help / color / mirror / Atom feed
From: deepcube <deepcube@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] wpa_supplicant: log to stdout instead of syslog
Date: Tue, 26 Sep 2023 17:04:09 +0200	[thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-46269@inbox.vuxu.org> (raw)

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

There is a new pull request by deepcube against master on the void-packages repository

https://github.com/deepcube/void-packages emg-wpa_supplicant-log-stdout
https://github.com/void-linux/void-packages/pull/46269

wpa_supplicant: log to stdout instead of syslog
A long time ago the wpa_supplicant service was changed[0] to log to syslog by default instead of the stdout.  This setting was carrier through a number of changes and persists to this day.  As such, wpa_supplicant will not log via the log/run mechanism as expected by default.

Remove the -s flag from the default and auto options so wpa_supplicant logs to stdout (and hence log/run) as expected for runit services.

[0] 62ae6738b59 (wpa_supplicant: log to syslog by default)



#### Testing the changes
- I tested the changes in this PR: **YES**

#### Local build testing
- I built this PR locally for my native architectures, (x86_64-musl, armv6l-musl)



A patch file from https://github.com/void-linux/void-packages/pull/46269.patch is attached

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-emg-wpa_supplicant-log-stdout-46269.patch --]
[-- Type: text/x-diff, Size: 1963 bytes --]

From f150907234a88c88736022171540ec6f07d904ea Mon Sep 17 00:00:00 2001
From: Evan Gates <evan.gates@gmail.com>
Date: Tue, 26 Sep 2023 08:02:39 -0600
Subject: [PATCH] wpa_supplicant: log to stdout instead of syslog

A long time ago the wpa_supplicant service was changed[0] to log to syslog
by default instead of the stdout.  This setting was carrier through a
number of changes and persists to this day.  As such, wpa_supplicant
will not log via the log/run mechanism as expected by default.

Remove the -s flag from the default and auto options so wpa_supplicant
logs to stdout (and hence log/run) as expected for runit services.

[0] 62ae6738b59 (wpa_supplicant: log to syslog by default)
---
 srcpkgs/wpa_supplicant/files/wpa_supplicant/run | 4 ++--
 srcpkgs/wpa_supplicant/template                 | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/srcpkgs/wpa_supplicant/files/wpa_supplicant/run b/srcpkgs/wpa_supplicant/files/wpa_supplicant/run
index d96bac26d1a5b..109a9e8339f50 100644
--- a/srcpkgs/wpa_supplicant/files/wpa_supplicant/run
+++ b/srcpkgs/wpa_supplicant/files/wpa_supplicant/run
@@ -1,10 +1,10 @@
 #!/bin/sh
 if [ -r ./conf ]; then
 	. ./conf
-	: ${OPTS:=-M -c ${CONF_FILE:-/etc/wpa_supplicant/wpa_supplicant.conf} ${WPA_INTERFACE:+-i ${WPA_INTERFACE}} ${DRIVER:+-D ${DRIVER}} -s}
+	: ${OPTS:=-M -c ${CONF_FILE:-/etc/wpa_supplicant/wpa_supplicant.conf} ${WPA_INTERFACE:+-i ${WPA_INTERFACE}} ${DRIVER:+-D ${DRIVER}} }
 else
 	. ./auto
-	OPTS="${AUTO} -s"
+	OPTS="${AUTO}"
 fi
 
 exec 2>&1
diff --git a/srcpkgs/wpa_supplicant/template b/srcpkgs/wpa_supplicant/template
index 87203097b009e..1706dbcfa7b71 100644
--- a/srcpkgs/wpa_supplicant/template
+++ b/srcpkgs/wpa_supplicant/template
@@ -1,7 +1,7 @@
 # Template file for 'wpa_supplicant'
 pkgname=wpa_supplicant
 version=2.10
-revision=3
+revision=4
 build_wrksrc="$pkgname"
 short_desc="WPA/WPA2/IEEE 802.1X Supplicant"
 maintainer="Enno Boland <gottox@voidlinux.org>"

             reply	other threads:[~2023-09-26 15:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-26 15:04 deepcube [this message]
2023-12-26  1:45 ` github-actions
2024-01-09  1:47 ` [PR PATCH] [Closed]: " github-actions

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-46269@inbox.vuxu.org \
    --to=deepcube@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).