🚀 go-pugleaf

Graham Daveney <graham@daveney.matra.com.au> skrev i artiklen
<63mtgu$2d9$1@daveney.matra.com.au>...
> Hi Guys,
> 
> yesterday I posted a message saying that I have put the following line in
my
> Xsetup_0 file in the /usr/X11R6/lib/X11/xdm directory.
> 
> xlock -nolock -mode forest -inroot &
> 
> Which gave me a nice login screen, but persisted when I started an X
session.
> 
> Even if I tried to "killall xlock" I could not do it as I had logged in
as
> another user, and xlock had been started with uid root.
> 
> After some more searching and reading of the xdm-config file, which went
as
> follows.
> 
> ! The following three resources set up display :0 as the console.
> DisplayManager._0.setup:	/usr/X11R6/lib/X11/xdm/Xsetup_0
> DisplayManager._0.startup:	/usr/X11R6/lib/X11/xdm/GiveConsole
> DisplayManager._0.reset:	/usr/X11R6/lib/X11/xdm/TakeConsole
> 
> So I edited the file GiveConsole and put the following lines.
> 
> killall xlock
> chown $USER /dev/console

That is not a very good thing to do, if you are running multiple X sessions
(remote or on the same machine). Imagine running X with 16bit color (nice
for
netscape), and deciding that you want to play doom (which requires 8bit 
color). What do you do?

1. xlock your current X.
2. start a new one.
3. Log in
4. the xlock you started in 1. is killed.

1 and 2 could be accomplised with something like

xlock &; X -query 127.0.0.1 -bpp 8 &

from an xterm.

Same problem, if you log in, after someone has started xlock on
a remote screen.

Of course, if you are the only one using the machine, and never use the
nice multitasking features, it won't be a problem.

The right thing to do would be to use

xlock -bla -bla bla &
echo 4! >/tmp/xlock:0.pid

and then

kill $(cat /tmp/xlock:0.pid)
> 
> Regards
> Graham
> graham@daveney.matra.com.au
> 

Kent

-- 
Linux 1.0 is out: NT 5.0 is now obsolete