From owner-freebsd-questions Thu Mar 30 10: 0:16 2000 Delivered-To: freebsd-questions@freebsd.org Received: from cx344940-a.meta1.la.home.com (cx344940-a.meta1.la.home.com [24.6.21.74]) by hub.freebsd.org (Postfix) with ESMTP id B95EB37BCF9 for ; Thu, 30 Mar 2000 10:00:08 -0800 (PST) (envelope-from conrads@cx344940-a.meta1.la.home.com) Received: (from conrads@localhost) by cx344940-a.meta1.la.home.com (8.9.3/8.9.3) id MAA38954; Thu, 30 Mar 2000 12:00:05 -0600 (CST) (envelope-from conrads) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Thu, 30 Mar 2000 12:00:04 -0600 (CST) Organization: @Home Network From: Conrad Sabatier To: William Melanson Subject: RE: How to stop XDM properly? Cc: freebsd-questions@FreeBSD.ORG Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On 30-Mar-00 William Melanson wrote: > > Sorry about the rather off-topic question. I've been starting XDM via a > startup file in the rc.d directory. As of now the only way I can stop > XDM > is to escape to another available console and kill all XDM associated > processes. Is there a simpler way to stop XDM outside the method I am > currently using? Did I read in a past simular post that the "exec" > command > should preceed the execution of XDM within the XDM/rc.d startup > script? What does adding exec to the script actually do? > > Thanxs much in advance... The reason for using the "exec" command, if you're running xdm from a script, is that it causes the invoked process (xdm, in this case) to *replace* the shell process that calls it, so you're not left with an unnecessary shell process still running in the background. As for the best, most surefire way to kill xdm, "killall xdm" should be the ticket. :-) -- Conrad Sabatier http://members.home.net/conrads/ ICQ# 1147270 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message