| View previous topic :: View next topic |
| Author |
Message |
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
 Posted: Tue Jun 20, 2006 10:15 pm Post subject: ssh e wm |
 |
|
Ho un server con installato X e fluxbox, il client è una livecd con knoppix.
Entrambe le macchine sono nella stessa rete.
Lato server metto in start sshd.....
Lato client faccio:
| Code: |
ssh utente server.remoto |
poi mi loggo.
Fatto questo voglio lanciare fluxbox dal client, cioè visualizzarlo sul client.
Ho provato con startfluxbox, startx, fluxbox ecc....... ma come risultato ottengo che parte il WM sul server, c' è il modo per lanciare sul server fluxbox e poi visualizzarlo sul client ?
Saluto |
|
| Back to top |
|
 |
tizio
Guru
Joined: 22 Mar 2005
Posts: 365
|
| Posted: Tue Jun 20, 2006 10:20 pm Post subject: |
|
|
from "man ssh":
-X Abilita l'inoltro di connessioni X11. |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Tue Jun 20, 2006 11:04 pm Post subject: |
|
|
| tizio wrote: | from "man ssh":
-X Abilita l'inoltro di connessioni X11. |
Ho già provato con ssh -X e ssh -Y e dice :
display is null
Se lancio con startx:
| Code: | X Window System Version 7.1.0
Release Date: 22 May 2006
X Protocol Version 11, Revision 0, Release 7.1
Build Operating System: Linux 2.6.16-gentoo-r9 i686
Current Operating System: Linux 2.6.16-gentoo-r9 #6 PREEMPT Thu Jun 15 11:17:10 GMT 2006 i686
Build Date: 15 June 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 21 00:59:53 2006
(==) Using config file: "/etc/X11/xorg.conf"
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc102)+it" };
xkb_geometry { include "pc(pc102)" };
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Logging to: /home/utente/.fluxbox/log
BScreen::BScreen: managing screen 0 using visual 0x22, depth 16
Idesk starting in :0.0
[idesk] Background's file not found.
[idesk] Background's source not found. |
....... e parte fluxbox sul server
Saluto |
|
| Back to top |
|
|
guerro
Guru
Joined: 21 Jun 2004
Posts: 417
Location: Brescia
|
| Posted: Wed Jun 21, 2006 6:41 am Post subject: |
|
|
Domanda stupida:
Hai abilitato nei file di configurazione di ssh (sshd_config sul server e ssh_config sul client) l'X11 forwarding e riavviato sshd sul server  
_________________
(.(*. .*).)
.. G u e r r o ..
(.(.* *.).) |
|
| Back to top |
|
|
gutter
Bodhisattva
Joined: 13 Mar 2004
Posts: 7162
Location: Aarau, Aargau, Switzerland
|
| Posted: Wed Jun 21, 2006 9:03 am Post subject: |
|
|
Posta un:
sulla macchina da cui lanci il client ssh.
_________________
Registered as User #281564 and Machines #163761 |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Wed Jun 21, 2006 9:05 am Post subject: |
|
|
| guerro wrote: | Domanda stupida:
Hai abilitato nei file di configurazione di ssh (sshd_config sul server e ssh_config sul client) l'X11 forwarding e riavviato sshd sul server |
LATO SERVER
ssh_config
| Code: | $OpenBSD: ssh_config,v 1.21 2005/12/06 22:38:27 reyk Exp $
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.
# Host *
# ForwardAgent no
ForwardX11 yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
PasswordAuthentication yes
# HostbasedAuthentication no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
PermitLocalCommand yes |
sshd.config
| Code: | # $OpenBSD: sshd_config,v 1.73 2005/12/06 22:38:28 reyk Exp $
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options change a
# default value.
#Port 22
Protocol 2
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 768
# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO
# Authentication:
#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile .ssh/authorized_keys
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication yes
#PermitEmptyPasswords no
# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication mechanism.
# Depending on your PAM configuration, this may bypass the setting of
# PasswordAuthentication, PermitEmptyPasswords, and
# "PermitRootLogin without-password". If you just want the PAM account and
# session checks to run without PAM authentication, then enable this but set
# ChallengeResponseAuthentication=no
UsePAM yes
AllowTcpForwarding yes
#GatewayPorts no
X11Forwarding yes
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
# no default banner path
#Banner /some/path
# override default of no subsystems
Subsystem sftp /usr/lib/misc/sftp-server |
LATO CLIENT
ssh_config
| Code: |
# $OpenBSD: ssh_config,v 1.21 2005/12/06 22:38:27 reyk Exp $
# This is the ssh client system-wide configuration file. See
# ssh_config(5) for more information. This file provides defaults for
# users, and the values can be changed in per-user configuration files
# or on the command line.
# Configuration data is parsed as follows:
# 1. command line options
# 2. user-specific file
# 3. system-wide file
# Any configuration value is only changed the first time it is set.
# Thus, host-specific definitions should be at the beginning of the
# configuration file, and defaults at the end.
# Site-wide defaults for some commonly used options. For a comprehensive
# list of available options, their meanings and defaults, please see the
# ssh_config(5) man page.
# Host *
# ForwardAgent no
ForwardX11 yes
# RhostsRSAAuthentication no
# RSAAuthentication yes
PasswordAuthentication yes
# HostbasedAuthentication no
# BatchMode no
# CheckHostIP yes
# AddressFamily any
# ConnectTimeout 0
# StrictHostKeyChecking ask
# IdentityFile ~/.ssh/identity
# IdentityFile ~/.ssh/id_rsa
# IdentityFile ~/.ssh/id_dsa
Port 22
# Protocol 2,1
# Cipher 3des
# Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc
# EscapeChar ~
# Tunnel no
# TunnelDevice any:any
# PermitLocalCommand no |
sshd_config
| Code: | # $OpenBSD: sshd_config,v 1.73 2005/12/06 22:38:28 reyk Exp $
# This is the sshd server system-wide configuration file. See
# sshd_config(5) for more information.
# This sshd was compiled with PATH=/usr/bin:/bin:/usr/sbin:/sbin
# The strategy used for options in the default sshd_config shipped with
# OpenSSH is to specify options with their default value where
# possible, but leave them commented. Uncommented options change a
# default value.
#Port 22
Protocol 2
#AddressFamily any
#ListenAddress 0.0.0.0
#ListenAddress ::
# HostKey for protocol version 1
#HostKey /etc/ssh/ssh_host_key
# HostKeys for protocol version 2
#HostKey /etc/ssh/ssh_host_rsa_key
#HostKey /etc/ssh/ssh_host_dsa_key
# Lifetime and size of ephemeral version 1 server key
#KeyRegenerationInterval 1h
#ServerKeyBits 768
# Logging
# obsoletes QuietMode and FascistLogging
#SyslogFacility AUTH
#LogLevel INFO
# Authentication:
#LoginGraceTime 2m
#PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#RSAAuthentication yes
#PubkeyAuthentication yes
#AuthorizedKeysFile .ssh/authorized_keys
# For this to work you will also need host keys in /etc/ssh/ssh_known_hosts
#RhostsRSAAuthentication no
# similar for protocol version 2
#HostbasedAuthentication no
# Change to yes if you don't trust ~/.ssh/known_hosts for
# RhostsRSAAuthentication and HostbasedAuthentication
#IgnoreUserKnownHosts no
# Don't read the user's ~/.rhosts and ~/.shosts files
#IgnoreRhosts yes
# To disable tunneled clear text passwords, change to no here!
PasswordAuthentication no
#PermitEmptyPasswords no
# Change to no to disable s/key passwords
#ChallengeResponseAuthentication yes
# Kerberos options
#KerberosAuthentication no
#KerberosOrLocalPasswd yes
#KerberosTicketCleanup yes
#KerberosGetAFSToken no
# GSSAPI options
#GSSAPIAuthentication no
#GSSAPICleanupCredentials yes
# Set this to 'yes' to enable PAM authentication, account processing,
# and session processing. If this is enabled, PAM authentication will
# be allowed through the ChallengeResponseAuthentication mechanism.
# Depending on your PAM configuration, this may bypass the setting of
# PasswordAuthentication, PermitEmptyPasswords, and
# "PermitRootLogin without-password". If you just want the PAM account and
# session checks to run without PAM authentication, then enable this but set
# ChallengeResponseAuthentication=no
UsePAM yes
#AllowTcpForwarding yes
#GatewayPorts no
#X11Forwarding no
#X11DisplayOffset 10
#X11UseLocalhost yes
#PrintMotd yes
#PrintLastLog yes
#TCPKeepAlive yes
#UseLogin no
#UsePrivilegeSeparation yes
#PermitUserEnvironment no
#Compression delayed
#ClientAliveInterval 0
#ClientAliveCountMax 3
#UseDNS yes
#PidFile /var/run/sshd.pid
#MaxStartups 10
#PermitTunnel no
# no default banner path
#Banner /some/path
# override default of no subsystems
Subsystem sftp /usr/lib/misc/sftp-server |
Poi, sul server lancio /etc/init.d/sshd start
sul client lancio: ssh -X utente@ip_server
secondo voi con la gentoo devo settare qualcosa di più ?
Saluto |
|
| Back to top |
|
|
gutter
Bodhisattva
Joined: 13 Mar 2004
Posts: 7162
Location: Aarau, Aargau, Switzerland
|
| Posted: Wed Jun 21, 2006 9:19 am Post subject: |
|
|
| silvius wrote: |
secondo voi con la gentoo devo settare qualcosa di più ?
Saluto |
Devi far girare il server X sulla macchina client in ascolto sulla porta TCP/6000.
_________________
Registered as User #281564 and Machines #163761 |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Wed Jun 21, 2006 10:05 am Post subject: |
|
|
| gutter wrote: |
Devi far girare il server X sulla macchina client in ascolto sulla porta TCP/6000. |
Quindi devo fare un ssh sulla porta 6000, e poi lanciare X sul client e dopo lanciare startfluxbox, giusto ?
Saluto |
|
| Back to top |
|
|
comio
Advocate
Joined: 03 Jul 2003
Posts: 2191
Location: Taranto
|
| Posted: Wed Jun 21, 2006 10:11 am Post subject: |
|
|
| silvius wrote: | | gutter wrote: |
Devi far girare il server X sulla macchina client in ascolto sulla porta TCP/6000. |
Quindi devo fare un ssh sulla porta 6000, e poi lanciare X sul client e dopo lanciare startfluxbox, giusto ?
Saluto |
No.
Devi:
- Avviare X sulla macchina locale (in ascolto sulla porta tcp 6000);
- Effettuare ssh -X verso la macchina remota
- Assicurarti che la variabile DISPLAY sia impostata (dovrebbe essere qualcosa del tipo DISPLAY=localhost:10.0), prova magari ad eseguire un xclock per vedere se va
- Eseguire la tua applicazione X (fluxbox) sulla macchina remota
ciao
_________________
RTFM!!!!
e
http://www.comio.it
 |
|
| Back to top |
|
|
gutter
Bodhisattva
Joined: 13 Mar 2004
Posts: 7162
Location: Aarau, Aargau, Switzerland
|
| Posted: Wed Jun 21, 2006 10:36 am Post subject: |
|
|
| comio wrote: | prova magari ad eseguire un xclock per vedere se va
- Eseguire la tua applicazione X (fluxbox) sulla macchina remota
|
Il test scientifico si effettua sempre con xeyes 
_________________
Registered as User #281564 and Machines #163761 |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Wed Jun 21, 2006 10:48 am Post subject: |
|
|
| comio wrote: |
No.
Devi:
- Avviare X sulla macchina locale (in ascolto sulla porta tcp 6000);
- Effettuare ssh -X verso la macchina remota
- Assicurarti che la variabile DISPLAY sia impostata (dovrebbe essere qualcosa del tipo DISPLAY=localhost:10.0), prova magari ad eseguire un xclock per vedere se va
- Eseguire la tua applicazione X (fluxbox) sulla macchina remota
ciao |
Domanda stupida: dove trovo la variabile display ?
Se sul server lancio
non mi dice nulla.
Se sul server remoto lancio
mi risponde che non può aprire il display.
Comunque sul server fluxbox funziona.
Per mettere X in ascolto gli passo l' opzione tcp/hostname:6000, giusto ?
ho trovato un tuo post vecchio che diceva di usare ssh così:
"ssh -R 6001:localhost:6000 utente@macchinaremota
poi sulla macchina remota dai il comando:
export DISPLAY=localhost:1.0 "
Proverò a fare così
Saluto |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Wed Jun 21, 2006 6:51 pm Post subject: |
|
|
Ho provato ad usare il metodo ssh -R........, ma non funziona:
| Code: | localhost ~ # ssh -X utente@192.168.0.50
Password:
Last login: Wed Jun 21 14:33:20 2006 from 192.168.0.27
utente@ca ~ $ startfluxbox
(ROX-Filer:5983): Gtk-WARNING **: cannot open display:
Display is null!!
Logging to: /home/utente/.fluxbox/log
utente@ca ~ $ startx
hostname: Unknown host
xauth: creating new authority file /home/utente/.serverauth.5989
X Window System Version 7.1.0
Release Date: 22 May 2006
X Protocol Version 11, Revision 0, Release 7.1
Build Operating System: Linux 2.6.16-gentoo-r9 i686
Current Operating System: Linux ca 2.6.16-gentoo-r9 #6 PREEMPT Thu Jun 15 11:17:10 GMT 2006 i686
Build Date: 15 June 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 21 20:37:40 2006
(==) Using config file: "/etc/X11/xorg.conf"
xkb_keycodes { include "xfree86+aliases(qwerty)" };
xkb_types { include "complete" };
xkb_compatibility { include "complete" };
xkb_symbols { include "pc(pc102)+it" };
xkb_geometry { include "pc(pc102)" };
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
Logging to: /home/utente/.fluxbox/log
Idesk starting in :0.0
[idesk] Background's file not found.
[idesk] Background's source not found.
BScreen::BScreen: managing screen 0 using visual 0x22, depth 16
waiting for X server to shut down XIO: fatal IO error 104 (Connection reset by peer) on X server ":0.0"
after 4339 requests (4336 known processed) with 6 events remaining.
FreeFontPath: FPE "/usr/share/fonts/misc" refcount is 2, should be 1; fixing.
Couldnt get a file descriptor referring to the console
utente@ca ~ $
xinit: unexpected signal 2.
utente@ca ~ $ exit
logout
Connection to 192.168.0.50 closed.
localhost ~ # ssh -R 6001:localhost:6000 utente@192.168.0.50
Password:
Last login: Wed Jun 21 20:37:17 2006 from 192.168.0.27
utente@ca ~ $ export DISPLAY=localhost:1.0
utente@ca ~ $ startfluxbox
The application 'ROX-Filer' lost its connection to the display localhost:1.0;
most likely the X server was shut down or you killed/destroyed
the application.
Logging to: /home/utente/.fluxbox/log
X connection to localhost:1.0 broken (explicit kill or server shutdown).
utente@ca ~ $ X connection to localhost:1.0 broken (explicit kill or server shutdown).
utente@ca ~ $ exit
logout
Connection to 192.168.0.50 closed.
localhost ~ # nmap localhost
-su: nmap: command not found
localhost ~ # netstat -tlp
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
localhost ~ # |
Come faccio a mettere X client in ascolto sulla 6000 ?
Saluto |
|
| Back to top |
|
|
.:chrome:.
Advocate
Joined: 19 Feb 2005
Posts: 4588
Location: Brescia, Italy
|
| Posted: Wed Jun 21, 2006 6:59 pm Post subject: |
|
|
| silvius wrote: | | Come faccio a mettere X client in ascolto sulla 6000 ? |
quella è ovviamente un'impostazione di X, non di SSH
se usi GDM basta disabilitare la voce DisallowTCP che per default è a true. con gli altri login managerci sarà qualcosa di simile |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Wed Jun 21, 2006 8:38 pm Post subject: |
|
|
| k.gothmog wrote: | | silvius wrote: | | Come faccio a mettere X client in ascolto sulla 6000 ? |
quella è ovviamente un'impostazione di X, non di SSH
se usi GDM basta disabilitare la voce DisallowTCP che per default è a true. con gli altri login managerci sarà qualcosa di simile |
Se io non usassi un login manager non posso attivare X sulla tcp ?
All' inizio ho fatto delle prove senza nessun login manager, poi ho emerso gdm ma ho gli stessi problemi anzi peggio perchè adesso con gdm quando mi loggo mi dice :
| Code: | /etc/X11/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/X11/gdm/PreSession/Default: running: /usr/X11R6/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/gdm/:0.Xservers" -h "" -l ":0" "root"
/etc/X11/gdm/Xsession: Beginning session setup...
/etc/X11/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
gnome-session: No such file or directory |
Non è che ho problemi per questo ?
Saluto |
|
| Back to top |
|
|
.:chrome:.
Advocate
Joined: 19 Feb 2005
Posts: 4588
Location: Brescia, Italy
|
| Posted: Wed Jun 21, 2006 8:49 pm Post subject: |
|
|
| silvius wrote: | | Se io non usassi un login manager non posso attivare X sulla tcp ? |
no. ssh-agent è un'altra cosa
se non vado errato quando si avvia X11 con startx, viene aperta in listen la porta 6000. puoi verificare semplicemente avviando X11 e dando il comando netstat -lntup.
se così non fosse c'è da modificare startx, che è uno script, quindi in questo non ci sono problemi, se non per il fatto che dopo ogni aggiornamento di xorg-x11 (o xorg-server, più verosimilmente) la modifica andrebbe perduta.
questo solleva però un problema: io sono sicuro al 90% che l'impostazione predefinita è quella di aprire il socket all'atto dell'avvio del server grafico, con startx. questo vuol dire però che per poterti collegare ad una macchina questa deve avere X11 attivo, diversamente non penso proprio che tu ti possa collegare. in altre parole o rimani sempre loggato o usi un login manager.
sottolineo però che non è un argomento che ho mai approfondito, e spero che qualcuno più ferrato possa darti un'opinione più affidabile della mia |
|
| Back to top |
|
|
gutter
Bodhisattva
Joined: 13 Mar 2004
Posts: 7162
Location: Aarau, Aargau, Switzerland
|
| Posted: Wed Jun 21, 2006 8:56 pm Post subject: |
|
|
Vediamo se riesco ad essere esaustivo. Hai due opzioni per lanciare sul computer client, un server X che stia in ascolto sulla porta TCP/6000. La prima, è quella di usare un login manager come XDM, GDM, ecc. La seconda è quella di modificare il file /usr/bin/startx e precisamente la riga:
| Code: | | defaultserverargs="-nolisten tcp -br" |
in
| Code: | | defaultserverargs="tcp -br" |
Fatto ciò sempre sulla macchina client usa xhost per abilitare l'accesso al tuo display:
P.S.: Consiglio una lettura della sintassi di xhost dato che il comando prevdente permette l'accesso al display della tua macchina da parte di qualunque pc.
_________________
Registered as User #281564 and Machines #163761 |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Wed Jun 21, 2006 9:41 pm Post subject: |
|
|
Ci siamo quasi, allora con gdm sul pc remoto ho X in ascolto sulla 6001.
Da locale entro con ssh -X ( o -Y ) root@ip_remoto
poi lancio startfluxbox e non và
lancio xhost +, poi startfluxbox e non và
lancio export DISPLAY=localhost:10.0, poi startfluxbox e non và
i log di fluxbox :
| Code: |
.............................
BScreen::BScreen: an error occured while querying the X server.
another window manager already running on displaylocalhost:11.0
Error: Couldn't find screens to manage.
Make sure you don't have another window manager running. |
Sul remoto ho provato sia quando ero loggato che quando non lo ero ( cioè in attesa di log)
E' come se sul remoto ci sia già avviato un WM, ma c'è solo gdm.
Saluto |
|
| Back to top |
|
|
gutter
Bodhisattva
Joined: 13 Mar 2004
Posts: 7162
Location: Aarau, Aargau, Switzerland
|
| Posted: Thu Jun 22, 2006 7:52 am Post subject: |
|
|
| silvius wrote: | | Ci siamo quasi, allora con gdm sul pc remoto ho X in ascolto sulla 6001. |
X lo devi avere in ascolto sul pc locale.
| silvius wrote: |
Da locale entro con ssh -X ( o -Y ) root@ip_remoto
poi lancio startfluxbox e non và
lancio xhost +, poi startfluxbox e non và
|
Non puo lanciare fluxbox. Prova a lanciare un xterm e xeyes.
_________________
Registered as User #281564 and Machines #163761 |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Thu Jun 22, 2006 6:14 pm Post subject: |
|
|
| gutter wrote: |
X lo devi avere in ascolto sul pc locale.
Non puo lanciare fluxbox. Prova a lanciare un xterm e xeyes. |
Mi sa che non ho capito bene come funziona X con ssh:
Non posso lanciare un WM, o fare direttamente startX ?
Quindi quando uso ssh -X ( pc locale ) devo già essere dentro una WM, giusto ?
Saluto |
|
| Back to top |
|
|
silvius
Guru
Joined: 16 May 2006
Posts: 364
|
| Posted: Fri Jun 23, 2006 5:23 pm Post subject: |
|
|
Leggendo un pò di cose non ho capito se è possibile avere un pc remoto con caricato solo gnome senza X, mentre il pc locale ha solo X e lancia gnome con SSH ?
Saluto |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Forum italiano (Italian)
