It checks for other Win4Lin processes. Normally when you shut
down a Win4Lin process, all the associated processes exit.
But apparently sometimes it seems that a process somehow did not exit.
Use "ps -e" or "ps a" (depending on which distribution you are using)
to see if a "dosexec" process is running. If it is, then you
need to kill that process to clear things up.
-David
"Paul W. Abrahams" wrote:
>
> I wonder - how does Win4Lin determine that there's an active session
> and that therefore it must not start another one? Is there, perhaps,
> a lock file lurking somewhere?
>
> > > I've encountered this problem several times. I'm forced to
> > > shut down Win4Lin because of some kind of unrecoverable
> > > error. Then, when I attempt to start it, the restart is
> > > blocked because Win4Lin thinks there's already a session
> > > going. Even shutting down X and logging in again doesn't
> > > cure the blockage, although a total system reboot does clear
> > > it.
> > >
> > > How can I clear this blockage without having to resort to a
> > > full reboot?
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
https://lists.netraverse.com/mailman/listinfo/win4lin-users
