Folks,
I discovered that running VNC (Virtual Network Computing, and extremely
useful tool) on my server prevented Win4Lin from starting in fwin mode.
After some digging, I discovered that it was because fwin allocates a
new display for itself by looking for Xwrapper to find the first
available display number. However, VNC does not use Xwrapper ... it
uses Xvnc. Thus fwin tried to allocate an x-server already in use, and
crashes.
The solution is to modify the fwin script as follows:
Find this section:
#look for a display that x is not running on.
for XX in 0 1 2 3 4 5 6
do
ps ax | grep Xwrapper | grep :$XX > /dev/null
[ $? -ne 0 ] && break
echo X running on $XX
done
And alter the 4th line to:
ps ax | grep X[wv][nr][ac] | grep :$XX > /dev/null
This new grep line selects both Xwrapper and Xvnc, while minimizing the
chances of selecting a random X application.
-Josh Berkus
--
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology [EMAIL PROTECTED]
and data management solutions (415) 436-9166
for law firms, small businesses fax 436-0137
and non-profit organizations. pager 338-4078
San Francisco
_______________________________________________
Win4Lin-users mailing list
[EMAIL PROTECTED]
http://lists.trelos.com/mailman/listinfo/win4lin-users
