Bug 800048
Summary: | 20second vnc connection delay in rhel6 environment | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | gregrwm <rhbugzi> |
Component: | tigervnc | Assignee: | Tim Waugh <twaugh> |
Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | qe-baseos-daemons |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4 | CC: | rhbugzi |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2014-10-23 14:29:32 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
gregrwm
2012-03-05 16:44:22 UTC
run rhel6 kernel run rhel4 in a chroot: mount --bind /tmp /<rhel4>/tmp mount --rbind /dev /<rhel4>/dev mount --rbind /sys /<rhel4>/sys mount --rbind /proc /<rhel4>/proc run Xvnc in rhel4 chroot connect vncviewer (via portforward via rhel6 sshd) copy ~/.Xauthority from rhel4 to rhel6 home directory launch xterm in (rhel4) Xvnc launch xterm from within that xterm launch DISPLAY=localhost:<display> from rhel6 launch xterm from within that xterm the rhel4 xterms display immediately the rhel6 xterms display after 20second delays. why? This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. It has been proposed for the next release. If you would like it considered as an exception in the current release, please ask your support representative. This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate, in the next release of Red Hat Enterprise Linux. Since the original report is alread two years old, I'd like to ask is it still an issue with the latest RHEL updates? According to comment #c2, sshd is only used as port forwarder. How? Is the portfowarding channel already established? Is there any delay when you try to connect to forwarded port using netcat/telnet? the problem was obviated by using ubuntu vnc instead of rhel6. sorry i no longer have rhel6 vnc handy for testing. |