From owner-freebsd-questions Sun May 21 6:30:41 2000 Delivered-To: freebsd-questions@freebsd.org Received: from mail.inka.de (quechua.inka.de [212.227.14.2]) by hub.freebsd.org (Postfix) with ESMTP id 7916437B8ED for ; Sun, 21 May 2000 06:30:35 -0700 (PDT) (envelope-from daemon@mips.inka.de) Received: from bigeye.rhein-neckar.de (uucp@) by mail.inka.de with local-bsmtp id 12tVoQ-0000s1-00; Sun, 21 May 2000 15:30:34 +0200 Received: (from daemon@localhost) by bigeye.rhein-neckar.de (8.9.3/8.9.3) id OAA21400 for freebsd-questions@freebsd.org; Sun, 21 May 2000 14:12:19 +0200 (CEST) (envelope-from daemon) From: naddy@mips.inka.de (Christian Weisgerber) Subject: Re: XDM remote only Date: 21 May 2000 14:12:19 +0200 Message-ID: <8g8jr3$ksg$1@bigeye.rhein-neckar.de> References: To: freebsd-questions@freebsd.org Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Lowkrantz, Goran wrote: > The problem: xdm just goes through the motions of starting up and then > exists. Here is the output of -debug 9 > [...] > Nothing left to do, exiting Ah, yes. This can take your sanity. Check the last lines of xdm-config: ! SECURITY: do not listen for XDMCP or Chooser requests ! Comment out this line if you want to manage X terminals with xdm DisplayManager.requestPort: 0 This line forbids xdm to manage remote displays. When you start up xdm in your configuration, it recognizes that indeed nothing is left to do and terminates. There is no error condition. -- Christian "naddy" Weisgerber naddy@mips.inka.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message