bug-guix
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#30939: shepherd: detailed output should be placed into well-known lo


From: conjaroy
Subject: bug#30939: shepherd: detailed output should be placed into well-known location and not tty
Date: Sat, 18 Jul 2020 12:27:06 -0400

Hello -

I too have found that debugging is a challenge when a service's stdout/stderr aren't captured automatically. From my point of view though, the issue is not just that certain binaries lack syslog support: since a service implementation's gexp can do much more than just exec a binary, and since mistakes in gexps usually go unnoticed until a runtime, I've found it easy to write scripts that trigger fatal Guile errors before the service binary is even started (syntax errors, missing `use-modules` declarations, etc.)

Will the solution proposed here capture output for this class of errors as well?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]