Quote from: some1 on August 08, 2014, 07:06:42 AM

Quote from: patmast3r on August 08, 2014, 06:35:56 AM

Quote from: smaragda on August 08, 2014, 06:33:52 AM

Quote from: patmast3r on August 08, 2014, 06:24:29 AM

I think that's normal. You see webstart installs NIS on your computer while the standalone package is merely lying around in some location unknown to it.
I think the best way to run the client is to choose Webstart OR the standalone package. Mixing things is a recipe for problems like yours

The standalone package is imho best for people that want to run a node 24/7 or only want to run NIS. Webstart is meant for people that just want to use the client and have an easy way of starting it.

Nobody is mixing anything though.

I understand that things are setup this way to accommodate those that go for the One Click Install but it causes this issue when running everything through the Standalone Package. Not saying that the issue is critical (or even important for the matter)... we just need to point to the solution when people report having this particular problem.

Oh you mean you start NCC from the standalone package and it tries to download and install NIS ?
I'll file an issue in the repo.

Thanks for reporting it.

Same happens on my Linux box too.

First I run nix.runNis.sh, than when I execute nix.runNcc.sh it generates an additional log (ncc/ncc/ncc-nis.log) complaining that Java Web Start cannot start:

Code:

Java Web Start splash screen process exiting .....
Splash: X11 connection failed: No such file or directory

It would be nice for NCC to execute NIS only if local port 7890 is free.

I think the standalone should not deal with webstart at all. Not sure how much more pain that will introduce to the building process though.