From: sean <seanlkml@sympatico.ca>
To: Andrey Borzenkov <arvidjaar@mail.ru>
Cc: git@vger.kernel.org
Subject: Re: git cherry unkillable
Date: Sun, 22 Jan 2006 06:39:04 -0500 [thread overview]
Message-ID: <BAYC1-PASMTP10435A067270A659801A48AE110@CEZ.ICE> (raw)
Message-ID: <20060122063904.2dbefbe4.seanlkml@sympatico.ca> (raw)
In-Reply-To: <200601221323.33377.arvidjaar@mail.ru>
On Sun, 22 Jan 2006 13:23:26 +0300
Andrey Borzenkov <arvidjaar@mail.ru> wrote:
> Hash: SHA1
>
> I mistakenly run git cherry on linus tree which was a bit too much for my poor
> old system. Trying to kill (^C) it I got
>
> {pts/0}% git cherry ali1535 linus
> external diff died, stopping at include/linux/sysctl.h.
> external diff died, stopping at drivers/serial/suncore.c.
> diff: /home/bor/tmp/.diff_Y6CvCw: No such file or directory
> diff: /home/bor/tmp/.diff_tBqCCk: No such file or directory
> external diff died, stopping at include/asm-arm/arch-pxa/pxa-regs.h.
> external diff died, stopping at fs/cifs/file.c.
> external diff died, stopping at MAINTAINERS.
> diff: /home/bor/tmp/.diff_P12uX9: No such file or directory
> diff: /home/bor/tmp/.diff_R4v0g0: No such file or directory
> external diff died, stopping at net/ipv4/route.c.
> ....
>
> and it jut goes on. This takes really some time here so ability to stop it
> would be really nice. It still runs with CPU temp rocketing.
>
Ouch yeah, you'd have to explicitly kill -9 from another command line. The
same problem exists in a few other scripts too, although probably none that
can be as long lived as git-cherry.
The attached patch works for me but i'm concerned about it a bit. With this
patch it looks like the signal handler is executed twice; once as normal and
a second time in response to the added "exit" statement. By adding
";trap - 0;exit" it is only executed once, but i'm not sure how universal that
is, and letting it run twice shouldn't be a big deal anyway.
The other minor concern is that exit should maybe return an error value
instead; but that isn't approprirate when handling signal zero. So it
might be better to have a separate trap for signal zero, but in the end
it doesn't seem worth the bother.
Sean
diff --git a/git-cherry.sh b/git-cherry.sh
index 1a62320..a1e4d70 100755
--- a/git-cherry.sh
+++ b/git-cherry.sh
@@ -49,7 +49,7 @@ ours=`git-rev-list $ours ^$limit` || exi
tmp=.cherry-tmp$$
patch=$tmp-patch
mkdir $patch
-trap "rm -rf $tmp-*" 0 1 2 3 15
+trap "rm -rf $tmp-*;exit" 0 1 2 3 15
_x40='[0-9a-f][0-9a-f][0-9a-f][0-9a-f][0-9a-f]'
_x40="$_x40$_x40$_x40$_x40$_x40$_x40$_x40$_x40"
diff --git a/git-format-patch.sh b/git-format-patch.sh
index 7e67c4e..38adaad 100755
--- a/git-format-patch.sh
+++ b/git-format-patch.sh
@@ -77,7 +77,7 @@ tt)
esac
tmp=.tmp-series$$
-trap 'rm -f $tmp-*' 0 1 2 3 15
+trap 'rm -f $tmp-*;exit' 0 1 2 3 15
series=$tmp-series
commsg=$tmp-commsg
diff --git a/git-ls-remote.sh b/git-ls-remote.sh
index f699268..ba96969 100755
--- a/git-ls-remote.sh
+++ b/git-ls-remote.sh
@@ -38,7 +38,7 @@ peek_repo="$(get_remote_url "$@")"
shift
tmp=.ls-remote-$$
-trap "rm -fr $tmp-*" 0 1 2 3 15
+trap "rm -fr $tmp-*;exit" 0 1 2 3 15
tmpdir=$tmp-d
case "$peek_repo" in
diff --git a/git-reset.sh b/git-reset.sh
index 6c9e58a..1b6781f 100755
--- a/git-reset.sh
+++ b/git-reset.sh
@@ -4,7 +4,7 @@ USAGE='[--mixed | --soft | --hard] [<co
. git-sh-setup
tmp=${GIT_DIR}/reset.$$
-trap 'rm -f $tmp-*' 0 1 2 3 15
+trap 'rm -f $tmp-*;exit' 0 1 2 3 15
reset_type=--mixed
case "$1" in
next prev parent reply other threads:[~2006-01-22 11:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-22 10:23 git cherry unkillable Andrey Borzenkov
[not found] ` <20060122063904.2dbefbe4.seanlkml@sympatico.ca>
2006-01-22 11:39 ` sean [this message]
[not found] ` <20060122095113.0eea7aa0.seanlkml@sympatico.ca>
2006-01-22 14:51 ` sean
2006-01-22 15:21 ` Andrey Borzenkov
[not found] ` <20060122103204.05a16683.seanlkml@sympatico.ca>
2006-01-22 15:32 ` sean
[not found] ` <20060122104850.33d07ad5.seanlkml@sympatico.ca>
2006-01-22 15:48 ` sean
2006-01-22 15:01 ` Andrey Borzenkov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAYC1-PASMTP10435A067270A659801A48AE110@CEZ.ICE \
--to=seanlkml@sympatico.ca \
--cc=arvidjaar@mail.ru \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).