# Logging

**URL:** <https://forums.swift.org/t/logging/16027>\
**Category:** Pitches\
**Created:** [September 10, 2018, 3:14pm UTC](https://forums.swift.org/t/logging/16027 "2018-09-10T15:14:46Z")\
**Posts on this page:** 1\
**Showing post:** 59

<div class="post-metadata">

**Author:** ![Joe\_Groff](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/joe_groff/32/1929_2.png) [@Joe\_Groff](https://forums.swift.org/u/Joe_Groff)\
**Post date:** [September 11, 2018, 4:28pm UTC](https://forums.swift.org/t/logging/16027/59 "2018-09-11T16:28:35Z")

</div>

The topic of emergency cleanup also came up [in this thread](https://forums.swift.org/t/crash-recovery-for-server-side-applications/15854) about the commonly-requested ability to soft-land when subprocesses crash so they don't immediately take down an entire supervising process. That would also require a way for us to install some kind of handling logic without interfering with other signal handlers the process may have set up independently of Swift (and as @johannesweiss noted, it'd require us to standardize what trap Swift code emits to take down a process in a semi-recoverable way). It would be nice if we could guarantee that at least some level of log messages get flushed even when the process crashes, since log messages are often intended to diagnose crash conditions.

---

_[View the full topic](https://forums.swift.org/t/logging/16027)._