Tim,
Sorry, I did not know about the striped attachments, see below.
> It is not a script, but it should be in the vnc-server package.
>
> [tim@cyberelk tim]$ rpm -qf /etc/sysconfig/vncservers
vnc-server-3.3.3r2-14
I was building using the source RPM, the i386 rpm on rpmfind.net was
incomplete. I never wen back and looked on Rawhide after you gave me the
link.
> Does the same thing happen if you just start 'vncserver' by hand
> rather than using the init script?
Scratch that last part... During my attempts to get VNC working correctly I
changed from runlevel 3 to runlevel 5 thinking that the problem had
something to do with the xserver being up or not... Anyway, the side effect
has something to do with the way xdm starts x vs. the startx script...
Thanks.
Paul.
================= VNCSERVERS ======================
#!/bin/sh
# The following line must point to the installed
# location of your vncserver script:
VNC_SERVER='/usr/bin/vncserver'
# The following line specifies the first display
# number to be used by VNCservers. Do *NOT* set
# this value to 0 if an X server is already running
# (or you intend to run one) on the console...
VNC_DISP=2
# The following line is a space-separated list of
# users for whom VNC servers will be started.
# The first-named user gets the VNC_DISP value listed
# above, the number is then incremented by 1 for each
# subsequent user.
# NOTE: These users *must* have already run vncserver
# interactively to set up their ~/.vnc directory and
# must have also created their ~/.vnc/passwd file!!
VNC_USERS="root root"
export VNC_USERS VNC_DISP VNC_SERVER
====================================================
================= VNCSERVER (INIT) ================
#!/bin/sh
# Source function library.
. /etc/rc.d/init.d/functions
# Source networking configuration.
. /etc/sysconfig/network
# Check that networking is up.
[ ${NETWORKING} = "no" ] && exit 0
# Source the VNC server & config file:
. /etc/sysconfig/vncservers
# Check that we have a list of VNC users...
[ -z "$VNC_USERS" ] && exit 0
if [ -z "$VNC_DISP" ]; then
VNC_DISP=0
fi
start() {
if [ -x "$VNC_SERVER" ]; then
echo "Starting VNC servers: "
VNC_DIR=`dirname $VNC_SERVER`
PATH=$VNC_DIR:$PATH && export PATH
else
echo "Cannot start VNC servers: $VNC_SERVER not executable" >&2
exit 1
fi
rm -f /tmp/.VNC_bootlog
disp=$VNC_DISP
for user in $VNC_USERS
do
echo -e "\t$user \t(display $HOSTNAME:$disp)...\c"
vncstart="$VNC_SERVER :$disp"
vnc_cmd="su $user -c \"$vncstart\" >/dev/null 2>>/tmp/.Vnc_bootlog"
if eval $vnc_cmd; then
success $"vncserver startup"
echo
else
failure $"vncserver start"
echo
fi
disp=$(( $disp + 1 ))
done
touch /var/lock/subsys/vnc
}
stop() {
[ ! -x "$VNC_SERVER" ] && exit 0
echo "Shutting down VNC servers: "
disp=$VNC_DISP
for user in $VNC_USERS
do
echo -e "\t$user \t(display $HOSTNAME:$disp)...\c"
vnckill="$VNC_SERVER -kill :$disp"
vnc_cmd="su -l $user -c \"$vnckill\" >/dev/null
2>>/tmp/.Vnc_bootlog"
if eval $vnc_cmd; then
success $"vncserver shutdown"
echo
else
failure $"vncserver shutdown"
echo
fi
disp=$(( $disp + 1 ))
done
rm -f /var/lock/subsys/vnc
echo ""
}
# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart|reload)
stop
start
;;
condrestart)
if [ -f /var/lock/subsys/vncserver ]; then
stop
start
fi
;;
status)
status Xvnc
;;
*)
echo $"Usage: $0 {start|stop|restart|condrestart|status}"
exit 1
esac ====================================================
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Tim Waugh
Sent: Friday, March 23, 2001 7:08 AM
To: [EMAIL PROTECTED]
Subject: Re: VNC startup problem.
On Fri, Mar 23, 2001 at 06:50:09AM -0500, Paul Rubin wrote:
> I think there is some confusion here, I am on Intel not Alpha.
Sorry, I am confusing you with someone else. Next time I'll check my
sent-mail folder.. :-)
> On the startup script I guess I mistyped, there was a vncserver.init
script,
> it used a /etc/sysconfig/vncservers, but there was no vncservers script at
> all.
It is not a script, but it should be in the vnc-server package.
[tim@cyberelk tim]$ rpm -qf /etc/sysconfig/vncservers
vnc-server-3.3.3r2-14
[tim@cyberelk tim]$ cat /etc/sysconfig/vncservers
# The VNCSERVERS variable is a list of display:user pairs.
#
# Uncomment the line below to start a VNC server on display :1
# as my 'myusername' (adjust this to your own). You will also
# need to set a VNC password; run 'man vncpasswd' to see how
# to do that.
#
# DO NOT RUN THIS SERVICE if your local area network is
# untrusted! For a secure way of using VNC, see
# <URL:http://www.uk.research.att.com/vnc/sshvnc.html>.
# VNCSERVERS="1:myusername"
> One final side effect. After installation of this package, my color
> highlighted ls is gone, directories are no longer blue and executables are
> no longer yellow. Do you have any Idea what might be causing this?
Does the same thing happen if you just start 'vncserver' by hand
rather than using the init script?
> [demime 0.97b removed an attachment of type application/octet-stream which
had a name of vncserver]
>
> [demime 0.97b removed an attachment of type application/octet-stream which
had a name of vncservers]
Unfortunately this list manager strips attachments.. :-(
Tim.
*/
[demime 0.97b removed an attachment of type application/pgp-signature]
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------
