Article View: dc.org.linux-users
Article #3569Re: XDM killclient problem
From: Joseph S. D. Yao
Date: Thu, 30 Nov 1995 00:00
Date: Thu, 30 Nov 1995 00:00
27 lines
1656 bytes
1656 bytes
In article <49kae2$pt7@news.cais.com>, Rusty Waters <ferric@undertow.xanthia.com> wrote: >small problem, probably already covered a million times, but... Actually, fairly original. >as part of my XDM login screen, I display a small oclock. the problem is/was, >it doesnt seem to want to die when xlogin hands off to >$USER/.xinitrc|.xsession. ... > ... this puzzles me, because i thought that xdm/Xsession run programs >ran at root equivalent level. i thought that it should have killed the oclock >with ALL logins, not just under root. Well, no. Consider that Xsession i s your X login session. It runs as "you" (the logged-in user, whoever that might be). You may have to set up a setuid-root program (*shudder*) that runs from /usr/lib/X11/xdm/Xsession and kills the clock. Better yet, since Przemek is EXACTLY RIGHT about super-user (you want as few things to be owned by or be run by the super-user as possible), have both the clock and the kill-clock program run as some other "neutral" user that doesn't have any vital task in the system. -- Joe Yao jsdy@cais.com - Joseph S. D. Yao
Technical Details
Message-ID:
<49l33g$bt3@zippy.cais.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<49kae2$pt7@news.cais.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 11663c,ecf473e340874e61 X-Google-Attributes: gid11663c,public X-Google-Thread: f4bda,ecf473e340874e61 X-Google-Attributes: gidf4bda,public From: jsdy@cais2.cais.com (Joseph S. D. Yao) Subject: Re: XDM killclient problem Date: 1995/11/30 Message-ID: <49l33g$bt3@zippy.cais.net> X-Deja-AN: 120489723 references: <49kae2$pt7@news.cais.com> organization: Hadron, Inc. [Posting from Cap. Area Internet Svcs.] newsgroups: dc.org.linux-users,comp.os.linux.x