You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Ales Dolecek (JIRA)" <ji...@apache.org> on 2013/03/06 15:20:13 UTC

[jira] [Commented] (DAEMON-279) MSVCR should be ditributed with procrun

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

Ales Dolecek commented on DAEMON-279:
-------------------------------------

Hmmm. 64-bit procrun fails to run on our server. From the error mesasge and what I have found on the web I got impression that msvcr.dll is missing. We can't move the library into system32 directory since it is production and the admins won't allow it.
                
> MSVCR should be ditributed with procrun
> ---------------------------------------
>
>                 Key: DAEMON-279
>                 URL: https://issues.apache.org/jira/browse/DAEMON-279
>             Project: Commons Daemon
>          Issue Type: Improvement
>          Components: Procrun
>    Affects Versions: 1.0.13
>            Reporter: Ales Dolecek
>            Priority: Minor
>              Labels: build
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> Windows OS does not by default include MSVCR library. And it is not system library and Miscrosoft does not provide it as "standalone" instalation. According to Microsoft knowledgebas it is responsibility of the application authors to distribute the DLL with their product: http://support.microsoft.com/kb/326922/en
> The binary distribution of procrun shall therefore include this file. While many systems already include this somewhere on PATH it is not required. And users often download the DLL from various sites in Internet which leads to security risks.
> If the omission of the DLL is deliberate then you shall document it along with some trusted source where the users might get the library.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira