Re: XDMCP and GDM3
Hi Rob, Rob Owens wrote: > On Mon, Nov 28, 2011 at 04:22:07PM +0100, Martin Feuersänger wrote: >> I know which files control the KDM behavior in regard to XDMCP (kdmrc >> and Xaccess, both in /etc/kde4/kdm/). >> But for GDM3 I have no idea where this is done. It just worked. Xaccess >> at /etc/X11/xdm/ had no influence so it must be somewhere else. >> >> > On my Squeeze system, there is /etc/gdm3/daemon.conf, which has an XDMCP > section. I'm taking a wild guess here, but you might add something to that > section like: Thanks for the suggestion, I forgot that we actually set 'Enable=true' in the XDMCP section of /etc/gdm3/daemon.conf, otherwise GDM3 doesn't even listen on port 177. Then it seems that GDM3 allows every host to access directly and indirectly. Several configuration examples that cover all of xdm, gdm and kdm seem to suggest this. They explicitly mention mention Xaccess for both xdm and kdm but leave it out for gdm. If GDM3 still behaves like the older GDM I guess http://library.gnome.org/admin/gdm/stable/configuration.html.en has the answer: HonorIndirect=true Enables remote execution of the chooser, 'true' seems to be default. Regarding access control the document says: "If GDM is compiled to support it, access from remote displays can be controlled using the TCP Wrappers library. The service name is gdm You should add gdm:.my.domain to your /hosts.allow, depending on your TCP Wrappers configuration." Cheers, Martin -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/6729.168.87.60.62.1322741297.squir...@wm.feuersaenger.de
Re: XDMCP and GDM3
On Mon, Nov 28, 2011 at 04:22:07PM +0100, Martin Feuersänger wrote: > Hi list, > > a while ago we played a bit with XDMCP at the local LUG gathering here in > Frankfurt, Germany. > > One machine was running KDE 4.6.5 (sid) and the other Gnome 3 (squeeze). > > We managed to get a Chooser on each machine from the respective other > machine by issuing > X :1 -broadcast -indirect > Each time the Chooser offered both machines. > > Now to my question. > > I know which files control the KDM behavior in regard to XDMCP (kdmrc and > Xaccess, both in /etc/kde4/kdm/). > But for GDM3 I have no idea where this is done. It just worked. Xaccess at > /etc/X11/xdm/ had no influence so it must be somewhere else. > On my Squeeze system, there is /etc/gdm3/daemon.conf, which has an XDMCP section. I'm taking a wild guess here, but you might add something to that section like: chooser = true I think the old gdm.conf file had a lot of commented out examples in it, if you can dig that up from somewhere. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2029170251.gc18...@aurora.owens.net
Re: XDMCP mess
On Thu, Nov 11, 2010 at 13:51, Rob Owens wrote: > Maybe you should be using LTSP. It will pxe boot pretty much anything, > and then do a remote GUI session to your server -- sound included. I don't want PXE, but rather two sessions (one local one remote), but i'll look into it, thanks. -- Mars 2 Stay! http://xkcd.com/801/ /etc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktik7xd+dwtvjiwduapmd5bhwdpokdvytkrhto...@mail.gmail.com
Re: XDMCP mess
On Thu, Nov 11, 2010 at 01:39:12PM +, Nuno Magalhães wrote: > On Thu, Nov 11, 2010 at 01:38, Arnt Karlsen wrote: > >> Now it's pulseaudio, seems simple but i'm missing something (it's > >> listening!). > > > > ..for XDMCP connections? > > Well yeah, XDMCP doesn't carry sound. My progress so far has been > losing sound altogether, but got it back on. Both boxes have > pulseaudio but the local one only sometimes sees the remote one. I'm > still fiddling with it + ALSA. > Maybe you should be using LTSP. It will pxe boot pretty much anything, and then do a remote GUI session to your server -- sound included. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2010135111.gc18...@aurora.owens.net
Re: XDMCP mess
On Thu, Nov 11, 2010 at 01:38, Arnt Karlsen wrote: >> Now it's pulseaudio, seems simple but i'm missing something (it's >> listening!). > > ..for XDMCP connections? Well yeah, XDMCP doesn't carry sound. My progress so far has been losing sound altogether, but got it back on. Both boxes have pulseaudio but the local one only sometimes sees the remote one. I'm still fiddling with it + ALSA. Stay tuned. -- Mars 2 Stay! http://xkcd.com/801/ /etc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktiktkyp-ky1vy9qk=hxomf8cqbjcrelm83sx4...@mail.gmail.com
Re: XDMCP mess
On Wed, 10 Nov 2010 00:33:32 +, Nuno wrote in message : > On Mon, Nov 8, 2010 at 19:28, Arnt Karlsen wrote: > > ..ok, then it's back to my hint to find out if X is listening > > at all, to anything but localhost. > > I must've commented out the remote xdm-config once testing with Xming > was done and forgot about it. After uncommenting it again the local > gdm chooser found the remote machine and i was greeted by the remote > XDM. > > Now it's pulseaudio, seems simple but i'm missing something (it's > listening!). ..for XDMCP connections? If not, your pulseaudio challenge probably warrants its own thread and I'm blank there. ;o) > Thanks for the heads up. > -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/2010023834.6e7f4...@a45.fmb.no
Re: XDMCP mess
On Mon, Nov 8, 2010 at 19:28, Arnt Karlsen wrote: > ..ok, then it's back to my hint to find out if X is listening > at all, to anything but localhost. I must've commented out the remote xdm-config once testing with Xming was done and forgot about it. After uncommenting it again the local gdm chooser found the remote machine and i was greeted by the remote XDM. Now it's pulseaudio, seems simple but i'm missing something (it's listening!). Thanks for the heads up. -- Mars 2 Stay! http://xkcd.com/801/ /etc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktikpu65ryvlxsa3nthayrydfnnw_sa5j-6q4p...@mail.gmail.com
Re: XDMCP mess
On Mon, 8 Nov 2010 13:56:13 +, Nuno wrote in message : > On Mon, Nov 8, 2010 at 03:14, Arnt Karlsen wrote: > > ..I lost you here, do you have your XDMCP connection working now??? > > No, manpages and comments in .conf files. ..ok, then it's back to my hint to find out if X is listening at all, to anything but localhost. -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101108202833.5f0c3...@a45.fmb.no
Re: XDMCP mess
On Mon, Nov 8, 2010 at 03:14, Arnt Karlsen wrote: > ..I lost you here, do you have your XDMCP connection working now??? No, manpages and comments in .conf files. -- Mars 2 Stay! http://xkcd.com/801/ /etc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktimfzpxiq92sncfnyrjnel_jsbxq65gw+dl7y...@mail.gmail.com
Re: XDMCP mess
On Mon, 8 Nov 2010 00:50:13 +, Nuno wrote in message : > On Mon, Nov 8, 2010 at 00:30, Arnt Karlsen wrote: > > ..try ' ps axu |grep nolisten '. ;o) > > XDMCP works well with UDP and there's no reason to use TCP, SSH can > tunnel UDP. The only nolisten's i use are for TCP. ..I lost you here, do you have your XDMCP connection working now??? -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101108041434.250e4...@a45.fmb.no
Re: XDMCP mess
On Mon, Nov 8, 2010 at 00:30, Arnt Karlsen wrote: > ..try ' ps axu |grep nolisten '. ;o) XDMCP works well with UDP and there's no reason to use TCP, SSH can tunnel UDP. The only nolisten's i use are for TCP. -- Mars 2 Stay! http://xkcd.com/801/ /etc -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktik-sn8+wnqbprhedryhspxuzazlzdh3rzks1...@mail.gmail.com
Re: XDMCP mess
On Sun, 7 Nov 2010 14:24:57 +, Nuno wrote in message : > Greetings, > > I've been trying to set up an XDMCP connection for a few days in my > LAN, to no avail. My current setup is: > - one desktop running two xservers, one managed by slim, the other by > xdm. I was able to connect to this xdm from one of the winVMs using > Xming. > - one laptop running one xserver manage by gdm, from where i'm trying > to connect to the desktop, > > I've added magic cookies with xauth, fiddled with xdm's Xservers, > wondered why gdm's conf is not under /etc/X11 and fiddled with it as > well, added :x lines to files, uncomented, read howtos that are not as > detailed as i'd like (and mostly assume remote linux local windows), > etc. My conf files are a mess. > > There's also chooser, but the laptop's gdm doesn't find anything on > the LAN. I don't need two xservers on the desktop, but it should allow > local and remote inbound connections. Same for the laptop, outbound. I > don't care which DM i use. I've briefly tried Xnest but couldn't even > get it to start. > > Does anyone have some nice detailed RTFM suggestions and/or tips? ..try ' ps axu |grep nolisten '. ;o) -- ..med vennlig hilsen = with Kind Regards from Arnt... ;o) ...with a number of polar bear hunters in his ancestry... Scenarios always come in sets of three: best case, worst case, and just in case. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20101108013055.4a5c3...@a45.fmb.no
Re: XDMCP in GDM Not Working
On Thu, Feb 25, 2010 at 5:45 PM, Rob Owens wrote: > On Wed, Feb 24, 2010 at 01:12:48AM -0800, Scarletdown wrote: > > I have GDM XDMCP enabled. However, when I select on the GDM screen to > login > > to a remote system via XDMCP, the system scans the netowrk and then > returns > > a claim of No Serving Hosts Were Found. > > > > I know this is wrong, because another box on my network is also XDMCP > > enabled, and its GDM chooser is only showing itself as an available host. > > > > Both systems are running Debian Unstable. The one that can at least see > > itself is running an older version of GDM (I have no idea what version). > > The other one that sees nothing on the network is running whatever the > > latest GDM in the Debian repositories is. > > Did you restart GDM after enabling XDMCP? I think that's required, but > I'm not positive. > > -Rob > Yes, GDM was restarted several times (including via reboot just for the helluvit.)
Re: XDMCP in GDM Not Working
On Wed, Feb 24, 2010 at 01:12:48AM -0800, Scarletdown wrote: > I have GDM XDMCP enabled. However, when I select on the GDM screen to login > to a remote system via XDMCP, the system scans the netowrk and then returns > a claim of No Serving Hosts Were Found. > > I know this is wrong, because another box on my network is also XDMCP > enabled, and its GDM chooser is only showing itself as an available host. > > Both systems are running Debian Unstable. The one that can at least see > itself is running an older version of GDM (I have no idea what version). > The other one that sees nothing on the network is running whatever the > latest GDM in the Debian repositories is. Did you restart GDM after enabling XDMCP? I think that's required, but I'm not positive. -Rob -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100226014531.gh25...@aurora.owens.net
Re: XDMCP build
On 2009-12-17, Jamie White wrote: > Hi > > Does anyone know a quick way I could a computer running a Linux build > solely for the purpose of XDMCP? > > Do a minimal install, then install xorg. Then you start the X server using the command 'X -query '. -- Liam O'Toole Birmingham, United Kingdom -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: xdmcp remote login, can log in to the server from one computer but not another
On Thu, Jan 22, 2009 at 06:48:37PM +0200, Micha Feigin wrote: > I'm trying to setup xdmcp login on one of my servers. > > This server has two network interfaces (actually 4, but two active). > > I'm trying to log in to X using xdmcp (enabled via gdm config) from two > clients, one connected directly via gigabit ethernet and the other over 100mb > network via an intermidiate switch. > > The setup: > > client one <--- (network) ---> server <--- (direct) ---> client two > 132.66.40.189 132.66.41.26/192.168.1.1 192.168.1.2 > > client two connects with no problem. Client one sees the correct details for > the sever once it's given the address but hangs on connect (all I see is the > gray screen and the mouse cursor, nothing comes up) > > The server is running gdm with xdmcp enabled, no firewall at the moment. > I could be completely wrong, but I have not managed to get gdm to support xdmcp logins for about a year now. Symptoms are as you described, on Suse11 and Ubuntu8.?? systems. Some discussion of the problem on various forums, but no fix that I can see. Gdm worked on earlier versions of the same distro's. I end up having to use kdm, which works. Rgds, -- Mike Bishop Willow, Alaska -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: XDMCP Capable Login Managers
On Sat, Aug 30, 2008 at 07:08:20PM -0700, Scarletdown wrote: > Other than GDM and KDM, are there any other graphical login managers > that allow a client to login to a remote machine via XDMCP? I was > hoping that WDM (Wings Display Manager) could do this, but I have not > seen any option on the login screen to connect to a remote machine. WDM is based on XDM, which does have xdmcp capabilities. That said, I find both to be very frustrating and feature-poor. > > I have a really lean old Toshiba laptop that I am wanting to put a very > minimal Debian installation on and essentially run it as a thin client > connected to a more hefty system. GDM is too resource intensive (I > think) for this old laptop, unless there is a way to get GDM without all > the additional GNOME baggage that normally goes with it. gdm's GUI is only used before you login. Its daemon is not that resource intensive. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP question
Hüvely Balázs wrote: Hi All! I have a problem with XDMCP. It's works fine, i can connect it to XDMCP remote server, but i cannot disconnect from the session... I only able to log out, and re-login. How can I make detachable XDMCP sessions like in windows remote desktop. I do not think that is possible. Another example that i created VNC server, it's also works fine, but i need to login to gdm, and after i'm able to connect to it via the internet. The only problem is: after I restart the server, i cannot connect to it, because vnc don't accept connections until I re login locally... how can I make working vnc, to handle login and logout too? Add the commands to start the vncserver to /etc/rc.local so that it will be started when the system starts. I think the most secure way to start gui applications on the remote host is through ssh. Use "ssh -X " to enable X11 forwarding. -- Raj Kiran -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Brockway wrote: > On Sun, 29 Apr 2007, Daniel D Jones wrote: > >>> One more thing: There is a reported but unfixded bug in kdm in >>> Debian/Ubuntu going back a long way which is causing some xdmcp >>> configurations to fail when they really are ok. If you look in your >>> logs >>> you'll see reports of kdm_greet getting memory corruption if you are >>> getting this problem. As a result of this problem I recently migrated a >>> bunch of thin client servers to use gdm instead of kdm. >> >> You didn't specify which log but I didn't find any such errors in either >> kdm.log or Xorg.0.log, nor did I find any other related errors in the >> log. >> Maybe I'll try switching to xdm just to see. > > It depends on how you have syslog configured. I recommend running a > debug log to catch all the info. You can grep for the following error > coming from kdm_greet: > > "Internal error: memory corruption detected" > > Cheers, > > Rob > I will just input that I was having a big issue with KDM and XDMCP with Etch a few days ago. The solution I found was to switch the host (X Client, the one doing the work) to GDM instead of KDM. Then it just sort of worked. I still do not know why KDM didn't. The X Server runs KDM and connects to the GDM X Client (XDMCP Server?) just fine. - -- Please do not use HTML mail for fully-textual messages. Matthew K Poer <[EMAIL PROTECTED]> Location: GA, USA Web: http://matthewpoer.freehostia.com GnuPG Public Key: 4DD0A9A6 Keyserver: subkeys.pgp.net Thinkpad 600: Debian Sarge Sony VAIO PCV-RS 520: Debian Etch -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with MultiZilla - http://enigmail.mozdev.org iD8DBQFGNUb9kRdiiE3QqaYRAk9YAJ0f6fKFM6gUtY783PtPUH6NAc1/HACfeNta Aie/0IXhBcMkMqdZEaTYbEU= =u/sO -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP
On Sun, 29 Apr 2007, Daniel D Jones wrote: One more thing: There is a reported but unfixded bug in kdm in Debian/Ubuntu going back a long way which is causing some xdmcp configurations to fail when they really are ok. If you look in your logs you'll see reports of kdm_greet getting memory corruption if you are getting this problem. As a result of this problem I recently migrated a bunch of thin client servers to use gdm instead of kdm. You didn't specify which log but I didn't find any such errors in either kdm.log or Xorg.0.log, nor did I find any other related errors in the log. Maybe I'll try switching to xdm just to see. It depends on how you have syslog configured. I recommend running a debug log to catch all the info. You can grep for the following error coming from kdm_greet: "Internal error: memory corruption detected" Cheers, Rob -- Robert Brockway B.Sc.Phone: +1-905-821-2327 Senior Technical Consultant Urgent Support: +1-416-669-3073 OpenTrend Solutions Ltd Email: [EMAIL PROTECTED] Web:www.opentrend.net Contributing Member of Software in the Public Interest -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP
On Saturday 28 April 2007 15:23, Robert Brockway wrote: Thanks for the response. > On Sat, 28 Apr 2007, Daniel D Jones wrote: > > Running unstable. Trying to get XDMCP working via KDM. On the local > > host, everything works. KDM gives me a graphical login prompt, and KDE > > loads when I log in. From a remote machine, however, I get what appears > > to be a pure X session with no Windows manager running. I get the hollow > > X cursor, and am able to move it with the mouse. However, neither left > > nor right clicks do any thing - no menu or anything. Clicking and > > dragging doesn't generate a dotted outline selection. No key presses > > appear to do anything. Not sure where to go from here. Hints and > > suggestions welcome. > > Checkout /etc/kde3/kdem/Xaccess to see what sorts of xdmcp access you > are allowing. At the least you want to offer: > > > * #any host can get a login window > > You may also want to allow: > > > * CHOOSER BROADCAST #any indirect host can get a > chooser [EMAIL PROTECTED]:/etc/kde3/kdm# cat Xaccess | grep ^[^#] * #any host can get a login window * CHOOSER BROADCAST #any indirect host can get a chooser > Also you need to enable xdmcp in kdmrc: > > # Whether KDM should listen to incoming XDMCP requests. > # Default is true > Enable=true [EMAIL PROTECTED]:/etc/kde3/kdm# cat kdmrc | grep ^[^#] [General] ConfigVersion=2.3 StaticServers=:0 ReserveServers=:1,:2,:3 ServerVTs=-7 ConsoleTTYs=tty1,tty2,tty3,tty4,tty5,tty6 PidFile=/var/run/kdm.pid [Xdmcp] Enable=true Willing=/etc/kde3/kdm/Xwilling [Shutdown] [X-*-Core] Setup=/etc/kde3/kdm/Xsetup Startup=/etc/kde3/kdm/Xstartup Reset=/etc/kde3/kdm/Xreset Session=/etc/kde3/kdm/Xsession AllowRootLogin=false AllowNullPasswd=false AllowShutdown=Root ClientLogFile=.xsession-errors-%s [X-*-Greeter] LogoArea=Logo LogoPixmap=/usr/share/apps/kdm/pics/kdelogo.png AntiAliasing=true MinShowUID=1000 MaxShowUID=2 Preloader=/usr/bin/preloadkde Theme=@@@ToBeReplacedByDesktopBase@@@ [X-:*-Core] ServerCmd=/usr/bin/X -br ServerArgsLocal=-nolisten tcp AllowNullPasswd=true AllowShutdown=All [X-:*-Greeter] PreselectUser=Previous FocusPasswd=true LoginMode=DefaultLocal AllowClose=true [X-:0-Core] ClientLogFile=.xsession-errors [X-:0-Greeter] > Restart kdm at this point. I verified the settings you mentioned, and all were correct. I restarted kdm just to ensure that I hadn't neglected to restart it after changing one of the above when I was doing the initial configuration. No change. > Make sure you backup kdmrc before making any changes so you can rollback > if you break it. > > One more thing: There is a reported but unfixded bug in kdm in > Debian/Ubuntu going back a long way which is causing some xdmcp > configurations to fail when they really are ok. If you look in your logs > you'll see reports of kdm_greet getting memory corruption if you are > getting this problem. As a result of this problem I recently migrated a > bunch of thin client servers to use gdm instead of kdm. You didn't specify which log but I didn't find any such errors in either kdm.log or Xorg.0.log, nor did I find any other related errors in the log. Maybe I'll try switching to xdm just to see. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP
On Sat, 28 Apr 2007, Daniel D Jones wrote: Running unstable. Trying to get XDMCP working via KDM. On the local host, everything works. KDM gives me a graphical login prompt, and KDE loads when I log in. From a remote machine, however, I get what appears to be a pure X session with no Windows manager running. I get the hollow X cursor, and am able to move it with the mouse. However, neither left nor right clicks do any thing - no menu or anything. Clicking and dragging doesn't generate a dotted outline selection. No key presses appear to do anything. Not sure where to go from here. Hints and suggestions welcome. Checkout /etc/kde3/kdem/Xaccess to see what sorts of xdmcp access you are allowing. At the least you want to offer: * #any host can get a login window You may also want to allow: * CHOOSER BROADCAST #any indirect host can get a chooser Also you need to enable xdmcp in kdmrc: # Whether KDM should listen to incoming XDMCP requests. # Default is true Enable=true Restart kdm at this point. Make sure you backup kdmrc before making any changes so you can rollback if you break it. One more thing: There is a reported but unfixded bug in kdm in Debian/Ubuntu going back a long way which is causing some xdmcp configurations to fail when they really are ok. If you look in your logs you'll see reports of kdm_greet getting memory corruption if you are getting this problem. As a result of this problem I recently migrated a bunch of thin client servers to use gdm instead of kdm. Cheers, Rob -- Robert Brockway B.Sc.Phone: +1-905-821-2327 Senior Technical Consultant Urgent Support: +1-416-669-3073 OpenTrend Solutions Ltd Email: [EMAIL PROTECTED] Web:www.opentrend.net Contributing Member of Software in the Public Interest -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xdmcp & Xwilling problems
Solved, at last! I just added a one-character-line made of an '*' to Xaccess file /etc/kde3/kdm Ciao Vittorio [EMAIL PROTECTED] [debian-user] <04/01/04 16:07 +0100>: > I'm trying ** for my first time ** to set up a simple X server communications > between a portable (PC1) and a desktop PC (PC2), connected thorugh eth0, BOTH > using debian testing and kde 3.1.4. > > In a nutshell I want to work on the desktop PC monitor, keyboard & mouse > watching the portable screen through the desktop monitor. > > > I have the following in BOTH kdmrc > > [Xdmcp] > Enable=true > Willing=/etc/kde3/kdm/Xwilling > > Issuing the command > > X -query PC1 :1 > > > (PC1 & PC2 are resolved in /etc/hosts and the th0 conenctions works correctly) > > The following **intricated** diagnostics comes up > > > (==) Log file: "/var/log/XFree86.1.log", Time: Sat Jan 3 14:10:05 2004 > > (==) Using config file: "/etc/X11/XF86Config-4" > > Skipping "/usr/X11R6/lib/modules/extensions/libGLcore.a:debug_xform.o": No > symbols found > > Skipping "/usr/X11R6/lib/modules/fonts/libspeedo.a:spencode.o": No symbols found > > (EE) MGA: Failed to load module "mga_hal" (module does not exist, 0) > > (WW) MGA(0): Failed to set up write-combining range (0x4100,0x100) > > (EE) MGA(0): [drm] DRIScreenInit failed. Disabling DRI. > > > > Fatal server error: > > XDMCP fatal error: Manager unwilling Host unwilling > > > > > What shall I do? > > Vittorio > > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] > signature.asc Description: Digital signature
Re: XDMCP and client requirements
On Fri, Mar 07, 2003 at 02:52:44PM -0500, Bob Paige wrote: > What about running X locally and starting the window manager remotely? Doable, though I can't tell you offhand how to get the window manager to run remotely, since I don't recall where it's started from. > 1. less sensitive to NIC hiccups; assuming my NIC is being flaky, I > never noticed before when running locally-hosted applications, so I > would think that the connection would be re-established before a TCP > timeout (wouldn't it?) > 2. window manager would present a list of apps installed on the server > (not the client) Both make sense to me. > Of course, the biggest disadvantage is starting the whole thing up > because it would require a manual step to go to connect to the server > and start the window manager, but I might be able to script that. No manual intervention needed. Create an ssh keypair with a null passphrase (so ssh will connect without requiring a password) and replace the standard window manager invokation with `ssh -X server /path/to/windowmanager`. Simple as that. -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP and client requirements
Dave Sherohman wrote: On Fri, Mar 07, 2003 at 09:19:04AM -0500, Bob Paige wrote: Another variable, just in case it will shed any light: I'm using a USB ethernet adapter (Linksys USB100M; very small). I've heard in the past of problems with USB ethernet adapters disconnecting and causing problems, but even when I was running the locally installed image it never froze like this. My luck with USB NICs has been pretty bad as well. Any chance of going to a more reliable connection? Keep in mind that with XDMCP, the display is being managed by a remote machine. If you lose contact with that machine (like, say, because of a flaky NIC), would you not expect the terminal to appear to have locked up? It may be running fine itself, but if it can't send input to the XDMCP server or get display updates back... What about running X locally and starting the window manager remotely? I _think_ the advantages would be: 1. less sensitive to NIC hiccups; assuming my NIC is being flaky, I never noticed before when running locally-hosted applications, so I would think that the connection would be re-established before a TCP timeout (wouldn't it?) 2. window manager would present a list of apps installed on the server (not the client) Of course, the biggest disadvantage is starting the whole thing up because it would require a manual step to go to connect to the server and start the window manager, but I might be able to script that. Also, since it is running at home (behind a NAT box) I'm not so concerned about being hacked. -- Bobman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP and client requirements
On Fri, Mar 07, 2003 at 09:33:18AM -0500, Bob Paige wrote: > Another possibility I've considered would be to not use XDMCP but > instead NFS mount everything and invoke it from the client. Yeah, that works pretty well, provided the client's RAM and CPU are up to the task. > I'm not > concerned about NFS security issues because this is just in my house. XDMCP is roughly as secure as NFS (and arguably less secure), given that it's a plain-text protocol which, among other things, asks for your password when you log in, then sends it across the network. > The only way I can think of doing this would be to start X locally, open > an xterm, log into the server, and run apps from there. > The display would be the client, but the CPU would be the server's. If you're NFS mounting everything an running ot on the client, then you're using the client's CPU. If you want to use the server's CPU, you would ssh to the server (with X tunnelling enabled) and use ssh to tell the server to run it and display on the client's screen. -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP and client requirements
On Fri, Mar 07, 2003 at 09:19:04AM -0500, Bob Paige wrote: > Another variable, just in case it will shed any light: I'm using a USB > ethernet adapter (Linksys USB100M; very small). I've heard in the past > of problems with USB ethernet adapters disconnecting and causing > problems, but even when I was running the locally installed image it > never froze like this. My luck with USB NICs has been pretty bad as well. Any chance of going to a more reliable connection? Keep in mind that with XDMCP, the display is being managed by a remote machine. If you lose contact with that machine (like, say, because of a flaky NIC), would you not expect the terminal to appear to have locked up? It may be running fine itself, but if it can't send input to the XDMCP server or get display updates back... -- The freedoms that we enjoy presently are the most important victories of the White Hats over the past several millennia, and it is vitally important that we don't give them up now, only because we are frightened. - Eolake Stobblehouse (http://stobblehouse.com/text/battle.html) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP and client requirements
Bob Paige <[EMAIL PROTECTED]> writes: > Here's a related question: Once you are running an XDMCP session on > the client, is there any way to invoke an executable on the client > machine? Connect to the Xterminal from your session host. Export a DISPLAY variable and then merge your xauth token from the session host into the Xterminals ~/.Xauthority file. Here are some details: You are sitting at Xterminal logged into session_host. session_host$ ssh Xterminal Xterminal$ export DISPLAY=Xterminal:0 Make sure that the DISPLAY vars value matches the FQDN listed by `xauth list' on the session host. I don't let my Xterminal ssh to my session host so I do the rest from the session_host, you could do it before ssh'ing to the Xterminal if tha suits you better or allow ssh to the session host. session_host$ xauth extract - $DISPLAY | ssh Xterminal xauth merge - Then you can start xclients on Xterminal and have them make use of the X server running locally. hth, jereme -- +--+ Jereme Corrado <[EMAIL PROTECTED]> System Administrator Restorative Management Corp. gpg: 1024D/9C39E1F0 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP and client requirements
Here's a related question: Once you are running an XDMCP session on the client, is there any way to invoke an executable on the client machine? Specifically, I want to be able to turn off the screen on the client machine, which can be accomplished by running a special executable on the client. The image I am running locally (based on Midori) came with IceWM pre-configured to run this executable when the user hit the 'power' switch on the keyboard. Makes it behave more like an appliance if you have 'instant-on' and 'instant-off' (so to speak). Another possibility I've considered would be to not use XDMCP but instead NFS mount everything and invoke it from the client. I'm not concerned about NFS security issues because this is just in my house. The only way I can think of doing this would be to start X locally, open an xterm, log into the server, and run apps from there. The display would be the client, but the CPU would be the server's. Any better ways? The main reason I'm considering some workaround is because I'm assuming the problem has to be with the XDMCP connection. -- Bobman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP and client requirements
Rob Weir wrote: Could you setup the box to log to another machine using syslog-over-TCP? This'd tell you if/when the kernel goes nuts. Also, recent 2.4 kernels (at least) start nuking things when memory gets tight. That said, 32MB should be enough to run an X server...that's more RAM than most Unix workstations wuold have had 15 years ago. I *think* it's possible to run swap over NFS or such, but I'd say it'd be pretty hacky, at best :) I've done another experiment: I switched to using IceWM instead of KDE. I thought I had the problem licked last night, but when I came back to the machine this morning, it was frozen. All I had going was the IceWM desktop. Another variable, just in case it will shed any light: I'm using a USB ethernet adapter (Linksys USB100M; very small). I've heard in the past of problems with USB ethernet adapters disconnecting and causing problems, but even when I was running the locally installed image it never froze like this. -- Bobman -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP and client requirements
On Thu, Mar 06, 2003 at 05:18:58PM -0500, Bob Paige wrote: > I am trying to set up a XDMCP server and client. The client is a hacked > Compaq Internet Appliance with 32MB RAM and an on-board flash disk > holding the Linux image. > > Problem is, about 45-seconds into the session, the client freezes. > > Could it be that the client doesn't have enough RAM, and crashes? > > I've accomplished pretty-much the same thing using VNC instead of XDMCP, > but XDMCP is much more responsive for me, so I'd like to try that. > > Thoughts? Could you setup the box to log to another machine using syslog-over-TCP? This'd tell you if/when the kernel goes nuts. Also, recent 2.4 kernels (at least) start nuking things when memory gets tight. That said, 32MB should be enough to run an X server...that's more RAM than most Unix workstations wuold have had 15 years ago. I *think* it's possible to run swap over NFS or such, but I'd say it'd be pretty hacky, at best :) -- Rob Weir <[EMAIL PROTECTED]>http://ertius.org/ pgp0.pgp Description: PGP signature
Re: xdmcp and gdm -- missing something ?
David Woyciesjes wrote: -SNIP- < Hmmm... this is the kind of info I've been waiting for. But one question. On my SUn Ultra1, running Solaris 9, the login box comes up, to login locally, and there is a menu option to flip to a chooser to login to a remote machine. I can login to my Debian/x86 box fromt there, or login locally to Solaris. Is there a way to get this same option in gdm/xdm on a Debian/x86 box? -- ---Dave Woyciesjes ---ICQ# 905818 As one who has only fooled around with second-hand or junked parts, I have never experienced any SUN equipment or Solaris OS... they just are not laying around the junk yards that I frequent . I can visualize what you are describing, and it sounds like it might be a useful "feature". The closest approximation I can suggest is to set up GDM for the "chooser" mode. I can login to my local machine just as well as any other machine running xdmcp on my LAN. For practical matters, to suit my tastes here, I usually boot up to the "normal" GDM login screen on F7 then start up a "chooser" session on F8 as I described before whenever I need it. I can switch between the two by (ctrl-alt-F7 <--> (ctrl-alt-F8). My reason for this is that I do a significant amount of re-booting (experimenting) of my local machine and I like to have the ability to re-boot from the GDM login screen. You can configure GDM to do this via the "System" option. I haven't yet found a way to do this "shortcut" from the Chooser screen. I have to exit to a terminal session (ctrl-alt-F2) then shutdown/reboot from the terminal prompt. Not a big deal... I just prefer to use the mouse to click on the normal GDM "system" then "reboot". The drawback is that I currently have to manually start the "chooser" session each time I reboot. I am probably not saving anything by doing it this way. BTW, You can get just about the same functionality using VNC. Its setup is different, and it seems a bit more awkward for me to use. I have always had a tough time getting the display sizes and depths just right for my tastes. One advantage of VNC that I have found is that you can startup sessions to different machines on different "pager" windows. You can then switch between machines via the "pager" in GNOME or KDE. You can also use ssh to run specific X apps on a remote machine and have the display local. Each method has its strengths and drawbacks... Cheers, -Don Spoon- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xdmcp and gdm -- missing something ?
Donald Spoon wrote: > > J.F.Gratton wrote: > > Don, > > > > Thank you so much, this is exactly what I looked for. I am stuck in the > > same position as you are, trying to automate the procedure. A temporary > > hack for now is to add the line you mentionned (X :1 vt8 etc etc) into > > my /etc/init.d/bootmisc.sh. This is ugly, but hey.. it works :) > > > > Hmm... have to give that a try. Thanks! I could get GDM to start in > either "mode" individually, but not both. It seem like it "should", but > if I had both server lines defined in /etc/gdm/gdm.conf the computer > would go into a loop of some sort and eventually kick me out to the > command line with neither one started. > > > I tried to solve it somehow, it didn't work (got a flickering screen for > > all my endeavours).. Here's what I added to /etc/X11/gdm/gdm.conf; I've > > commented the lines since for now it doesn't work. helsinki is the > > hostname on that computer. That reminds me... in your example, -indirect > > legolas legolas was the local host, right ? > > > No, not usually. Let me explain that a bit... Here are the computer > names and their functions on my LAN: > legolas ---> gateway, IPMasq, > bilbo ---> time server, mail server, workstation (old DEC Alpha) > gandalf ---> main workstation, LAN print-server (my machine) > gimli ---> secondary workstation (son's machine) > elrond ---> secondary workstation (wife's machine) > > All machines are using gdm and are setup to honor "indirect" xdmcp > request as per the [xdmcp] section of /etc/gdm/gdm.conf. I can actually > use any one of them, including the "localhost" in the "-indirect > [hostname]" part of the line and get it to work. > > > #[server-Chooser] > > #name=Chooser > > #command=/usr/bin/X11/X -indirect helsinki > > #flexible=true > > > > [servers] > > 0=Standard vt7 > > #1=Chooser vt8 > > > I wonder if our "problem" isn't caused by looking at the local machine > for a "chooser" when it is still trying to start X for vt7??. Maybe the > "chooser" function isn't working at the time we are trying to start > vt8. I wonder if setting the "-indirect..." line to an external machine > that already has X running and offering "chooser" services would work?? > > BTW, I found that understanding how it is done in XDM, then applying > that knowledge to GDM was quite helpful to me. There are several > different places in XDM that have to be modified to get xdmcp working, > but you can do it all in /etc/gdm/gdm.conf when using GDM. The KDM > setup is almost identical to the XDM setup... or used to be. I have not > looked at KDM in quite a while. Here is a good HOWTO on setting up XDM > in a college LAB setting that I found helpful: > http://www.linuxgazette.com/issue27/kaszeta.html > > The XDMCP HOWTO at the Linux Documentation Project was quite useful too, > but you had to do some mental conversions to adapt it to Debian. The > above link was mainly about XDMCP on Debian, although on an older > version of X that had the files located in different places. > > Guess I have some thinking and experimenting to do > > Cheers, > -Don Spoon- Hmmm... this is the kind of info I've been waiting for. But one question. On my SUn Ultra1, running Solaris 9, the login box comes up, to login locally, and there is a menu option to flip to a chooser to login to a remote machine. I can login to my Debian/x86 box fromt there, or login locally to Solaris. Is there a way to get this same option in gdm/xdm on a Debian/x86 box? -- ---Dave Woyciesjes ---ICQ# 905818 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xdmcp and gdm -- missing something ?
J.F.Gratton wrote: Don, Thank you so much, this is exactly what I looked for. I am stuck in the same position as you are, trying to automate the procedure. A temporary hack for now is to add the line you mentionned (X :1 vt8 etc etc) into my /etc/init.d/bootmisc.sh. This is ugly, but hey.. it works :) Hmm... have to give that a try. Thanks! I could get GDM to start in either "mode" individually, but not both. It seem like it "should", but if I had both server lines defined in /etc/gdm/gdm.conf the computer would go into a loop of some sort and eventually kick me out to the command line with neither one started. I tried to solve it somehow, it didn't work (got a flickering screen for all my endeavours).. Here's what I added to /etc/X11/gdm/gdm.conf; I've commented the lines since for now it doesn't work. helsinki is the hostname on that computer. That reminds me... in your example, -indirect legolas legolas was the local host, right ? No, not usually. Let me explain that a bit... Here are the computer names and their functions on my LAN: legolas ---> gateway, IPMasq, bilbo ---> time server, mail server, workstation (old DEC Alpha) gandalf ---> main workstation, LAN print-server (my machine) gimli ---> secondary workstation (son's machine) elrond ---> secondary workstation (wife's machine) All machines are using gdm and are setup to honor "indirect" xdmcp request as per the [xdmcp] section of /etc/gdm/gdm.conf. I can actually use any one of them, including the "localhost" in the "-indirect [hostname]" part of the line and get it to work. #[server-Chooser] #name=Chooser #command=/usr/bin/X11/X -indirect helsinki #flexible=true [servers] 0=Standard vt7 #1=Chooser vt8 I wonder if our "problem" isn't caused by looking at the local machine for a "chooser" when it is still trying to start X for vt7??. Maybe the "chooser" function isn't working at the time we are trying to start vt8. I wonder if setting the "-indirect..." line to an external machine that already has X running and offering "chooser" services would work?? BTW, I found that understanding how it is done in XDM, then applying that knowledge to GDM was quite helpful to me. There are several different places in XDM that have to be modified to get xdmcp working, but you can do it all in /etc/gdm/gdm.conf when using GDM. The KDM setup is almost identical to the XDM setup... or used to be. I have not looked at KDM in quite a while. Here is a good HOWTO on setting up XDM in a college LAB setting that I found helpful: http://www.linuxgazette.com/issue27/kaszeta.html The XDMCP HOWTO at the Linux Documentation Project was quite useful too, but you had to do some mental conversions to adapt it to Debian. The above link was mainly about XDMCP on Debian, although on an older version of X that had the files located in different places. Guess I have some thinking and experimenting to do Cheers, -Don Spoon- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xdmcp and gdm -- missing something ?
Don, Thank you so much, this is exactly what I looked for. I am stuck in the same position as you are, trying to automate the procedure. A temporary hack for now is to add the line you mentionned (X :1 vt8 etc etc) into my /etc/init.d/bootmisc.sh. This is ugly, but hey.. it works :) I tried to solve it somehow, it didn't work (got a flickering screen for all my endeavours).. Here's what I added to /etc/X11/gdm/gdm.conf; I've commented the lines since for now it doesn't work. helsinki is the hostname on that computer. That reminds me... in your example, -indirect legolas legolas was the local host, right ? #[server-Chooser] #name=Chooser #command=/usr/bin/X11/X -indirect helsinki #flexible=true [servers] 0=Standard vt7 #1=Chooser vt8 Many thanks, Don ! Jeff On Sat, 2003-02-15 at 19:11, Donald Spoon wrote: > J.F.Gratton wrote: > > Hello all, > > > > I have two computers (networked, 'f course) both with the same setup, > > gdm + gnome 2.2 latest versions (I apt-get dist-upgrade every day on the > > unstable branch). > > > > The way I understood the Chooser is that I'd be able to get the gdm > > login screen of PC #2 on PC #1 . > > > > I've found an (outdated) xdmcp howto, but it mixed gdm, kdm and xdm in > > the same howto, and the end result is that I' don't get that expected > > result. > > > > Is there anyone kind enough to explain what to do (if it IS possible, in > > the first place !), which config files to modify, etc ? > > > > Many, many thanks ! > > > > Jeff > > > > > > I am using the GDM from Woody (GNOME 1.4??) exclusively on my 5-computer > LAN, and can do what you are trying to do between all 5 computers. > Maybe the outline of my changes will help you figure out your problem. > BTW, you should make the changes on all computers you want to use xdmcp. > > 1. Changing X to do xdmcp: You have to edit the > /etc/X11/xinit/xserverrc file and remove the "- nolisten tcp" at the end > of the line. Dunno if this is needed for GDM or not, but it definately > is needed for XDM. > > 2. Changing GDM for xdmcp: (Note: All edits are on /etc/gdm/gdm.conf) > > a. In the [xdmcp] section set "Enable = true". All other default > options were OK. > > b. In either the [server-Standard] or [server] section (I forget which > one had it) remove the "-nolisten tcp" part. Leave the rest of the line > as it is. > > 3. When starting up the chooser, I have to manually start a new X > session by going to a terminal (ctrl-alt-F1), logging in as root, and > typing in the following line: "X :1 vt8 -indirect legolas". (legolas is > one of my computers setup to use xdmcp and honor indirect queries... you > should substitute one of your computer's names here). > > This will start a new X session and bring up the chooser screen. You can > go back to your original screen by doing a ctrl-alt-F7. You now can > switch between session :0 (vt7) and session :1 (vt8) with ctrl-alt-F7 > and ctrl-alt-F8. > > There should be some way to automate this, but I haven't figured it out > yet. I am still experimenting > > HTH, > > Cheers, > -Don Spoon- > -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: xdmcp and gdm -- missing something ?
J.F.Gratton wrote: Hello all, I have two computers (networked, 'f course) both with the same setup, gdm + gnome 2.2 latest versions (I apt-get dist-upgrade every day on the unstable branch). The way I understood the Chooser is that I'd be able to get the gdm login screen of PC #2 on PC #1 . I've found an (outdated) xdmcp howto, but it mixed gdm, kdm and xdm in the same howto, and the end result is that I' don't get that expected result. Is there anyone kind enough to explain what to do (if it IS possible, in the first place !), which config files to modify, etc ? Many, many thanks ! Jeff I am using the GDM from Woody (GNOME 1.4??) exclusively on my 5-computer LAN, and can do what you are trying to do between all 5 computers. Maybe the outline of my changes will help you figure out your problem. BTW, you should make the changes on all computers you want to use xdmcp. 1. Changing X to do xdmcp: You have to edit the /etc/X11/xinit/xserverrc file and remove the "- nolisten tcp" at the end of the line. Dunno if this is needed for GDM or not, but it definately is needed for XDM. 2. Changing GDM for xdmcp: (Note: All edits are on /etc/gdm/gdm.conf) a. In the [xdmcp] section set "Enable = true". All other default options were OK. b. In either the [server-Standard] or [server] section (I forget which one had it) remove the "-nolisten tcp" part. Leave the rest of the line as it is. 3. When starting up the chooser, I have to manually start a new X session by going to a terminal (ctrl-alt-F1), logging in as root, and typing in the following line: "X :1 vt8 -indirect legolas". (legolas is one of my computers setup to use xdmcp and honor indirect queries... you should substitute one of your computer's names here). This will start a new X session and bring up the chooser screen. You can go back to your original screen by doing a ctrl-alt-F7. You now can switch between session :0 (vt7) and session :1 (vt8) with ctrl-alt-F7 and ctrl-alt-F8. There should be some way to automate this, but I haven't figured it out yet. I am still experimenting HTH, Cheers, -Don Spoon- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: XDMCP Howto? [SOLVED]
Thanks to everyone for your help. I now have it working exactly as I
wanted. For those who care, this is what I did to each of the machines.
Commented out the servers in the [servers] section of gdm.conf.
Added
x5:5:respawn:/usr/bin/X11/X -indirect localhost > /var/log/XFree86.log
2>&1
to /etc/inittab and set my default runlevel to 5
(I'm a little unsure of the syntax of this, but it seems to work
correctly). I chose to enable xdmcp on all of the machines and have
them all query localhost. If I had them all just querying one machine
and that machine was down I wouldn't have X anywhere, that wouldn't be
any fun :).
Now whenever I boot any of my linux boxes it gives me the gdmchooser to
decide which machine to log into, once I choose a machine I am then
given the standard gdm login screen (except if I choose the Indy, which
gives me the standard xdm login screen...wish I could get that one to
give me clogin, but that's a question for an IRIX list).
Now I'd like to add my laptop into the mix, but my concern is that my
laptop is also connected to the internet. Is there something I can put
into /etc/hosts.{allow|deny} that will let me do this safely? I can't
just blindly deny everything not on my network, since there are some
services that I do need to be able to reach from the internet.
By the way, the Indigo Magic desktop looks GREAT on a 22" monitor :). I
just wish that 5dwm.org had released source code so that I could fix
some of the more glaring errors and use it as my desktop on all of my
machines. Better yet, having SGI open source 4Dwm, toolchest, and fm
would truly make me happy. Ah well, such is life.
Cheers,
Caleb
signature.asc
Description: This is a digitally signed message part
Re: XDMCP Howto?
Hans Ekbrand <[EMAIL PROTECTED]> wrote: This might be trivial to you, but have you tried: ~>X :1 vt9 -query foo THANK YOU VERY MUCH! No, I hadn't tried it recently, and yes it works like a charm!! Combined with my other recent "discovery" I now almost have exactly what I would like!! Thanks again! Cheers, -Don Spoon-
Re: XDMCP Howto?
Donald Spoon wrote: > --snip-- < This is a KLUDGE and very awkward to use! If you know how to get another X-session going at the same time, I would appreciate knowing it. One of the problems with the above is that the [local computer] doesn't have GDM/XDM running so it cannot participate in the XDMCP network except as a "dumb" terminal. Once again, I KNOW you can have GDM running without bringing up the login screen, but I don't know how to do it. I have done it using XDM in XFree86 version 3.3.6, but the 4.1 version has me stumped... all my familiar old files have been changed :( Sorry to reply to my own message, but I just discovered how to have GDM running BUT not have the x-server started. This will boot you into a command prompt with GDM running where you can type in the command "X -indirect [lan computer with "chooser" enabled]. You can even point it at the "local" computer if you have gdmchooser enabled there. You can now choose to login to your local computer if you want! 1. Boot up and go to another terminal (ctrl-alt-F2) 2. login as root and stop GDM (/etc/init.d/gdm stop) 3. Using the editor of your choice edit the /etc/gdm/gdm.conf file in the [servers] section and comment out the line that reads something like this "0=Standard vt7". In fact comment out ALL of them listed here. 4. Restart GDM (/etc/init.d/gdm start). You should now still be at a command prompt with a GDM process listed in "ps aux". 5. Start up X with an "indirect" parameter, i.e. "X -indirect gandalf", where gandalf is the name of my "local" computer. This should bring up the gdmchooser screen with ALL the XDMCP computers on the LAN listed, including the local one. You should be able to connect to any one listed there. If all this works, you can now automate it by creating an initscript that issues this command and starts AFTER the GDM initscript per the suggestions in the linuxgazette article mentioned in my previous message. You will have to go to one of the tty terminals to shut the system down in this config. The only options on the individual login screens (in addition to the normal Xsession selections) are to either "connect" or "disconnect". The "disconnect" option will cycle you back to the chooser screen. Cheers, -Don Spoon-
Re: XDMCP Howto?
On Thu, Mar 07, 2002 at 01:37:02PM -0600, Donald R. Spoon wrote: > several years at random times. I have not been able to find the "magic" > to get several X-servers running on different terminals (vt7, vt8, etc) > yet, so the steps below are restricted to a machine that has only ONE > X-server session capability. I know it can be done, but just don't know > how...:( This might be trivial to you, but have you tried: ~>X :1 vt9 -query foo -- Note that I use Debian version 3.0 Linux emac140 2.4.17 #1 s?n feb 10 20:21:22 CET 2002 i686 unknown Hans Ekbrand pgpqzOCUM09co.pgp Description: PGP signature
Re: XDMCP Howto?
Caleb Shay <[EMAIL PROTECTED]> wrote: Here's one for the X-perts. I have 3 machines on a private network. 2 linux boxes using gdm and 1 SGI using xdm/clogin. I would like to be able to log into any of the boxes from any one of the other boxes. This seemed like a perfect time for me to play with XDMCP. After all, isn't network transparency supposed to be one of the big selling points of X11? So, after much fruitless searching for info on XDMCP and the configuration of xdm and gdm, all I could come up with was that I needed to enable xdmcp in my gdm.conf files (done), enable broadcast in same (done) and also enable xdmcp broadcasts on all boxes (done). As far as I can tell from the man pages I should get (gdm)chooser popping up automagically on the all 3. Unfortunately, nothing like that happens. I just have my normal login screens. Anybody have any hints for me? Cheers, Caleb I am NOT an "X-pert", but I have been playing around with XDMCP for several years at random times. I have not been able to find the "magic" to get several X-servers running on different terminals (vt7, vt8, etc) yet, so the steps below are restricted to a machine that has only ONE X-server session capability. I know it can be done, but just don't know how...:( GDM and XDM are configured differently for XDMCP. KDM is quite similar to XDM, but ALL the config for GDM is done in /etc/gdm/gdm.conf. If you have a "mixed" network using any/all of these, you might want to refer to the following sites for some insights on how to get XDM or KDM going: http://www.linuxdoc.org/HOWTO/XDMCP-HOWTO/index.html http://www.linuxgazette.com/issue27/kaszeta.html I found the second reference a bit more enlightening since it uses Debian and XDM and provides some very concrete steps to follow. The normal GDM login screen (or XDM or KDM) and the "Chooser" screen cannot run at the same time if you have only a single X-server session capability. This means you will have to either "kill" the GDM process or "stop" it with "/etc/init.d/gdm stop" The bottom line is to get to a command prompt WITHOUT a X-server running. Once you are at the command prompt without any X-server running you can then "test" your system out to see if the other comuters are setup correctly. I have found the following commands QUITE useful: 1. "X" (or startx) will start an X-session on the local computer. 2. "X -quiet -query [remote computer} should bring up the login-screen of the remote computer... the GDM login screen if it uses GDM. 3. "X -indirect [remote computer] should bring up the "chooser" screen of the remote computer. Note.. you only have to have ONE computer enabled to provide a "chooser" function for the entire network. The gdmchooser DOES work! If you have problems acessing remote computers, check both the [local compter] and [remote computer] /etc/X11/xinit/xserverrc file and make sure that the "nolisten -tcp" part is removed. You should also probably do this in the server section of /etc/gdm/gdm.conf too. These entries are there by default for security reasons. Once you test out your system and can connect to the various computers on the network, you can make some "permanant" changes in your initscripts. You should disable the /etc/init.d/gdm initscript. I do this by placing a "exit 0" as the second line. This preserves the initscript for future use. You also can create a NEW initscript that will implement either option 2 or 3 above. A sample initscript is included in the linuxgazette reference above. This is a KLUDGE and very awkward to use! If you know how to get another X-session going at the same time, I would appreciate knowing it. One of the problems with the above is that the [local computer] doesn't have GDM/XDM running so it cannot participate in the XDMCP network except as a "dumb" terminal. Once again, I KNOW you can have GDM running without bringing up the login screen, but I don't know how to do it. I have done it using XDM in XFree86 version 3.3.6, but the 4.1 version has me stumped... all my familiar old files have been changed :( HTH, -Don Spoon-
Re: XDMCP Howto?
Caleb Shay wrote: xdmcp broadcasts on all boxes (done). As far as I can tell from the man pages I should get (gdm)chooser popping up automagically on the all 3. Unfortunately, nothing like that happens. I just have my normal login screens. Anybody have any hints for me? gdmchooser is supposed to replace gdm; so that when you are about to login, you'd face a list of hosts to login to. Unfortunately, AFAIK, the program is not yet ready. Oki
Re: XDMCP Howto?
On Thu, 2002-03-07 at 13:44, Caleb Shay wrote: > Here's one for the X-perts. > > I have 3 machines on a private network. 2 linux boxes using gdm and 1 > SGI using xdm/clogin. I would like to be able to log into any of the > boxes from any one of the other boxes. This seemed like a perfect time > for me to play with XDMCP. After all, isn't network transparency > supposed to be one of the big selling points of X11? So, after much > fruitless searching for info on XDMCP and the configuration of xdm and > gdm, all I could come up with was that I needed to enable xdmcp in my > gdm.conf files (done), enable broadcast in same (done) and also enable > xdmcp broadcasts on all boxes (done). As far as I can tell from the man > pages I should get (gdm)chooser popping up automagically on the all 3. > Unfortunately, nothing like that happens. I just have my normal login > screens. Anybody have any hints for me? I set this up ages ago and vaguelly remember. Its all in the Thin-Client HOWTO on linuxdoc.org. As well as setting up XDMCP on your display managers (gdm/xdm) you need to start an X server on a free VT with it set to look for the XDMCP server. Have a look at the startx script which calls the X programme. Doing it by hand you may do something like X :1 -broadcast or specify it with something like... X :1 vt09 -query xdcmphost.domain.com This should start up X and greet you with the display manager screen from the remote host. X -h for more info Kind Regards Crispin Wellington
Re: XDMCP broken after X upgrade
Hi, On Wed, Mar 01, 2000 at 07:46:42PM -0700, Jason Gunthorpe wrote: > Edit things in /etc/X11/xdm - I think it was pretty obvois IIRC. Oddly, it > was decided that xdm is some kind of security risk - I personally don't > see why.. > > Jason The config file in question is /etc/X11/xdm/Xaccess. BTW, I only allow xdm logins from within my LAN, so I guess the security risk is minimal Thanks. -- David Karlin [EMAIL PROTECTED] Powered by Debian GNU/Linux
Re: XDMCP broken after X upgrade
On Wed, 1 Mar 2000, David Karlin wrote: > I'm guessing that some new configuration file might have been inserted > during the X upgrade. Am I on the right track? Has anyone experienced > this, or know how to fix it? Edit things in /etc/X11/xdm - I think it was pretty obvois IIRC. Oddly, it was decided that xdm is some kind of security risk - I personally don't see why.. Jason
Re: XDMCP broadcasts on all machines
On Tue, Aug 31, 1999 at 09:20:42AM -0400, Aleksandra Bytnerowicz wrote > Igor Mozetic, the Debian List and Brandon Harris: > > I came across a post for XDMCP and broadcast posting to the debian lists > + in November 1998. SPecifically, the message which was written was: > > http://www.debian.org/Lists-Archives/debian-user-9811/msg00336.html > > I have a subnet of 6 Linux boxes and tried to achieve what you mentioned > +, that a XDMCP chooser pops up in each monitor querying for ITSELF and > +BROADCASTING to other machines. By opening up the Xaccess file: > > *.domain.com > *.domain.com CHOOSER BROADCAST > > and commenting the Xservers line: > > #:0 local /usr/X11R6/bin/X > > makes the local machine act like an X terminal > > and running X -indirect some_host.domain.com I can see the other machine > +s via broadcast, but of course cannot see the XDM for my own machine. > > In effect, I am trying to get each machine to show a CHOOSER with ITSELF > + and all the other hosts on the subnet which are collected via BROADCAS > +T, and let me select my choice of machine to login to. > > Any ideas? Any suggestions would be appreciated! > I run a one-line script called Xchooser out of inittab: /usr/bin/X11/X -indirect `/bin/hostname --fqdn` &> /var/log/XChooser.errors My Xaccess file contains: *.localnet localhost *.localnet CHOOSER BROADCAST localhost CHOOSER BROADCAST (*.localnet is my local ethernet) and it works for me. I suspect that you either want to use the FQDN for your host as the indirect host rather than localhost, or add entries for localhost to /etc/X11/xdm/Xaccess. I do it this way, as if I do X -indirect localhost I get two entries for the localhost (FQDN and localhost). John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] "Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
Re: XDMCP without xdm?
On Sun, Jun 27, 1999 at 04:14:41PM -0400, Stuart Ballard wrote > Is there any way I can allow remote hosts to access my machine via xdmcp > without running xdm on the machine itself? (running xdm seems to lock > the machine completely on a regular basis). Would running xdm without > managing any local displays solve the locking-up problem? Alternatively, > does anyone have any experience with whether any of the other display > managers (kdm, wdm, gdm, login.app, ...) solve the problem of locking > machines up? Do those provide xdmcp? I have a very similar setup here using Slink (x*_3.3.2.3a-11.deb) with no problems; xdm doesn't manage any displays directly, it just does the XDMCP bit. Perhaps you have other problems, or your xdm is broken? In slink at least, wdm and login.app don't appear to support XDMCP. John P. -- [EMAIL PROTECTED] [EMAIL PROTECTED] "Oh - I - you know - my job is to fear everything." - Bill Gates in Denmark
RE: XDMCP without xdm?
On 27-Jun-99 Stuart Ballard wrote: > Is there any way I can allow remote hosts to access my machine via xdmcp > without running xdm on the machine itself? (running xdm seems to lock > the machine completely on a regular basis). Would running xdm without > managing any local displays solve the locking-up problem? Alternatively, > does anyone have any experience with whether any of the other display > managers (kdm, wdm, gdm, login.app, ...) solve the problem of locking > machines up? Do those provide xdmcp? > kdm, wdm, login.app are all based on xdm so if one does not work, they all should fail. gdm is a complete fresh start so if anything you have a chance there. However xdm should NOT lock your machine. The greatest benefit would be from you tracking down the cause of this. Others may be fighting the same issue.
Re: XDMCP without xdm?
* Stuart Ballard <[EMAIL PROTECTED]>: > Failing all this, is there a way to get a similar effect using startx? > (ie, start an x session but run all programs from another machine). Use ssh! ssh will take care of seting up X-forwarding and setting the DISPLAY variable... On your client use startx with an xterm for your windowmanager. In the xterm ssh to the server and start the windowmanager of your choice from there. Now you're running all programs from your server. I've done this myself some times when the machine I'm at is really slow. I'm sure this could be automated if you use authentication keypairs... Do something like this in .xinitrc or whichever file is used with startx. -.xinitrc-- #if you have any special keybindings you'll want to do; xmodmap .Xmodmaprc #so your keybindings work when you type your password. ssh-add "I contend that we are both atheists. I just believe in one fewer god than you do. When you understand why you dismiss all the other possible gods, you will understand why I dismiss yours." -- Stephen Roberts
