You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2017/05/31 10:01:04 UTC

[jira] [Reopened] (UIMA-5418) DUCC check_ducc -k should not use -9 to kill the database, by default

     [ https://issues.apache.org/jira/browse/UIMA-5418?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou DeGenaro reopened UIMA-5418:
--------------------------------

check_ducc w/o any parms gives spurious message for DB: Killing (-QUIT) ...


> DUCC check_ducc -k should not use -9 to kill the database, by default
> ---------------------------------------------------------------------
>
>                 Key: UIMA-5418
>                 URL: https://issues.apache.org/jira/browse/UIMA-5418
>             Project: UIMA
>          Issue Type: Bug
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.2.1
>
>
> Normally, check_ducc -k sends -9 signal to those process it aims to kill, including the database.  This may leave the database in a bad (unusable?) state.
> 1. Change check_ducc -k to issue signal -9 to all daemons except database which will get -3.
> 2. Change check_ducc to accept the --db-9 option that indicates that the database should get signal -9.  The db-9 option only applies if the -k option is also specified, and should be used only as a last resort.



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