From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [External] Re: [PATCH v2 1/1] package/hostapd: add debug information options
Date: Mon, 17 Jun 2019 21:02:23 +0200 [thread overview]
Message-ID: <20190617210223.77a97ee2@windsurf> (raw)
In-Reply-To: <CAM=7fbd717PmwGE5Dh4Wi4AGhY14Pb7tabG7qrxCsgdCgDQ-LQ@mail.gmail.com>
Hello,
On Mon, 17 Jun 2019 12:56:08 -0500
Jared Bents <jared.bents@collins.com> wrote:
> > Could you explain what CONFIG_DEBUG_FILE is doing compared to
> > CONFIG_DEBUG_SYSLOG, and why one is conditional and not the other ? Do
> > we really want CONFIG_DEBUG_FILE unconditionally ?
>
> I based it off of wpa_supplicant's implementation for each. In
> wpa_supplicant, CONFIG_DEBUG_FILE is turned on unconditionally while
> CONFIG_DEBUG_SYSLOG is optional. CONFIG_DEBUG_FILE enables a runtime
> option (-f) to specify a file to direct the hostapd output to instead
> of stdout. CONFIG_DEBUG_SYSLOG enables a runtime option (-s) to have
> the output go to syslog instead of stdout. These are purely optional
> at runtime as if neither of the -f or -s command line arguments are
> used, the output will go to stdout as before.
What is the size impact of each option, compared to the overall
installation size of hostapd ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-06-17 19:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 15:35 [Buildroot] [PATCH v2 1/1] package/hostapd: add debug information options jared.bents at rockwellcollins.com
2019-06-17 17:41 ` Thomas Petazzoni
2019-06-17 17:56 ` [Buildroot] [External] " Jared Bents
2019-06-17 19:02 ` Thomas Petazzoni [this message]
2019-06-17 20:27 ` Jared Bents
2019-06-18 22:05 ` Arnout Vandecappelle
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=20190617210223.77a97ee2@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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