On Tue, 2013-01-29 at 17:56 +0100, Per Jessen wrote:
Adam Tauno Williams wrote:
On Tue, 2013-01-29 at 10:20 -0300, Cristian Rodríguez wrote:
El 29/01/13 03:31, Anders Johansson escribió:
So you are saying if a daemon crashes, all we can tell people is "sorry, run it again, your files have been deleted? FHS version 2.3 explains it for you. "The /tmp directory must be made available for programs that require temporary files. Programs must not assume that any files or directories in /tmp are preserved between invocations of the program." +1 Assuming you can collect forensic information from /tmp is mis-guided; plain and simple. If a deamon actually 'crashes' then it needs to be debugged, that means gdb or some tool, at least using strace. When a problem is not immediately reproducable, you can't do much else than wait and see - collect diagnostics, core dumps etc. Debugging a production issue with gdb and strace is for the optimistic.
What? It isn't opportunistic at all. You configure the system to preserve core files; and you can look at them after-the-fact with gdb. UN*X is aware of core files from the bolts and screws on up. There are sysctl and ulimit parameters to control how core files are created [or not created] and managed. If you have a service that is crashing then you MUST grab a core. That is debugging step #2. [Step #1 being looking in the log]. -- Adam Tauno Williams GPG D95ED383 Systems Administrator, Python Developer, LPI / NCLA -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org