* [ISSUE] bind: -g option disables logging @ 2022-09-24 3:45 TitaniumHocker 2022-09-24 3:51 ` TitaniumHocker ` (2 more replies) 0 siblings, 3 replies; 4+ messages in thread From: TitaniumHocker @ 2022-09-24 3:45 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 576 bytes --] New issue by TitaniumHocker on void-packages repository https://github.com/void-linux/void-packages/issues/39440 Description: Hey! Current [runit file](https://github.com/void-linux/void-packages/blob/master/srcpkgs/bind/files/named/run#L5) for `bind` disables all logging with `-g` option: ``` # man named | grep -- -g -g This option runs the server in the foreground and forces all logging to stderr. ``` So it's impossible to config logging with default `bind` configuration. Is there any reason for that or maybe it's just a mistake? ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: bind: -g option disables logging 2022-09-24 3:45 [ISSUE] bind: -g option disables logging TitaniumHocker @ 2022-09-24 3:51 ` TitaniumHocker 2022-09-24 3:51 ` [ISSUE] [CLOSED] " TitaniumHocker 2022-09-24 5:35 ` sgn 2 siblings, 0 replies; 4+ messages in thread From: TitaniumHocker @ 2022-09-24 3:51 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 305 bytes --] New comment by TitaniumHocker on void-packages repository https://github.com/void-linux/void-packages/issues/39440#issuecomment-1256848178 Comment: Sorry, I found that standard bind logging is [broken in void](https://github.com/void-linux/void-packages/commit/6041f96bef58174255e6db66428a3c866e59dab6) ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [ISSUE] [CLOSED] bind: -g option disables logging 2022-09-24 3:45 [ISSUE] bind: -g option disables logging TitaniumHocker 2022-09-24 3:51 ` TitaniumHocker @ 2022-09-24 3:51 ` TitaniumHocker 2022-09-24 5:35 ` sgn 2 siblings, 0 replies; 4+ messages in thread From: TitaniumHocker @ 2022-09-24 3:51 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 579 bytes --] Closed issue by TitaniumHocker on void-packages repository https://github.com/void-linux/void-packages/issues/39440 Description: Hey! Current [runit file](https://github.com/void-linux/void-packages/blob/master/srcpkgs/bind/files/named/run#L5) for `bind` disables all logging with `-g` option: ``` # man named | grep -- -g -g This option runs the server in the foreground and forces all logging to stderr. ``` So it's impossible to config logging with default `bind` configuration. Is there any reason for that or maybe it's just a mistake? ^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: bind: -g option disables logging 2022-09-24 3:45 [ISSUE] bind: -g option disables logging TitaniumHocker 2022-09-24 3:51 ` TitaniumHocker 2022-09-24 3:51 ` [ISSUE] [CLOSED] " TitaniumHocker @ 2022-09-24 5:35 ` sgn 2 siblings, 0 replies; 4+ messages in thread From: sgn @ 2022-09-24 5:35 UTC (permalink / raw) To: ml [-- Attachment #1: Type: text/plain, Size: 183 bytes --] New comment by sgn on void-packages repository https://github.com/void-linux/void-packages/issues/39440#issuecomment-1256868522 Comment: You can enable socklog service for logging. ^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-09-24 5:35 UTC | newest] Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2022-09-24 3:45 [ISSUE] bind: -g option disables logging TitaniumHocker 2022-09-24 3:51 ` TitaniumHocker 2022-09-24 3:51 ` [ISSUE] [CLOSED] " TitaniumHocker 2022-09-24 5:35 ` sgn
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).