atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Radley (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ATLAS-1733) No SIGKILL in python signal library on Windows
Date Sat, 15 Apr 2017 07:55:41 GMT

    [ https://issues.apache.org/jira/browse/ATLAS-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15969856#comment-15969856
] 

David Radley commented on ATLAS-1733:
-------------------------------------

[~grahamwallis] The Jira is still in open state - I think you want to resolve this Jira as
fixed.

> No SIGKILL in python signal library on Windows
> ----------------------------------------------
>
>                 Key: ATLAS-1733
>                 URL: https://issues.apache.org/jira/browse/ATLAS-1733
>             Project: Atlas
>          Issue Type: Bug
>          Components:  atlas-core
>    Affects Versions: 0.9-incubating
>         Environment: Windows 7
>            Reporter: Graham Wallis
>            Assignee: Graham Wallis
>            Priority: Minor
>         Attachments: ATLAS-1733.patch
>
>   Original Estimate: 0.5h
>  Remaining Estimate: 0.5h
>
> [I am new to Atlas and this is my first JIRA issue so apologies if I have omitted any
necessary information or steps.]
> There is no SIGKILL signal in the python signal library on Windows, so the import in
atlas_stop.py fails.
> There are two ways I can suggest that we fix it:
> 1) introduce platform-specific code into atlas_stop.py
> 2) wrap the python os.kill function
> My preference is for the former as it is a small and localized change. 
> In either case the use of SIGTERM should be sufficient on Windows, as the existing python
os.kill() function will open the process and terminate it, which is supposed to be equivalent
to a SIGKILL (-9) on Linux.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message