Re: gdm/xdm setup

[Govind Salinas <warder pcisys net>]

On Fri, 10 Sep 1999 16:57:04 Roberto Zunino wrote:
> 
> On Thu, 9 Sep 1999, Ben FrantzDale wrote:
> 
> > thanks.... that's what I was looking for :-)
> > 
> > One other oddity:  I removed the redhat logo and turned the background
> > black, adding xflame -root to $prefix/etc/gdm/Init/Default.  It seemed as
> > though xflame was running very strangely (slowly, glitchy) and a check of
> > top revealed two coppies of it running. killing one made it better.
> > I also tried Eterm -e top as part of $prefix/etc/gdm/Init/Default  this lead
> > to two instances of top!
> > I got rid of the Eterm line and had this:
> > killall xflame
> > xflame -root &
> > the problem with an ugly xflame went away, so it appears as though
> > $prefix/etc/gdm/Init/Default is being run twice. is this intentional?
> > 
> > also, if xflame doesn't have the ampersand on the end, the gdm logon screen
> > doesnt appear. with the ampersand you have to click the mouse before it
> > appears, then, of course, you have to kill xflame as root once you are loged
> > in.
> > 
> > suggjestions?
> > 
> > thanks,
> >         Ben
> 
> (assuming gdm2-beta)
> 
> If you start something in Init, it must be non blocking: i.e. if the
> command doesn't return immediately (like xflame but unlike xv -root , for
> example) you must use the ampersand in order to run it in the background.
> 
> Check that you have KillInitClients=1 in your $prefix/etc/gdm/gdm.conf in
> the [daemon] section: this option should kill what you start in Init
> so you don't have to kill it yourself.
> 
> Hope this helps!
> Zun.
> 
I have this line in my gdm.conf and I still get two versions of xflame.
However, I put

killall xflame
xflame -root &

in my Defaults file and I only endup running one at a time. 

NB:I am assuming that one Default script is run and then the other.  If
that is not the case and both processes run concurrently you could still
end up with two xflames.