I have activated VNC on our Linux-Server with the following /etc/xinetd.d/vnc Config-File
service vnc1
{
socket_type = stream
protocol = tcp
wait = no
user = nobody
server = /usr/bin/Xvnc
server_args = -noreset -inetd -once -query localhost -geometry 1600x970 -depth 16 -securitytypes none
type = UNLISTED
port = 5901
}
When I am now starting two VNC-Sessions (“vncviewer :1”) and login with different user-id (e.g. “root” and “oracle”) from a Windows 7 Client machine both VNC-Sessions working right. But, when I am trying to connect two times with the same user-id (e.g. “root”) the second VNC-Session crashes and the VNC-Viewer closes without any comment. Under SuSE 11 it works right, starting two VNC-session with the same user-id is no problem.
It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.
These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:
Visit http://www.suse.com/support and search the knowledgebase and/or check all
the other support options available.
If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot…
The first thing any of our forum volunteers will need to know in order to help you is the software version you are using. Please run this command and post the results.
cat /etc/*release
Any error messages would also help. Please look in /var/log/messages.
The first thing any of our forum volunteers will need to know in order
to help you is the software version you are using. Please run this
command and post the results.
Code:
cat /etc/*release
--------------------[/color]
From the web forum I can see the version tag for the thread is SLES12
SP1 (remember those tags don’t show up via NNTP).
[color=blue]
Any error messages would also help. Please look in /var/log/messages.[/color]
Given that SLES12 SP2 is currently the latest release available (SLES12
SP3 is in beta) I would try duplicating it with that then report back here.
HTH.
Simon
SUSE Knowledge Partner
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
I don’t have any ideas how I can help [COLOR=#333333][FONT=Arial]maennel1[/FONT][/COLOR]. Are you able to offer any suggestions?[/QUOTE]
Nothing that is backed by experience with Xvnc.
“same user” and “window manager” triggers an uneasy feeling with me, knowing that many resources are opened and potentially not all may have been secured against parallel access. Some are tied to the DISPLAY used (i.e. via an individualized file name), but a counter-example would be Firefox databases, where the second FF invocation would leave the user with a “read-only” version of much of the browser interface and I remember having had no bookmarks with earlier FF versions under these circumstances.
But again, I’ve not used this combo Xvnc and xinetd (and the thread-opener didn’t mention the window manager, my guess would be Gnome), and I typically advise against using parallel log-ins anyhow. So nothing really helpful from my side, else I’d already have given an answer earlier on
Hm, there’s one question/advice I may offer: Do the logins provide output via ~/.xsession-errors-? If so, running a "tail -F ~/.xession-errors\" may provide some insight to what is happening after the second login that causes the Xvnc session to terminate. If no such output is created, use Xvnc’s “-Log” parameter to send debug output to syslog.
