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: Mike Miller
Subject: [Octave-bug-tracker] [bug #51830] uname nodename sometimes gives "localhost" instead of pc name
Date: Fri, 25 Aug 2017 12:22:40 -0400 (EDT)
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0

Update of bug #51830 (project octave):

              Item Group:              Regression => Incorrect Result       

    _______________________________________________________

Follow-up Comment #7:

Like I said before, the msg only matters if err is non-zero.

So this indicates that the uname function in gnulib is not returning an error.
When I look in the code for uname on Windows, it calls the gethostname
function to fill in the nodename field, which is part of the Windows API.

If the Windows gethostname function returns with an error, it fills nodename
with the string "localhost". So that's as much as I can tell at this point.

Can you also try gethostname with multiple running instances of Octave, along
with uname, to see if it has the same behavior?

Can you not get Octave to report the correct host name at all now?

Avinoam - was your test also with multiple instances of Octave running at the
same time? I don't think this is a regression since Marshall sees both good
and bad results with version 4.2

    _______________________________________________________

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]