You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Arpit Gupta (JIRA)" <ji...@apache.org> on 2013/11/12 03:16:17 UTC

[jira] [Updated] (FALCON-187) Update Falcon start script to also redirect stdout to the log file

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

Arpit Gupta updated FALCON-187:
-------------------------------

    Attachment: FALCON-187-v1.patch

Attached is a simple patch that i tested on my mac. Without this patch if falcon is started within an ssh call it will not return the control back to the user. Makes it a bit difficult to automate :)

> Update Falcon start script to also redirect stdout to the log file 
> -------------------------------------------------------------------
>
>                 Key: FALCON-187
>                 URL: https://issues.apache.org/jira/browse/FALCON-187
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.3
>            Reporter: Arpit Gupta
>            Assignee: Arpit Gupta
>             Fix For: 0.4
>
>         Attachments: FALCON-187-v1.patch
>
>
> I noticed a weird behavior where if the bin/falcon-start script was called within the ssh call it would start the service but not return the control back to the user.
> If the same ssh call was issued with -t option it worked. What i determined is that the java command being issued is only redirecting stderr to the log file and stdout is not being captured. If we capture stdout as well we do not run into this issue.



--
This message was sent by Atlassian JIRA
(v6.1#6144)