On Sun, Oct 18, 2015 at 11:26 PM, Kevin Buckley < [email protected]> wrote:
> On 19 October 2015 at 15:56, Kapil Arya <[email protected]> wrote: > > Hi Kevin, > > > > Looks like you have run into yet another bug/feature. The "--quiet" flag > was > > enforced aggressively, but looks like we went too far. Before we fix it, > it > > will be good to know if this information is useful to the end user. We > can > > then try to come up with a better combination of information to print on > > screen (and may be add a "--verbose" flag). > > Well, the info is actually visible from a > > [term2]$ dmtcp_command --status > Coordinator: > Host: localhost > Port: 7779 (default port) > Status... > NUM_PEERS=1 > RUNNING=yes > CKPT_INTERVAL=90 > [term2] > > but I could see that being told about the status on launch, might serve to > inform you that you had previously set EnvVars which were not readily > apparent (A bit like leaving an old dmtcp_coordinator hanging around !) > > My vote would thus be for quiet by default, plus a "--verbose" flag of > some sort. > > Maybe giving the' dmtcp_launch' a '--status' flag would be an alternative? > That's a good point. We are trying to come up with a simpler policy regarding existing coordinator process and the desired behavior. > Talking of EnvVars, I couldn't see a way to tell the build about the local > Java, other than explicitly setting EnvVars to the configure, indeed trying > to use --with-java or --enable-java breaks the search for Java altogether: > $ ./configure --prefix=/path/to/dmtcp-2.4.2 > ... > checking for java... no > checking for javac... no > ... > $ ./configure --prefix=/path/to/dmtcp-2.4.2 --with-java=yes > configure: WARNING: unrecognized options: --with-java > ... > $ ./configure --prefix=/path/to/dmtcp-2.4.2 --with-java=/some/path/to/java > configure: WARNING: unrecognized options: --with-java > ... > $ > $ HAS_JAVA="yes" HAS_JAVAC="yes" ./configure --prefix=/path/to/dmtcp-2.4.2 > ... > checking for java... yes > checking for javac... yes > ... > $ > > however, the EnvVars controlling the enabling of Java aren't mentioned in > any of the MarkDown doc files - so you need to speak/read configure and/or > Makefile to work out how to enable it. > The Java configure checks are only there to enable java tests in the test suite. They aren't need for DMTCP to work and that's why we didn't want to make any additional efforts in searching for a valid Java environment :). Kapil
------------------------------------------------------------------------------
_______________________________________________ Dmtcp-forum mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
