From: Erik Blake <erik@icefield.yk.ca>
To: Pat Thoyts <patthoyts@users.sourceforge.net>
Cc: Thomas Rast <trast@student.ethz.ch>, git@vger.kernel.org
Subject: Re: Warning from AV software about kill.exe
Date: Wed, 04 Jan 2012 10:15:29 +0100 [thread overview]
Message-ID: <4F0418B1.5050403@icefield.yk.ca> (raw)
In-Reply-To: <878vm4lb9q.fsf@fox.patthoyts.tk>
Another way to implement this (on Windows) would be for the git programs
to tag themselves with a mutex. Then the "kill" program can determine
which git programs are running and send them user-defined windows
messages to shut themselves down. Alternatively, you could send the
programs the standard windows WM_CLOSE message, but the OS or an AV
program might still be troubled by that behaviour.
This is how we implement this type of behaviour in our windows programs.
It does not raise the ire of the OS or AV since you do not have one
process trying to shut down another. It also bypasses all issues with
process privileges etc.
Erik
On 2011-12-22 19:19, Pat Thoyts wrote:
> Thomas Rast<trast@student.ethz.ch> writes:
>
>> Erik Blake<erik@icefield.yk.ca> writes:
>>
>>> I'm running git under Win7 64. As I selected "Repository|Visualize all
>>> branch history" in the git gui, my AV software (Trustport) trapped the
>>> bin\kill.exe program for "trying to modify system global settings
>>> (time, timezone, registry quota, etc.)"
>>>
>>> Does anyone know the details of this process and what it's function
>>> is? First time I've seen it, though I'm a relatively new user.
>> 'kill' is a standard unix utility that sends signals to processes, in
>> particular signals that cause the processes to exit or be killed
>> forcibly by the kernel, hence the name. (I don't know how the windows
>> equivalent works under the hood, but presumably it's something similar.)
>>
>> git-gui and gitk use kill to terminate background worker processes that
>> are no longer needed because you closed the window their output would
>> have been displayed in, etc.
> You might try replacing the command in the tcl scripts with 'exec
> taskkill /f /pid $pid' and see if that avoids the error. taskkill is
> present on XP and above as part of the OS distribution so shouldn't
> suffer any AV complaints.
>
next prev parent reply other threads:[~2012-01-04 9:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-22 7:47 Warning from AV software about kill.exe Erik Blake
2011-12-22 8:45 ` Thomas Rast
2011-12-22 18:19 ` Pat Thoyts
2012-01-04 9:15 ` Erik Blake [this message]
2012-01-05 16:33 ` Erik Faye-Lund
2012-01-06 13:51 ` Erik Blake
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=4F0418B1.5050403@icefield.yk.ca \
--to=erik@icefield.yk.ca \
--cc=git@vger.kernel.org \
--cc=patthoyts@users.sourceforge.net \
--cc=trast@student.ethz.ch \
/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).