[Gmsh] Socket port parsing bug ?

Christophe Geuzaine cgeuzaine at ulg.ac.be
Tue Aug 20 20:02:12 CEST 2013


Hi Pierre - it's normal (but the documentation is indeed not very explicit...). The socket name is actually a "base name", to which the unique client ID is appended. The doc has been fixed.

Thanks,

Christophe

On 14 Aug 2013, at 00:54, Pierre Boulenguez <pierre.boulenguez at gmail.com> wrote:

> Typo : "localhost:10000" gives gmsh listening on ip 100002
> On 14/08/2013 00:49, Pierre Boulenguez wrote:
>> Precision: I use ubuntu 13.04
>> 
>> On 14/08/2013 00:44, Pierre Boulenguez wrote:
>>> Hello,
>>> 
>>> A '2' is suffixed to the socket ip number of gmsh: for instance, configured with "localhost:10000" (through the GUI or the  Gmsh Option File) gmsh will in fact listen to the port 10002.
>>> 
>>> I could not find information regarding this behavior in the documentation so I suspect it is a bug. I observed the phenomenon with gmsh 2.6.2 and 2.8.2.
>>> 
>>> With kind regards,
>>> Pierre
>> 
> 
> 
> _______________________________________________
> gmsh mailing list
> gmsh at geuz.org
> http://www.geuz.org/mailman/listinfo/gmsh

-- 
Prof. Christophe Geuzaine
University of Liege, Electrical Engineering and Computer Science 
http://www.montefiore.ulg.ac.be/~geuzaine