octave-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #51830] uname nodename sometimes gives "localh


From: Avinoam Kalma
Subject: [Octave-bug-tracker] [bug #51830] uname nodename sometimes gives "localhost" instead of pc name
Date: Fri, 25 Aug 2017 18:49:54 -0400 (EDT)
User-agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Follow-up Comment #8, bug #51830 (project octave):

Checking again, I saw that in version 4.2.1 under Win-10,
I always get the correct nodename, and it does not depend on the number of
Octave instances (I have tried 1-5).

In 4.3.0+ (dev) I get always "localhost", and again, it does not depend on the
number of Octave instances. 

In the help of uname I see:
"If successful, ERR is 0 and MSG is an empty string."

On both 4.2.1 & dev, ERR is 0, but MSG is not empty.

There is still a regression problem:

On 4.2.1


>> gethostname
ans = Kalma-PC


On dev:

>> gethostname
ans = unknown



    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51830>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]