Downloads:

842

Downloads of v 1.1.4:

625

Last Update:

22 Jul 2018

Package Maintainer(s):

Software Author(s):

  • alirdn

Tags:

windows kill signal send x86 x64

windows-kill (Commandline)

1.1.4 | Updated: 22 Jul 2018

Downloads:

842

Downloads of v 1.1.4:

625

Maintainer(s):

Software Author(s):

  • alirdn

windows-kill (Commandline) 1.1.4

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install windows-kill (Commandline), run the following command from the command line or from PowerShell:

>

To upgrade windows-kill (Commandline), run the following command from the command line or from PowerShell:

>

To uninstall windows-kill (Commandline), run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade windows-kill -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade windows-kill -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure windows-kill installed
  win_chocolatey:
    name: windows-kill
    state: present
    version: 1.1.4
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'windows-kill' do
  action    :install
  version  '1.1.4'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: windows-kill,
    Version: 1.1.4,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller windows-kill
{
   Name     = 'windows-kill'
   Ensure   = 'Present'
   Version  = '1.1.4'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'windows-kill':
  provider => 'chocolatey',
  ensure   => '1.1.4',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install windows-kill version="1.1.4" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

This package was approved as a trusted package on 03 Nov 2019.

Description

Send signal to process by PID in Windows, like POSIX kill
Windows has no process signaling mechanism like what POSIX provide using the kill command. But windows-kill could send signal to process by PID

  ## Features
  * Support both 32bit (Win32) and 64bit (x64) Windows
  * Support both SIGNBREAK (Ctrl + Break) and SIGINT (Ctrl + C) Signals
  
  ## Usage Examples
  Using the **windows-kill** is easy and straightforward. It's just like POSIX kill. If signal sending was successful or any error occurred during the sending, appropriate message will be printed in cmd.
  
  ### Sending signal to PID
  ```
  windows-kill -SIGNALTYPE PID
  ```

  ### Sending SIGBREAK (Ctrl + Break) to sample 1234 PID
  ```
  windows-kill -SIGBREAK 1234
  windows-kill -1 1234
  ```

  ### Sending SIGINT (Ctrl + C) to sample 1234 PID
  ```
  windows-kill -SIGINT 1234
  windows-kill -2 1234
  ```

  ### List supported signal types
  ```
  windows-kill -l
  ```

  ### Usage help
  ```
  windows-kill -h
  ```

tools\archives\windows-kill_Win32_1.1.4_lib_release.zip
md5: FF0A21F78D9328BF7299BEC3600FBFED | sha1: AFEF7AC1693652E46EEF1DF06376136AF9B09060 | sha256: A327897CA15114CE1DDAA1FFCCC555B069D9C361E3874E4F0627422E842DD5E6 | sha512: C7DF34232E96A2E57351F445D2A4EC378E7188C1CE51150AE44366AEB39454C9F90823B18765E802B7E5CB0F15D6CF98C0C84D041BFAB03AB8B9AA5424972CAE
tools\archives\windows-kill_x64_1.1.4_lib_release.zip
md5: 3B5286EF7EB94192474B0EE85E8C0B42 | sha1: FFC83BE2BDA512AFB6608AE879FE2D0D47742CB6 | sha256: 86410DCF5364FB0A26EB3FD3D9C004B8F02ED51E23FCAE1107439456CA581AD3 | sha512: 5AF8A5B9B54F35234C89BE7650DAD4269F814C01E8387A26EA5769908768723C567BDCC160681111D1DD9EE90299C46FF0EE09CE513320D2BFFAA270CD82E399
tools\chocolateyinstall.ps1
$ErrorActionPreference = 'Stop'

$toolsPath = Split-Path -parent $MyInvocation.MyCommand.Definition

$packageArgs = @{
  packageName = $env:ChocolateyPackageName
  file        = "$toolsPath\archives\windows-kill_Win32_1.1.4_lib_release.zip"
  file64      = "$toolsPath\archives\windows-kill_x64_1.1.4_lib_release.zip"
  destination = $toolsPath
}

Get-ChocolateyUnzip @packageArgs

Remove-Item $toolsPath\archives\*.zip -ea 0
Remove-Item $toolsPath\archives -ea 0
tools\LICENSE.txt
MIT License

Copyright (c) 2017-2018 Alireza Dabiri Nejad <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.
tools\VERIFICATION.txt
VERIFICATION

Verification is intended to assist the Chocolatey moderators and community
in verifying that this package's contents are trustworthy.

Package can be verified like this:

1. Go to

   x32: https://github.com/alirdn/windows-kill/releases/download/1.1.4/windows-kill_Win32_1.1.4_lib_release.zip
   x64: https://github.com/alirdn/windows-kill/releases/download/1.1.4/windows-kill_x64_1.1.4_lib_release.zip

   to download the program zip archive.

2. You can use one of the following methods to obtain the SHA256 checksum:
   - Use powershell function 'Get-FileHash'
   - Use Chocolatey utility 'checksum.exe'

   checksum32: A327897CA15114CE1DDAA1FFCCC555B069D9C361E3874E4F0627422E842DD5E6
   checksum64: 86410DCF5364FB0A26EB3FD3D9C004B8F02ED51E23FCAE1107439456CA581AD3

Using AU:

   Get-RemoteChecksum https://github.com/alirdn/windows-kill/releases/download/1.1.4/windows-kill_Win32_1.1.4_lib_release.zip
   Get-RemoteChecksum https://github.com/alirdn/windows-kill/releases/download/1.1.4/windows-kill_x64_1.1.4_lib_release.zip

File 'license.txt' is obtained from:
   https://github.com/alirdn/windows-kill/blob/master/LICENSE

In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).

Chocolatey Pro provides runtime protection from possible malware.

Version Downloads Last Updated Status
windows-kill (Commandline) 1.1.3 71 Sunday, July 22, 2018 Approved
windows-kill (Commandline) 1.1.1 62 Sunday, July 22, 2018 Approved
windows-kill (Commandline) 1.1.0 84 Monday, July 9, 2018 Approved

This package has no dependencies.

Discussion for the windows-kill (Commandline) Package

Ground Rules:

  • This discussion is only about windows-kill (Commandline) and the windows-kill (Commandline) package. If you have feedback for Chocolatey, please contact the Google Group.
  • This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
  • The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
  • Tell us what you love about the package or windows-kill (Commandline), or tell us what needs improvement.
  • Share your experiences with the package, or extra configuration or gotchas that you've found.
  • If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
comments powered by Disqus