You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Gary D. Gregory (Jira)" <ji...@apache.org> on 2022/05/12 03:12:00 UTC

[jira] [Updated] (DAEMON-443) prunsrv writes gigabytes of null bytes to stderr

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

Gary D. Gregory updated DAEMON-443:
-----------------------------------
        Fix Version/s: 1.3.1
    Affects Version/s: 1.1.0

> prunsrv writes gigabytes of null bytes to stderr
> ------------------------------------------------
>
>                 Key: DAEMON-443
>                 URL: https://issues.apache.org/jira/browse/DAEMON-443
>             Project: Commons Daemon
>          Issue Type: Bug
>    Affects Versions: 1.1.0
>            Reporter: Ryan Ernst
>            Priority: Major
>             Fix For: 1.3.1
>
>
> When trying to start a non-existent service, procrun will write an enormous amount of null bytes to stderr. Since these are not printable, the problem is not normally seen in a terminal. However, if a wrapper script is used that captures stdout/stderr, the output file is over 8 GB.
> Reproducing is quite simple:
> {{prunsrv.exe //ES/my-dummy-service 2> test.err}}
> The file test.err then has 8589934985 bytes. The printable characters are only a few lines of warn/error log messages.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)