[ucx-group] use stderr rather than stdout for logging?
shamisp at ornl.gov
Mon Oct 5 09:55:53 EDT 2015
Howard - I'm curious if this worked for you. If so, maybe we shell post a FAQ entry for running on cray with slurm.
Pavel (Pasha) Shamis
Computer Science Research Group
Computer Science and Math Division
Oak Ridge National Laboratory
On Oct 2, 2015, at 2:45 PM, Yossi Itigin <yosefe at mellanox.com<mailto:yosefe at mellanox.com>> wrote:
Have you used UCS_LOG_FILE=stderr for that?
Is there a way to detect that this and use the appropriate stream for every system?
BTW you can always send SIGHUP to the process to make it flush the log.
From: Pritchard Jr., Howard [mailto:howardp at lanl.gov<http://lanl.gov>]
Sent: Friday, October 02, 2015 12:07 AM
To: ucx-group at elist.ornl.gov<mailto:ucx-group at elist.ornl.gov>
Subject: [ucx-group] use stderr rather than stdout for logging?
I’m working with Pasha on some gni/cray stuff in ucx. I’m noticing
that on my favorite XC system (which uses slurm rather than alps/aprun),
that I don’t get UCS_LOG_LEVEL=debug output if the app hangs early
on. If I switch to using stderr things work like expected – I get output.
I tried using the srun –u option but srun complained about this.
So, if there aren’t any objections, could we switch to using stderr for
Los Alamos National Laboratory
ucx-group mailing list
ucx-group at elist.ornl.gov<mailto:ucx-group at elist.ornl.gov>
To unsubscribe, send a blank email to ucx-group-unsubscribe at elist.ornl.gov<mailto:ucx-group-unsubscribe at elist.ornl.gov>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ucx-group