public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Pavel Rosenboim <pavelr@coresma.com> To: cygwin-xfree@cygwin.com Subject: Re: XWin works on Win2K but not on some WinXP clients Date: Tue, 11 Nov 2003 16:54:00 -0000 [thread overview] Message-ID: <3FB11450.1040208@coresma.com> (raw) In-Reply-To: <Pine.LNX.4.58.0311111731380.12355@herkules.hrz.tu-chemnitz.de> Alexander Gottwald wrote: > On Tue, 11 Nov 2003, Woellert, Kirk D. wrote: > > > We are not running NAT. All firewalls are turned off completely > (linux and > > Win). We are all on the same network segment, and all have the same > IP scope > > (i.e. 137.x.x.x). > > > > I tried to get debug running as requested but, as a new linux user > its not > > straightforward to figure out how to stop kdm/gdm/xdm or whatever RH9 > uses, > > and restart it again. I looked at the post you cited and searched the > net > > also. "/etc/init.d/xdm stop" returns command not found. I tried several > > iterations but no avail. So finally I did "xdm -debug 10 -no daemon", > got a > > fatal server error, did some grep's and here is the followoing: > > maybe /etc/init.d./gdm stop In RedHat systems xdm/kdm/gdm is started by init (as configured in /etc/inittab) so the only way to stop it is by switching to runlevel 3 - /sbin/init 3 > > > [debug] > > # This will enable debugging into the syslog, usually not neccessary > > # and it creates a LOT of spew of random stuff to the syslog. > However it > > # can be useful in determining when something is going very wrong. > > Enable=false > > Set this to true. Most likely gdm will create a logfile in > /var/log/gdm > > > XFree86.log.1 > > [kdw@gaia log]# cd gdm > > [kdw@gaia gdm]# ls > > :0.log :0.log.1 :0.log.2 :0.log.3 :0.log.4 > > [kdw@gaia gdm]# cat :0.log > > These are all logfiles for the local xserver and do not contain > information for your problem. > > > [kdw@gaia log]# cat kdm.log > > > > Fatal server error: > > Server is already active for display 0 > > If this server is no longer running, remove /tmp/.X0-lock > > and start again. > > This is a normal error. There was already a xserver running on display > 0 (started by gdm) and kdm tried to start another which failed. > > bye > ago > -- > Alexander.Gottwald@s1999.tu-chemnitz.de > http://www.gotti.org ICQ: 126018723 >
next prev parent reply other threads:[~2003-11-11 16:54 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-11-11 15:51 Woellert, Kirk D. 2003-11-11 16:37 ` Alexander Gottwald 2003-11-11 16:54 ` Pavel Rosenboim [this message] 2003-11-12 2:46 ` Willem Riede -- strict thread matches above, loose matches on Subject: below -- 2003-11-14 13:28 Woellert, Kirk D. 2003-11-14 13:48 ` Harold L Hunt II 2003-11-13 23:31 Woellert, Kirk D. 2003-11-13 23:45 ` Harold L Hunt II 2003-11-14 14:39 ` Alexander Gottwald 2003-11-13 13:17 Woellert, Kirk D. 2003-11-13 18:40 ` Harold L Hunt II 2003-11-12 15:01 Woellert, Kirk D. 2003-11-12 15:18 ` Pavel Rosenboim 2003-11-12 15:35 ` Harold L Hunt II 2003-11-11 13:31 Woellert, Kirk D. 2003-11-11 13:53 ` XWin " Harold L Hunt II 2003-11-11 13:58 ` Harold L Hunt II 2003-11-10 19:17 Woellert, Kirk D. 2003-11-10 19:36 ` XWin " Harold L Hunt II 2003-11-09 23:22 kirk woellert 2003-11-10 11:03 ` Alexander Gottwald
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=3FB11450.1040208@coresma.com \ --to=pavelr@coresma.com \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).