Github messages for voidlinux
 help / color / mirror / Atom feed
From: AluminumTank <AluminumTank@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: unbound: add logging service
Date: Tue, 20 Jul 2021 21:15:53 +0200	[thread overview]
Message-ID: <20210720191553.SL1c1MZGv-D8y2QAOQLfDfMDXx3zAmmUbjTXYGGICtQ@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-31992@inbox.vuxu.org>

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

New comment by AluminumTank on void-packages repository

https://github.com/void-linux/void-packages/pull/31992#issuecomment-883632182

Comment:
Huh, you're right. I think I got confused when I was trying to enable logging within unbound because I copied a config from somewhere which didn't have the `use-syslog: true` directive. I'll close then, thanks for the tip.

As an aside, the issue about `log/supervise` missing may be related to `log/run` being a symlink to `/usr/bin/vlogger` since I checked several other services in void-packages using this symlink (`bluez`, dhcp`, `caddy`) and none of them have `log/supervise` either. Not sure if this is intended behavior or not...

  parent reply	other threads:[~2021-07-20 19:15 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-16  0:38 [PR PATCH] " AluminumTank
2021-07-17  2:59 ` ericonr
2021-07-17 11:51 ` leahneukirchen
2021-07-17 11:52 ` leahneukirchen
2021-07-17 11:53 ` leahneukirchen
2021-07-17 13:54 ` AluminumTank
2021-07-17 13:56 ` AluminumTank
2021-07-17 19:14 ` Duncaen
2021-07-17 19:15 ` Duncaen
2021-07-20 18:59 ` ericonr
2021-07-20 19:15 ` AluminumTank [this message]
2021-07-20 19:15 ` [PR PATCH] [Closed]: " AluminumTank
2021-07-20 19:16 ` AluminumTank
2021-07-20 19:27 ` ericonr

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=20210720191553.SL1c1MZGv-D8y2QAOQLfDfMDXx3zAmmUbjTXYGGICtQ@z \
    --to=aluminumtank@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).