<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/">
	<channel>
				<title>Comments on: CLI: Catching Ctrl+C, kill commands and fatal errors</title>
		<link>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html</link>
		<description>CLI: Catching Ctrl+C, kill commands and fatal errors Comment Feed</description>
				<language>de</language>
		<pubDate>Sun, 05 Feb 2012 09:31:51 +0000</pubDate>
		<generator>mcw[blog] 'Ruby' Alpha 3</generator>
		<item>
			<title>Comment #1 by: Robert de Wilde</title>
			<link>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment10732</link>
			<guid>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment10732</guid>
			<author>Robert de Wilde</author>			
			<pubDate>Sun, 07 Feb 2010 08:53:50 +0000</pubDate>
			<content:encoded><![CDATA[ This was great help, thanks! Only thing is that my exit() didn't seem to be right, lol. Can't kill the proces :) ]]></content:encoded>
		</item>
		<item>
			<title>Comment #2 by: Dominik Jungowski</title>
			<link>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment10741</link>
			<guid>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment10741</guid>
			<author>Dominik Jungowski</author>			
			<pubDate>Sun, 07 Feb 2010 19:05:49 +0000</pubDate>
			<content:encoded><![CDATA[ What does the script look like? ]]></content:encoded>
		</item>
		<item>
			<title>Comment #3 by: </title>
			<link>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment27128</link>
			<guid>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment27128</guid>
			<author></author>			
			<pubDate>Fri, 14 Jan 2011 22:30:03 +0000</pubDate>
			<content:encoded><![CDATA[ Works great, thanks! ]]></content:encoded>
		</item>
		<item>
			<title>Comment #4 by: Geoffrey McRae</title>
			<link>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment30967</link>
			<guid>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment30967</guid>
			<author>Geoffrey McRae</author>			
			<pubDate>Sun, 27 Feb 2011 09:51:28 +0000</pubDate>
			<content:encoded><![CDATA[ Umm, why the class&#8230; you can just do this..<br />
<br />
function catchSigInt() {<br />
}<br />
<br />
function catchSigTerm() {<br />
}<br />
<br />
pcntl_signal(SIGINT , 'catchSigInt' );<br />
pcntl_signal(SIGTERM, 'catchSigTerm');<br />
<br />
You should also be aware that "register_shutdown_function" doesn't just occur on a fatal shutdown, it occurs EVERY time your script exits. ]]></content:encoded>
		</item>
		<item>
			<title>Comment #5 by: IT support UK</title>
			<link>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment53182</link>
			<guid>http://www.phpdevblog.net/2009/05/cli-catching-ctrlc-kill-commands-and-fatal-errors.html#comment53182</guid>
			<author>IT support UK</author>			
			<pubDate>Sun, 23 Oct 2011 10:21:30 +0000</pubDate>
			<content:encoded><![CDATA[ C has a numerical value of three. It was chosen to cause an interrupt as it is otherwise unlikely to be part of the program's interactive interface. ]]></content:encoded>
		</item>
		</channel>
</rss>
