Thanks for the enlightenment...(pun intended)
turned out that the first problem was caused by my commenting out the
lines between
initlog $INITLOG_ARGS -c \
"su ${display##*:} -c \"cd ~${display##*:} && [ -f
.vnc/passwd ] && vncserver :${display%%:*} $ARGS\""
# "su ${display##*:} -c \"cd ~${display##*:} && [ -f
.vnc/passwd ] && vncserver :${display%%:*}\""
what I mean is that when the commented line was above the non-commented
line, it wouldn't work - strange but true...
as for the second issue, I am somewhat dense on window managers and have
gotten stuck on KDE but with RH 8, it probably doesn't much matter to me
whether I use GNOME or KDE - I am not knowledgable of the differences
between the two (spoken like a guy with a $60 video card and a $10 audio
card).
Some of this is important to me since I intend to try LTSP and this is
good for background...
Now if Redhat would update the Gnome 2.0 on RH8...
Craig
On Mon, 2003-01-06 at 12:11, Jeremy Impson wrote:
>
> [Apologies if this has already been discussed to death. I'm just getting
> caught up on email.]
>
> On Sat, 7 Dec 2002, Craig White wrote:
>
> [...]
>
> > In this vein...I am having a problem with VNC that perhaps someone can
> > shed some light on.
> >
> > After reading the an article in the Linux Journal magazine - which I've
> > saved for quite some time, I wanted to set up VNC so I can have a
> > continuous session going, whether I am on the localhost or one of the
> > other machines around my house (yes, it's decadent but I figured, the
> > learning experience would be good).
> >
> > The article is online <jeremy.impson@lmco.com.>
> >
> > I am using RH 8
> >
> > The problem that I ran into is this...
> > I changed /etc/init.d/vncserver as follows...
> >
> > from
> > "su ${display##*:} -c \"cd ~${display##*:} && [ -f
> > .vnc/passwd ] && vncserver :${display%%:*}\""
> >
> > to
> > "su ${display##*:} -c \"cd ~${display##*:} && [ -f
> > .vnc/passwd ] && vncserver ${ARGS} :${display%%:*}\""
> >
> > and changed /etc/sysconfig/vncservers by adding a line...
> >
> > ARGS="-geometry 1024x768 -alwaysshared "
> >
> > all per the article...
> >
> > When I try to start vncserver (service vncserver start), I get an error
> > that it can't find the file which I am certain is -geometry 1024 x 768
> > -alwaysshared instead of using those as arguments to the vncserver
> > command within /etc/init.d/vncserver
> >
> > I have tried various combinations...i.e. removing -geometry 1024x768 and
> > by removing -alwaysshared and even deleted the ${ARGS} and replaced it
> > with -alwaysshared and the same error occurs...
> >
> > Is anyone doing this? Does anyone see the cause of the problem?
>
> I don't have access to a RH8 system at the moment, but one possibility is
> that vncserver (or Xvnc) has changed how it handles command line args.
> With the VNC service down, what happens when you run
>
> vncserver -geometry 1024x768 -alwaysshared
>
> on the command line? My first thought is maybe it now wants you to use
> double dashes instead of single dashes.
>
> > If I log in locally and then log out...then any application that I used
> > locally will give me an error if I try to use it via VNC -
> >
> > (KDE) - KLauncher could not be reached via DCOP
> >
> > and vice versa - if I use an application from remote VNC Connection and
> > close the connection, I get the same error when I log on locally and try
> > to launch the application.
>
>
> On my RH 7.3 (KDE 3.0), there are two directories in /tmp, one called
> kde-$USER, the other ksocket-$USER. The latter seems to be full of
> sockets for various KDE apps.
>
> I bet even after killing a local desktop some part of KDE (like maybe
> kdeinit) is still running (and using some of those sockets), and when you
> connect a remote desktop (or vice versa), and start a new app, it tries to
> connect to whatever KDE piece still that was started for the OLD desktop.
> That mismatch may be confusing KDE.
>
> When you log in then log out (either remotely or locally), log back in
> with a command line ONLY (i.e. no X or Xvnc running at all) and look at
> your process listing. I bet something is still listening on one or mroe
> of those sockets.
>
> FYI, I've been able to run two instances of GNOME with no problem, but
> I've never tried with KDE. I often use fvwm or something else equally
> lightweight on my VNC desktop. (This is because my GNOME system has the
> RAM to run two concurrent instances of GNOME, but my KDE system does not.
> Also, the GNOME system's VNC desktop is used regularly, while the KDE
> system's VNC desktop is used only occasionally when I need a GUI
> application remotely.)
>
> A better solution might be had from some KDE-specific list or mail
> archive.
>
> --Jeremy
--
Psyche-list mailing list
Psyche-list@redhat.com
https://listman.redhat.com/mailman/listinfo/psyche-list
