They are set in different places, but I'll try to avoid both. Would be safe to if(suppress) ... else if (listen) ... else .... But while trying to decide if both JD & JP logs should be suppressed when the console is not attached I discovered that our separate driver/process_attach_console always attach both ... so we might as well always suppress both.
Note that unlike the attach flags the suppress flag could be made to apply to services as well as jobs & APs. On Wed, Oct 2, 2013 at 6:11 PM, Jim Challenger (JIRA) <[email protected]>wrote: > > [ > https://issues.apache.org/jira/browse/UIMA-3312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13784525#comment-13784525] > > Jim Challenger commented on UIMA-3312: > -------------------------------------- > > Burn, to make sure I know exactly what is to be done: > 1. if that env var is set, ducc_ling should redirect stdout/stderr to > /dev/null, correct? > 2. Why would both DUCC_SUPPRESS_CONSOLE and DUCC_CONSOLE_LISTENER both be > set? Since they're mutually contradictory it seems the CLI should insure > they are not both present. > > > > Add new CLI option to enable or disable console logging > > ------------------------------------------------------- > > > > Key: UIMA-3312 > > URL: https://issues.apache.org/jira/browse/UIMA-3312 > > Project: UIMA > > Issue Type: Improvement > > Components: DUCC > > Reporter: Burn Lewis > > Assignee: Jim Challenger > > Priority: Minor > > > > Currently for DUCC jobs and APs the console is always written to a file, > even when also streamed back to the client. Add a new option flag to > suppress the logging in case it is excessive, and also to let viaducc > emulate ssh. > > > > -- > This message was sent by Atlassian JIRA > (v6.1#6144) >
