Re: xemacs under version 2.3.3
Re: xemacs under version 2.3.3
- Subject: Re: xemacs under version 2.3.3
- From: Samuel Isaacson <email@hidden>
- Date: Mon, 18 May 2009 09:47:45 -0600
'hostname -s' responds immediately with just the hostname of my
computer, no delay and no other info.
I'm not using LDAP, NIS, or anything like that (as far as I know). I
shouldn't have any servers or such running. Everything is unchecked in
the sharing system preference pane too.
Thanks,
-Sam
Jeremy Huddleston wrote:
Just to be sure, 'hostname -s' responds immediately, right?
What does 'hostname -s' report?
Are you using LDAP, NIS, or anything like that?
On May 17, 2009, at 22:12, Samuel Isaacson wrote:
Hi Jeremy,
I get 127.0.0.1 immediately upon running the program with localhost or
127.0.0.1 as input. Using $(hostname) as input it takes slightly
longer (but still less than a second) and returns my ip address. Using
$(hostname -s) takes about 20 seconds and then gives me the following
message:
getaddrinfo returned 8: nodename nor servname provided, or not known
the line after this message then contains my computer's hostname.
I guess this is probably a 10.5.7 bug/interaction then instead of an
xserver issue. If you have any more suggestions on what to look at
please do let me know (though I understand this is moving outside the
domain of this list).
Thanks,
-Sam
Jeremy Huddleston wrote:
I looked into this a bit deeper and it doesn't look like it's calling
make_device over and over. It only calls it once... and you get
stuck waiting for a response to getaddrinfo().
I made a test program using xemac's unix_canonicalize_host_name for
you to test on your system (attached).
Compile this application by:
gcc -o getaddrinfo.test getaddrinfo.test.c
then run it:
./getaddrinfo.test localhost
You should see 127.0.0.1 respond immediately if things are working
right... but for some reason it looks like your system is hanging on
that. Please try running it and tell me what error message gets
printed. If it works with localhost, try 127.0.0.1, your hostname, etc:
./getaddrinfo.test localhost
./getaddrinfo.test 127.0.0.1
./getaddrinfo.test $(hostname)
./getaddrinfo.test $(hostname -s)
...
On May 17, 2009, at 19:33, Jeremy Huddleston wrote:
Well it looks to me like it's trying Fmake_device() over and over
for a certain number of attempts until it gives up and moves on.
From the stack, it looks like xemacs is not liking the restult it is
getting from getaddrinfo() ...
hmm... it's certainly not something specific to xquartz. You can
even try reverting to your old version by uninstalling the current
version and installing 2.3.2.1 from the website. I suspect that you
will still have the same problem.
I'll look into it some more to see what I can dig up.
--Jeremy
On May 17, 2009, at 16:31, Samuel Isaacson wrote:
I do indeed. I'm able to run xterm, gv, and several other graphical
programs.
This time I waited a while after typing xemacs (before I was
probably only waiting 30 seconds or so since it always started
immediately in the past), and it finally did start. This seems to
work consistently, so the problem is not that it won't start, but
that it is taking much much longer to start than previously. (This
is for starting xemacs without loading any specific file.)
The output from the sample command is attached. The sample was
taken before the window appeared.
Thanks,
-Sam
Jeremy Huddleston wrote:
Just to confirm, if you run 'xterm', you get an xterm, right?
Can you sample the xemacs application as it's running and send me
the result? Just run 'sample <pid>' from your prompt, and it'll
save a text file in /tmp with the results.
On May 17, 2009, at 16:13, Samuel Isaacson wrote:
Hi Jeremy and William,
Thank you for your suggestions
I tried Jeremy's suggestion on upgrading all outdated ports, but
it made no difference. I also uninstalled and reinstalled the
xemacs package, but this also didn't help (in addition to trying
the specific upgrade command William suggested).
I then tried completely deleting my macports installation
(removed the entire directory tree). I reinstalled macports from
scratch, and reinstalled the xemacs package. I still have the
same problem with xemacs just hanging when started (and the
terminal version working fine).
When I run the dependency checks in /opt/local/lib and in
/opt/local/bin
I now get no results (before I reinstalled macports there were a
number of libraries).
Any other suggestions?
Thanks,
-Sam
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
X11-users mailing list (email@hidden)
This email sent to email@hidden