apple/foundationdb

macOS package: fdbmonitor output is being lost

Open

#318 建立於 2018年5月7日

在 GitHub 查看
 (3 留言) (0 反應) (0 負責人)C++ (13,912 star) (1,266 fork)batch import
help wanted

描述

On Linux, we run fdbmonitor with the --daemonize flag, which causes it to log to syslog. On macOS, we do not use the --daemonize flag (and I'm not immediately sure why), which results in output going to stderr. As far as I can tell, it doesn't seem that we are capturing stderr anywhere, so this logging output is being lost.

貢獻者指南

技術棧
cppshell
領域
backenddatabasedevops
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-3 hours
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
C++macOS developmentFoundationDB build system
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
25
研究方向
Investigate why daemonize is not used on macOS. Check the fdbmonitor launch scripts in the repository (likely in packaging or contrib). Look at how stderr is handled (e.g., shell redirection). Consider adding syslog on macOS or capturing stderr and redirecting to a log file. Review previous comments for potential solutions.