Write log output to file
Repository details (botten-nappet)
- Project page
- botten-nappet
- Project log category
- botten-nappet (195 entries)
- Repository
- @joelpurra/botten-nappet
- Owner
- @joelpurra
- Issues
- Issues on Github
- Contributors
- Contributors on Github
- Project status
- 💤 This project is inactive.
- 📂 This project is open.
- 🤷 This project is not particularly popular.
- Repository activity period
- 🗓
- Commits
- 209 commits
- Stars
- 5 stars
Commit details (259aebfb)
- Author
- Joel Purra
- Authored at
- Committer
- Joel Purra
- Committed at
Commit message
Write log output to file
- In nodejs
stdout
can get closed prematurely (before the synchronousexit
event).- When
stdout
closes, logging breaks.- Using a separate file works better, and stop/disconnect logging messages can get logged.
- Separately, pino would forcefully and synchronously terminate the nodejs application when shutting itself down (
SIGTERM
,beforeExit
,uncaughtException
, etcetera).- This would break the
ShutdownManager
and other attempts cleanly exit the application, including cleanly closing network connections etcetera.- The solution is to override and ignore the
onTerminated
configurable function for pino.
Raw text
Write log output to file - In nodejs `stdout` can get closed prematurely (before the synchronous `exit` event). - When `stdout` closes, logging breaks. - Using a separate file works better, and stop/disconnect logging messages can get logged. - Separately, pino would forcefully and synchronously terminate the nodejs application when shutting itself down (`SIGTERM`, `beforeExit`, `uncaughtException`, etcetera). - This would break the `ShutdownManager` and other attempts cleanly exit the application, including cleanly closing network connections etcetera. - The solution is to override and ignore the `onTerminated` configurable function for pino.