Solaris startup problem

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Solaris startup problem

Bloom, Greg
I installed vim on our Solaris 8 box yesterday from a sunfreeware.com
package.  The install went just fine and I was able to fire up vim, no
problems.

This morning, I tried starting vim and it just sat there for about 5
minutes, then came up.  I did a 'truss -d vim 2>vim.out' to see what it
was hanging on and found this:

 0.1456 open("/dev/udp", O_RDONLY)                      = 4
 0.1459 ioctl(4, 0xC00C6982, 0xFFBEF424)                = 0
 0.1461 close(4)                                        = 0
 0.1466 open64("/etc/.name_service_door", O_RDONLY)     = 4
 0.1468 fcntl(4, F_SETFD, 0x00000001)                   = 0
 0.1469 door_info(4, 0xFEDC07E0)                        = 0
 0.1472 door_call(4, 0xFFBED390)                        = 0
connect(3, 0xFFBEF5D8, 16, 1)   (sleeping...)
224.7667        connect(3, 0xFFBEF5D8, 16, 1)                   Err#145
ETIMEDOU
T
224.7674        close(3)                                        = 0
224.7677        ioctl(0, TCGETS, 0x00157E44)                    = 0
224.7680        ioctl(0, TCSETS, 0xFFBEF9E8)                    = 0
224.7682        write(1, "1B 71B [ ? 4 7 h", 8)                 = 8
224.7685        ioctl(1, TCGETA, 0xFFBEF99C)                    = 0
224.7689        getuid()                                        = 1033
[1033]

It appears vim is hanging for 224 seconds on that connect right after
the door_call.  Can anyone tell me what the heck is going on here?
Better, can anyone tell me what I can do to get vim started in less than
224 seconds?

Thanks,
Greg Bloom

Reply | Threaded
Open this post in threaded view
|

Re: Solaris startup problem

A.J.Mechelynck
Bloom, Greg wrote:

> I installed vim on our Solaris 8 box yesterday from a sunfreeware.com
> package.  The install went just fine and I was able to fire up vim, no
> problems.
>
> This morning, I tried starting vim and it just sat there for about 5
> minutes, then came up.  I did a 'truss -d vim 2>vim.out' to see what it
> was hanging on and found this:
>
>  0.1456 open("/dev/udp", O_RDONLY)                      = 4
>  0.1459 ioctl(4, 0xC00C6982, 0xFFBEF424)                = 0
>  0.1461 close(4)                                        = 0
>  0.1466 open64("/etc/.name_service_door", O_RDONLY)     = 4
>  0.1468 fcntl(4, F_SETFD, 0x00000001)                   = 0
>  0.1469 door_info(4, 0xFEDC07E0)                        = 0
>  0.1472 door_call(4, 0xFFBED390)                        = 0
> connect(3, 0xFFBEF5D8, 16, 1)   (sleeping...)
> 224.7667        connect(3, 0xFFBEF5D8, 16, 1)                   Err#145
> ETIMEDOU
> T
> 224.7674        close(3)                                        = 0
> 224.7677        ioctl(0, TCGETS, 0x00157E44)                    = 0
> 224.7680        ioctl(0, TCSETS, 0xFFBEF9E8)                    = 0
> 224.7682        write(1, "1B 71B [ ? 4 7 h", 8)                 = 8
> 224.7685        ioctl(1, TCGETA, 0xFFBEF99C)                    = 0
> 224.7689        getuid()                                        = 1033
> [1033]
>
> It appears vim is hanging for 224 seconds on that connect right after
> the door_call.  Can anyone tell me what the heck is going on here?
> Better, can anyone tell me what I can do to get vim started in less than
> 224 seconds?
>
> Thanks,
> Greg Bloom
>
>
>
>
>

What could it be trying to connect to?

If you are running an X-enabled version on a machine where X11 isn't
running, or in a terminal which has no access to X, adding the -X switch
to the Vim command-line may help.

Note: Even console versions of Vim are often compiled with X11 support,
so that they can access the clipboard if running in an xterm.

See ":help -X"


Best regards,
Tony.

Reply | Threaded
Open this post in threaded view
|

RE: Solaris startup problem

Bloom, Greg
In reply to this post by Bloom, Greg
You nailed it!  If I use the -X option from my plain-vanilla telnet
session, it fires right up.  

Turns out I had been running a separate X session yesterday when vim was
launching okay and I do have my DISPLAY environment variable set to my
PC by default, which is where I would be running my X server when I need
it.  

Thanks Tony.



-----Original Message-----
From: A. J. Mechelynck [mailto:[hidden email]]
Sent: Thursday, June 30, 2005 10:12 AM
To: Bloom, Greg
Cc: [hidden email]
Subject: Re: Solaris startup problem

Bloom, Greg wrote:
> I installed vim on our Solaris 8 box yesterday from a sunfreeware.com
> package.  The install went just fine and I was able to fire up vim, no
> problems.
>
> This morning, I tried starting vim and it just sat there for about 5
> minutes, then came up.  I did a 'truss -d vim 2>vim.out' to see what
it

> was hanging on and found this:
>
>  0.1456 open("/dev/udp", O_RDONLY)                      = 4
>  0.1459 ioctl(4, 0xC00C6982, 0xFFBEF424)                = 0
>  0.1461 close(4)                                        = 0
>  0.1466 open64("/etc/.name_service_door", O_RDONLY)     = 4
>  0.1468 fcntl(4, F_SETFD, 0x00000001)                   = 0
>  0.1469 door_info(4, 0xFEDC07E0)                        = 0
>  0.1472 door_call(4, 0xFFBED390)                        = 0
> connect(3, 0xFFBEF5D8, 16, 1)   (sleeping...)
> 224.7667        connect(3, 0xFFBEF5D8, 16, 1)
Err#145

> ETIMEDOU
> T
> 224.7674        close(3)                                        = 0
> 224.7677        ioctl(0, TCGETS, 0x00157E44)                    = 0
> 224.7680        ioctl(0, TCSETS, 0xFFBEF9E8)                    = 0
> 224.7682        write(1, "1B 71B [ ? 4 7 h", 8)                 = 8
> 224.7685        ioctl(1, TCGETA, 0xFFBEF99C)                    = 0
> 224.7689        getuid()                                        = 1033
> [1033]
>
> It appears vim is hanging for 224 seconds on that connect right after
> the door_call.  Can anyone tell me what the heck is going on here?
> Better, can anyone tell me what I can do to get vim started in less
than
> 224 seconds?
>
> Thanks,
> Greg Bloom
>
>
>
>
>

What could it be trying to connect to?

If you are running an X-enabled version on a machine where X11 isn't
running, or in a terminal which has no access to X, adding the -X switch
to the Vim command-line may help.

Note: Even console versions of Vim are often compiled with X11 support,
so that they can access the clipboard if running in an xterm.

See ":help -X"


Best regards,
Tony.