﻿id	summary	reporter	owner	description	type	status	priority	milestone	component	version	resolution	keywords	cc
153	os._exit() after logging a FATAL message	Zooko		I would like it if foolscap called {{{os._exit()}}} after it finishes durably/reliably logging a {{{FATAL}}} message. Note that I don't want {{{os.abort()}}} because that allows more Python code to run before ending the operating system process. (Alternately you might consider {{{os.kill(os.getpid(), 9)}}}, but I don't think that works right on Windows.)	enhancement	new	major	undecided	unknown	0.4.1			
