SEO

#1 (**permalink**) 02-15-2008, 05:20 PM

Hi,

I'm trying to get tightvnc going on my OSR5.0.6 box but I'm unable to get
anything but a gray screen with a black cross and no password prompt. I've
followed the directions in
http://aplawrence.com/Unixart/vnc_sco_openserver.html and have double
checked everything.

When a client connects a Xvnc process is started, but the xstartup script,
with execute permissions, in /.vnc is not being excuted at all. And of
course the log file in that directory gets nothing added to it when the
client connection is made. xstartup is as follows:-

PATH=$PATH:/usr/bin/X11 ; export PATH
[ -f $HOME/.Xresources ] && xrdb $HOME/.Xresources
scosession &

I've also installed perl, bash, glib and gzcat.

I've done a google search but can find nothing specific to SCO and this
problem that seems to help. So any assistance would be appreciated.

Thanks in advance.
--
greghines@bigfoot.com.NOSPAM
Remove NOSPAM when replying

#2 (**permalink**) 02-15-2008, 05:20 PM

Does "netstat -a" show anything running on those ports ?

vnc640 5950/tcp
vnc800 5951/tcp
vnc1024 5952/tcp

#3 (**permalink**) 02-15-2008, 05:20 PM

--

"B....@gmail.com" <brent.bolin@gmail.com> wrote in message
news:1125418876.986302.25540@g44g2000cwa.googlegro ups.com...
> Does "netstat -a" show anything running on those ports ?
>
> vnc640 5950/tcp
> vnc800 5951/tcp
> vnc1024 5952/tcp
>

netstat -a gives 3 lines as follows:-

tcp 0 0 *.vnc1024 *.* LISTEN
tcp 0 0 *.vnc800 *.* LISTEN
tcp 0 0 *.vnc640 *.* LISTEN

Does not look right as there is no mention of 5950 - 5952.

Ideas?
greghines@bigfoot.com.NOSPAM
Remove NOSPAM when replying

#4 (**permalink**) 02-15-2008, 05:20 PM

Hi,

Have traced the problem to the S99vncserver link in /etc/rc2.d. This file
links to /etc/init.d/vncserver

The line:-

su ${display##*:} -c "/usr/local/bin/vncserver :${display%%:*}"

is producing the error:-

bad substitution

Any help would be appreciated.

Greg
--
greghines@bigfoot.com.NOSPAM
Remove NOSPAM when replying

#5 (**permalink**) 02-15-2008, 05:20 PM

Greg Hines wrote:
> Hi,
>
> Have traced the problem to the S99vncserver link in /etc/rc2.d. This file
> links to /etc/init.d/vncserver
>
> The line:-
>
> su ${display##*:} -c "/usr/local/bin/vncserver :${display%%:*}"
>
> is producing the error:-
>
> bad substitution

The first line of the script should be:
#!/bin/ksh

If not,then that's the problem, or at least it's one problem.

#6 (**permalink**) 02-15-2008, 05:20 PM

Greg Hines wrote:
> Hi,
>
> Have traced the problem to the S99vncserver link in /etc/rc2.d. This file
> links to /etc/init.d/vncserver
>
> The line:-
>
> su ${display##*:} -c "/usr/local/bin/vncserver :${display%%:*}"
>
> is producing the error:-
>
> bad substitution

The first line of the script should be:
#!/bin/ksh

If not,then that's the problem, or at least it's one problem.

#7 (**permalink**) 02-15-2008, 05:20 PM

>
> The first line of the script should be:
> #!/bin/ksh
>
> If not,then that's the problem, or at least it's one problem.
>

Changing it still produces the same error. Was:-

#!/bin/bash

Greg
--
greghines@bigfoot.com.NOSPAM

#8 (**permalink**) 02-15-2008, 05:20 PM

Greg Hines wrote:
> >
> > The first line of the script should be:
> > #!/bin/ksh
> >
> > If not,then that's the problem, or at least it's one problem.
> >
>
> Changing it still produces the same error. Was:-
>
> #!/bin/bash

I don't do bash, but it apparently does parameter substitution
similarly to ksh. Looking at /etc/rc2, I see it executes the scripts
in /etc/rc2.d by doing "/bin/sh <script>", so that first line
specifying the shell is ignored. The parameter substitution your
script is using is not supported in sh, so you'll have to change it.
E.g., you could do something like the following instead (not tested):

su `expr $display : '.*:$.*$'` \
-c "/usr/local/bin/vncserver :`expr $display : '$[^:]*$`"

#9 (**permalink**) 02-15-2008, 05:20 PM

Roger Cornelius wrote:
> Greg Hines wrote:
> > >
> > > The first line of the script should be:
> > > #!/bin/ksh
> > >
> > > If not,then that's the problem, or at least it's one problem.
> > >
> >
> > Changing it still produces the same error. Was:-
> >
> > #!/bin/bash
>
> I don't do bash, but it apparently does parameter substitution
> similarly to ksh. Looking at /etc/rc2, I see it executes the scripts
> in /etc/rc2.d by doing "/bin/sh <script>", so that first line
> specifying the shell is ignored. The parameter substitution your
> script is using is not supported in sh, so you'll have to change it.
> E.g., you could do something like the following instead (not tested):
>
> su `expr $display : '.*:$.*$'` \
> -c "/usr/local/bin/vncserver :`expr $display : '$[^:]*$`"

I left out a closing "'". That should be:

su `expr $display : '.*:$.*$'` \
-c "/usr/local/bin/vncserver :`expr $display : '$[^:]*$'`"

#10 (**permalink**) 02-15-2008, 05:20 PM

Roger Cornelius wrote:
> Greg Hines wrote:
>
>>>The first line of the script should be:
>>>#!/bin/ksh
>>>
>>>If not,then that's the problem, or at least it's one problem.
>>>
>>
>>Changing it still produces the same error. Was:-
>>
>>#!/bin/bash
>
>
> I don't do bash, but it apparently does parameter substitution
> similarly to ksh. Looking at /etc/rc2, I see it executes the scripts
> in /etc/rc2.d by doing "/bin/sh <script>", so that first line
> specifying the shell is ignored. The parameter substitution your
> script is using is not supported in sh, so you'll have to change it.
> E.g., you could do something like the following instead (not tested):
>
> su `expr $display : '.*:$.*$'` \
> -c "/usr/local/bin/vncserver :`expr $display : '$[^:]*$`"
>

I think it would be easier to install bash and change the rc2 script -
especially if there's more of this stuff. Besides, bash is nice to have
on the system.

--
Tony Lawrence
Unix/Linux/Mac OS X resources: http://aplawrence.com
Geek Yard Sale: http://geekyardsale.com

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

VNC giving a gray screen on OSR5.0.6