Hi Manuel,
My pull request to fix the issue of silencing the coordinator
has now been pushed in. It's in the master repo on github now,
and it should be appearing in a new 2.4.2 release in about a week.
Thanks for reporting this. It helped us to re-thing the --quiet
flag, and do it right. (Now, when dmtcp_launch causes a new
coordinator to be created, it passes --quiet to the coordinator.)
Best,
- Gene
On Wed, Sep 16, 2015 at 04:31:55PM +0200, Manuel RodrÃguez Pascual wrote:
> hi all,
>
> I am trying to silence all output related to DMTCP. I have however the
> feeling that it is impossible to silence dmtcp_launch completely. this is,
> when executing a code with
>
> ---
> dmtcp_launch ./myCode
> ---
>
> I would like not having
>
> ---
> dmtcp_coordinator starting...
> Host: slurm-master (192.168.1.10)
> Port: 7779
> Checkpoint Interval: disabled (checkpoint manually instead)
> Exit on last client: 1
> Backgrounding...
>
> ---
>
> at the beginning of the execution. My question is, is it possible to do
> it? My closest attempt so far is to redirect the application standard
> output to a file with ">", but it is not really elegant plus I still lose
> stderr.
>
> Any suggestion?
>
> Best regards,
>
>
> Manuel
> ------------------------------------------------------------------------------
> Monitor Your Dynamic Infrastructure at Any Scale With Datadog!
> Get real-time metrics from all of your servers, apps and tools
> in one place.
> SourceForge users - Click here to start your Free Trial of Datadog now!
> http://pubads.g.doubleclick.net/gampad/clk?id=241902991&iu=/4140
> _______________________________________________
> Dmtcp-forum mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
------------------------------------------------------------------------------
_______________________________________________
Dmtcp-forum mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
