Users-l Digest, Vol 104, Issue 4
Roman Nádhera
roman at nadhera.name
Tue Feb 7 16:22:33 CET 2012
> ------------------------------
>
> Message: 2
> Date: Mon, 06 Feb 2012 13:31:34 +0100
> From: Dan Lukes <dan na obluda.cz>
> To: FreeBSD mailing list <users-l na freebsd.cz>
> Subject: Re: Dotaz na forum
> Message-ID: <4F2FC826.2000805 na obluda.cz>
> Content-Type: text/plain; charset=ISO-8859-2; format=flowed
>
> On 02/06/12 12:50, Roman N?dhera:
>> da se tady diskutovat i o PC-BSD?
>> Nebo je a pouze o FreeBSD?
>>
>> Ono totiz ceske forum na PC-BSD neni a slovenske uz nefunguje.
>
> No, ja myslim, ze zkusit to muzeme. Ty systemy jsou si hodne podobne a
> zatim podobnych dotazu ocekavam spise minimum. Kdyby se to pozdeji
> rozjelo do vetsich rozmeru, nebo by se ukazalo, ze vetsina dotazu je na
> takove speciality, ktere obema systemum spolecne nejsou a tudiz tady
> prekazeji, zalozime pro PC-BSD zvlastni list ...
>
>
> Dan
Tak dobra, zkusim to.
Mam problem z rozchozenim vnc serveru na pc-bsd.
Na jinych pocitacich, s Windows a s Linuxem pouzivam
UltraVNC (Windows7), TightVNC (Xubuntu) a x11vnc
(OpenSuSE Linux).
Na stroji s PC-BSD jsem nainstaloval x11vnx a xrdp
z portu. (v prepackagech to neni)
A nyni problem. Kdyz spustim vncserver, tak na
na klientskem pocitaci normalne prihlasim k serveru,
ale zobrazi se mi pouze prazdne okno s GUI terminalem.
Nic víc.
Kdyz pouziji na serveru x11vnc, tak:
nekdy se uspesne pripojim, ale pouze jednou po bootu a i tak jenom nekdy.
Vetsinou skoncim tak, ze x11vnc se spustí, ale pri pokusu o pripojeni
klienta spadne s naslednou lamentaci:
[rna na mumu] /home/rna# x11vnc -create
###############################################################
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@ @#
#@ ** WARNING ** WARNING ** WARNING ** WARNING ** @#
#@ @#
#@ YOU ARE RUNNING X11VNC WITHOUT A PASSWORD!! @#
#@ @#
#@ This means anyone with network access to this computer @#
#@ may be able to view and control your desktop. @#
#@ @#
#@ >>> If you did not mean to do this Press CTRL-C now!! <<< @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
#@ @#
#@ You can create an x11vnc password file by running: @#
#@ @#
#@ x11vnc -storepasswd password /path/to/passfile @#
#@ or x11vnc -storepasswd /path/to/passfile @#
#@ or x11vnc -storepasswd @#
#@ @#
#@ (the last one will use ~/.vnc/passwd) @#
#@ @#
#@ and then starting x11vnc via: @#
#@ @#
#@ x11vnc -rfbauth /path/to/passfile @#
#@ @#
#@ an existing ~/.vnc/passwd file from another VNC @#
#@ application will work fine too. @#
#@ @#
#@ You can also use the -passwdfile or -passwd options. @#
#@ (note -passwd is unsafe if local users are not trusted) @#
#@ @#
#@ Make sure any -rfbauth and -passwdfile password files @#
#@ cannot be read by untrusted users. @#
#@ @#
#@ Use x11vnc -usepw to automatically use your @#
#@ ~/.vnc/passwd or ~/.vnc/passwdfile password files. @#
#@ (and prompt you to create ~/.vnc/passwd if neither @#
#@ file exists.) Under -usepw, x11vnc will exit if it @#
#@ cannot find a password to use. @#
#@ @#
#@ @#
#@ Even with a password, the subsequent VNC traffic is @#
#@ sent in the clear. Consider tunnelling via ssh(1): @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/#tunnelling @#
#@ @#
#@ Or using the x11vnc SSL options: -ssl and -stunnel @#
#@ @#
#@ Please Read the documention for more info about @#
#@ passwords, security, and encryption. @#
#@ @#
#@ http://www.karlrunge.com/x11vnc/faq.html#faq-passwd @#
#@ @#
#@ To disable this warning use the -nopw option, or put @#
#@ 'nopw' on a line in your ~/.x11vncrc file. @#
#@ @#
#@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@#
###############################################################
07/02/2012 16:16:00 x11vnc version: 0.9.13 lastmod: 2011-08-10 pid: 14325
07/02/2012 16:16:01
07/02/2012 16:16:01 wait_for_client: WAIT:cmd=FINDCREATEDISPLAY-Xvfb
07/02/2012 16:16:01
07/02/2012 16:16:01 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560
07/02/2012 16:16:01
07/02/2012 16:16:01 Autoprobing TCP port
07/02/2012 16:16:01 Autoprobing selected port 5900
07/02/2012 16:16:01 Listening also on IPv6 port 5900 (socket 4)
07/02/2012 16:16:01
The VNC desktop is: mumu:0
PORT=5900
**************** TADY TO CEKA, A AZ SPUSTIM NA KLIENTOVI (WOKNA) VNC,
TAK TO POKRACUJE:
07/02/2012 16:17:24 Got connection from client 192.168.1.29
07/02/2012 16:17:24 other clients:
07/02/2012 16:17:24 incr accepted_client=1 for 192.168.1.29:64902 sock=5
07/02/2012 16:17:24 wait_for_client: got client
07/02/2012 16:17:24 Client Protocol Version 3.8
07/02/2012 16:17:24 Protocol version sent 3.8, using 3.8
07/02/2012 16:17:24 client progressed=1 in 0/1 0.000874 s
07/02/2012 16:17:24 client useCopyRect: 192.168.1.29 0
07/02/2012 16:17:24 client_set_net: 192.168.1.29 0.0030
07/02/2012 16:17:24 wait_for_client: running: env X11VNC_SKIP_DISPLAY=''
/bin/sh /tmp/x11vnc-find_display.6MA32O
The program "Xvfb" could not be found in PATH and standard locations.
You probably need to install a package that provides the "Xvfb" program.
Without it FINDCREATEDISPLAY mode may not be able to create an X display.
07/02/2012 16:17:25 wait_for_client: find display cmd failed.
07/02/2012 16:17:25 wait_for_client: FINDCREATEDISPLAY cmd: /bin/sh
/tmp/x11vnc-find_display.6MA32O Xvfb
-p: not found
trying N=20 ...
The program "Xvfb" could not be found in PATH and standard locations.
You probably need to install a package that provides the "Xvfb" program.
07/02/2012 16:17:25 wait_for_client: read failed: /bin/sh
/tmp/x11vnc-find_display.6MA32O Xvfb
07/02/2012 16:17:25 fgets: Bad file descriptor
[rna na mumu] /home/rna#
Sice mi to sdeluje nejake dobre minene rady, ale vubec z toho nejsem moudry.
Jak to, je nekdy zridkakdy po bootu to naskoci a jede, ale jina ne.
Stejne tak, proc mi x11vnc na OpenSuSE jede jak z praku
a tady se s tim patlam uz kolik hodin bezvysledne.
Podotykam, ze storepasswd jsem provedl, zadal heslo, vse se
jakoby bez protestu ulozilo.
Firewall jsem vypnul, aby neprekazel.
Co je kde spatne?
More information about the Users-l
mailing list