Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Write logs to file #2427
Please sign your commits following these rules:
$ git clone -b "log-to-file" firstname.lastname@example.org:BasPH/distribution.git somewhere $ cd somewhere $ git rebase -i HEAD~842353265024 editor opens change each 'pick' to 'edit' save the file and quit $ git commit --amend -s --no-edit $ git rebase --continue # and repeat the amend for each commit $ git push -f
Amending updates the existing PR. You DO NOT need to open a new one.
@@ Coverage Diff @@ ## master #2427 +/- ## ========================================== - Coverage 60.32% 50.72% -9.61% ========================================== Files 126 126 Lines 14436 14442 +6 ========================================== - Hits 8708 7325 -1383 - Misses 4844 6373 +1529 + Partials 884 744 -140
Actually, they go to stderr. ;)
We don't have this option because it forces the system to have rotation and other features. Basically, file-based logging tends to lead to filled disks. If we can avoid adding this, I'd prefer not. Most daemon management (systemd, upstartd, runit, daemontools, etc.) support this model but there may be something still in use that I am unaware of.
Are you not able to run the registry in a context that has a proper stderr logging facility? I'd be open to this if there were some situation that made stderr logging completely untenable. If so, let me know.