> Gentlemen, Dr. Evil has typed
> # sleep 666; rm -rf /
> on my keyboard and went off to buy milkshakes. How can I stop the
> impending doom?
> C-c C-c, but some files still will get hurt. There is no break key etc.
> The computer is not nearby.

> On Sun, 10 Feb 2008 07:52:17 +0800, jidanni wrote:
>

>> Gentlemen, Dr. Evil has typed
>> # sleep 666; rm -rf /
>> on my keyboard and went off to buy milkshakes. How can I stop the
>> impending doom?
>> C-c C-c, but some files still will get hurt. There is no break key etc.
>> The computer is not nearby.

>
> Log in on another terminal and kill the session
>
> skill -1 pts/0 # or whatever

> At 2008-02-09 07:17PM, "Carbon" wrote:

>> On Sun, 10 Feb 2008 07:52:17 +0800, jidanni wrote:
>>

>>> Gentlemen, Dr. Evil has typed
>>> # sleep 666; rm -rf /
>>> on my keyboard and went off to buy milkshakes. How can I stop the
>>> impending doom?
>>> C-c C-c, but some files still will get hurt. There is no break key etc.
>>> The computer is not nearby.

>>
>> Log in on another terminal and kill the session
>>
>> skill -1 pts/0 # or whatever

>
> And as more than 11 minutes and 6 seconds elapsed between the question
> and the answer, the conclusion must be: "Nevermind"
>
>

> Gentlemen, Dr. Evil has typed
> # sleep 666; rm -rf /
> on my keyboard and went off to buy milkshakes.
> How can I stop the impending doom?
> C-c C-c, but some files still will get hurt.
> There is no break key etc. The computer is not nearby.

> On Sun, 10 Feb 2008 07:52:17 +0800, jida...@jidanni.org wrote:

>> Gentlemen, Dr. Evil has typed
>> # sleep 666; rm -rf /
>> on my keyboard and went off to buy milkshakes.
>> How can I stop the impending doom?
>> C-c C-c, but some files still will get hurt.
>> There is no break key etc. The computer is not nearby.

>
> bash is the only shell that will run "rm" if you interrupt
> "sleep" with C-c.

>On 11 Feb, 10:03, Stephane Chazelas
>wrote:

>> On Sun, 10 Feb 2008 07:52:17 +0800, jida...@jidanni.org wrote:

>>> Gentlemen, Dr. Evil has typed
>>> # sleep 666; rm -rf /
>>> on my keyboard and went off to buy milkshakes.
>>> How can I stop the impending doom?
>>> C-c C-c, but some files still will get hurt.
>>> There is no break key etc. The computer is not nearby.

>>
>> bash is the only shell that will run "rm" if you interrupt
>> "sleep" with C-c.

>And if it's bash you can stop it with ctrl-Z, then kill %%1.

> On Sun, 10 Feb 2008 07:52:17 +0800, jidanni@jidanni.org wrote:

>> Gentlemen, Dr. Evil has typed
>> # sleep 666; rm -rf /
>> on my keyboard and went off to buy milkshakes.
>> How can I stop the impending doom?
>> C-c C-c, but some files still will get hurt.
>> There is no break key etc. The computer is not nearby.

>
> bash is the only shell that will run "rm" if you interrupt
> "sleep" with C-c.
>
> All the other shells including the Bourne shell, ksh88, ksh93,
> pdksh, zsh, csh, tcsh, rc, es and their derivatives will not
> unless Dr. Evil has installed a trap on SIGINT.
>
> With bash, you'll have to kill bash from another shell.

> colin.macl...@tesco.net writes:

>>And if it's bash you can stop it with ctrl-Z, then kill %%1.

>
> No you can't because bash will stop the "sleep" and then run the
> job.
>
> $ bash
> bash-3.2$ sleep 10 ; echo foo
> ^Z
> [1]+  Stopped                 sleep 10
> foo
> bash-3.2$

>On Sun, 10 Feb 2008 07:52:17 +0800, jidanni@jidanni.org wrote:

>> Gentlemen, Dr. Evil has typed
>> # sleep 666; rm -rf /
>> on my keyboard and went off to buy milkshakes.
>> How can I stop the impending doom?
>> C-c C-c, but some files still will get hurt.
>> There is no break key etc. The computer is not nearby.

>
>bash is the only shell that will run "rm" if you interrupt
>"sleep" with C-c.
>
>All the other shells including the Bourne shell, ksh88, ksh93,
>pdksh, zsh, csh, tcsh, rc, es and their derivatives will not
>unless Dr. Evil has installed a trap on SIGINT.
>
>With bash, you'll have to kill bash from another shell.