Hi

It doesn't matter which window manager I use. The ~/.xession which I have 
is:

#!/bin/sh
xterm &
exec fvwm2

*or*

exec twm

In fact, I've noticed that even if you dont log onto the console it goes 
black for a second or two, like its going to sleep, even though the 5 
minutes is not up :-) then it starts again. If I do a ps -ax on the the 
processes, I notice that xdm is running twice.

I don't know if this could have an affect on it, I run a shell script from 
rc.local to start my PPP connection, it loops checking that the line is 
running and if it isn't restarts it. I did try disabling this and other 
optional services like apache to see if they were causing it, didn't change 
a thing.

Any ideas would be muchly appreciated.

Cheers, Paul.

-----Original Message-----
From:	Frederick Bruckman [SMTP:fb@enteract.com]
Sent:	Sunday, September 12, 1999 12:28 AM
To:	Paul Thompson
Cc:	'MacBSD'
Subject:	Re: X

On Sat, 11 Sep 1999, Paul Thompson wrote:

> Got most of my upgrade to 1.4.1 working now, Thanks to everyone who 
helped
> with my DNS problems, But X is now giving me some grief :-) If I use xdm 
I
> can login, but I have to complete my session in less than two mintues or 
it
> kicks me off back to the login screen :-) This in itself can be a
> challenge!
>
> What I've done to X. :-)
> 	Installed the OSFA colour server for 1.4 which is working fine.
> 	Installed fvwm2 from the package source which is also working fine.
> 	Installed mozilla, which while slow works.
> 	Followed the faq for configuring and installing xdm.
>
> If I disable xdm from rc.conf and manually startx it works fine. Any 
ideas?

It sounds like maybe your .xsession script is completing prematurely.
How are you starting fvm2? The "normal" way to start a window manager
is to end ~/.xsession with a line like "exec fvm2", or "exec ssh-agent
fvm2", so .xsession doesn't complete until the window manager does.