Solved

VNC session terminates after I exit telnet session

Posted on 2004-08-04
5
763 Views
Last Modified: 2013-12-23
I telnet to my solaris 2.8 server and login.  I then type "vncserver" and create a vncsession.  Then, I use my vnc viewer client on my laptop to connect to the vnc session without any problems at all.  All is well up till now.  Then, I type exit in my telnet session to close it.  When I do this, my vnc session goes to a grey screen without any terminal windows.

Why is this happening?
0
Comment
Question by:conoverc73
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
  • 2
5 Comments
 
LVL 62

Expert Comment

by:gheist
ID: 11724850
try "nohup vncserver" so vncserver stays running when you log off

or ( vncserver </dev/null 2>&1 >/dev/null ) &
0
 

Author Comment

by:conoverc73
ID: 11728657
I tried both of your suggestions and still get the same result.  Here is a copy of my /.vnc/startup file:

#!/bin/sh

[ -r $HOME/.Xresources ] && xrdb $HOME/.Xresources
xsetroot -solid grey
vncconfig -iconic &
xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
twm &

I have 3 other sun boxes running solaris 2.8 and vnc 4.0 that do not behave like this at all.  You can exit out of the telnet session and your vnc session will stay active like it shoud.
0
 
LVL 62

Expert Comment

by:gheist
ID: 11733227
Try -nowin instead of -iconic, as -iconic uses DISPLAY you set to show icon, and this may get close when you log off...
0
 
LVL 10

Accepted Solution

by:
Nukfror earned 125 total points
ID: 11803852
What's your default shell ?  Sounds like its bourne shell.

Try this:

- Login
- execute "exec /bin/ksh"
- vncserver
- Logout

Your session should stay up.  Bourne shell doesn't understand job control which mean there is only a single process group.  So *ALL* the processes you start in Bourne shell are in the same group.  Signals are propegated throughout process groups so when your parent process died, the vncserver child process being in the same group got whacked also.

These shells all have job control and shouldn't have this problem: ksh, bash, csh, jsh
0
 

Author Comment

by:conoverc73
ID: 11810521
Thank you so much Nukfror.....................that did it.

I was losing faith in this battle.

You nailed this.

Problem solved.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
For many of us, the  holiday season kindles the natural urge to give back to our friends, family members and communities. While it's easy for friends to notice the impact of such deeds, understanding the contributions of businesses and enterprises i…
Internet Business Fax to Email Made Easy - With  eFax Corporate (http://www.enterprise.efax.com), you'll receive a dedicated online fax number, which is used the same way as a typical analog fax number. You'll receive secure faxes in your email, f…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

726 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question