More info: Yet another "rc3.d" problem . . .
Fri Jun 27 21:41:01 2003
I've got some preliminary responses, and I greatly appreciate it! Here's
some more information . . .
Some of the responses suggested that an X server process might not be
available for the VNC "Xvnc" process to bind to when my vncserver sessions
are spawned. In fact, if I populate my xstartup script with just an
"xterm" executable, the VNC log complains that . . .
"xterm: fatal IO error 32 (Broken pipe) or KillClient on X server
So, I attempted to address this angle by adding "/usr/bin/X11/X :5 &" to
"xstartup", but then I get . . .
"Fatal server error: Cannot establish any listening sockets - Make sure
an X server isn't already running". Not being able to decipher the
vncserver script/manuals very well, I'm guessing that the Xvnc process
must be serving as the Xserver for display :5 already at this point, so I
don't really need to explicitly spawn another X server . . .
To reiterate, my VNC xstartup scripts work fine once I log into root,
whether it be at the graphics console or telnet . . .
> Joey Knight said:
>> Thanks for the quick reply, William . . .
>> Since I'm rather confident that this is probably a "UNIX is UNIX is UNIX"
>> problem, I didn't want to confuse anyone with the particular UNIX variant.
>> But, I could be wrong, so . . .
> It's when you are sure that you are usually mistaken :-) In this case
> fact that Tru64 puts init.d in /sbin caused more confusion.
>> I'm running Tru64 UNIX v5.1B, where the "init.d" sripts and "rc3.d" links
>> are in "/sbin". The script contents are below. The plan is to start five
>> displays as root upon boot. Immediately following the script contents is
>> a look at the log for the :25 display . . .
>> Thanks again for any help!
>> # Startup/Stop script for VNCservers for root
>> export HOME
> First up, I know nothing about Tru64, so be patient if I'm off base.
> HOME is set to /, so that means VNC is looking for a /.vnc/xstartup
>> 25/06/03 16:05:17 Xvnc version 3.3.2r3
>> 25/06/03 16:05:17 Copyright (C) 1997-8 Olivetti & Oracle Research
>> 25/06/03 16:05:17 See http://www.orl.co.uk/vnc for information about
>> 25/06/03 16:05:17 Desktop name 'X' (tesoro:25)
>> 25/06/03 16:05:17 Protocol version supported 3.3
>> 25/06/03 16:05:17 Listening for VNC connections on TCP port 5925
25/06/03 16:05:17 Listening for HTTP connections on TCP port 5825
25/06/03 16:05:17 URL http://tesoro:5825
>> 25/06/03 16:05:20 Xvnc version 3.3.2r3
>> 25/06/03 16:05:20 Copyright (C) 1997-8 Olivetti & Oracle Research
>> 25/06/03 16:05:20 See http://www.orl.co.uk/vnc for information about
>> 25/06/03 16:05:20 Desktop name 'X' (tesoro:25)
>> 25/06/03 16:05:20 Protocol version supported 3.3
> No errors here... hmm... You might try putting an "echo" statement at
> beginning of your xstartup file, just to verify that it isn't something
about your window manager that is the issue (grasping at straws). If
> echo doesn't appear in the logs, than you are definitely not reading the
> As I said, I don't know anything about Tru64 (just Linux and a bit of
FreeBSD), so I'm afraid I can't suggest anything else to test.
> William Hooper
> VNC-List mailing list
> To remove yourself from the list visit:
Joseph B. Knight
Specialist Solutions Architect
hp Enterprise UNIX