"Derek Warren" <[EMAIL PROTECTED]> wrote: > [... T]he > Mini-ITX left the DTUs resetting after flashing 26B in an endless > loop. > > /var/opt/SUNWut/log/messages showed that all was well, but > /var/dt/Xerrors showed that Xsun keeps on dying over and over: > > XIO: fatal IO error 146 (Connection refused) on X server ":2.0" > after 0 requests (0 known processed) with 0 events remaining. > XIO: fatal IO error 146 (Connection refused) on X server ":2.0" > after 0 requests (0 known processed) with 0 events remaining. > ... (ad nauseum) > > Supposedly Xsun doesn't care about the video hardware in the > machine running SunRay Server [...]
It doesn't, provided that you have Xsun/x86 patch 119060-02 or better installed. What rev of that patch do you have? > http://derek.trideja.com/lib/srss_appcrash_output.txt That's just a dtlogin process, there's not much of interest there. A 'truss' of the failing Xsun would be more interesting. You can get that by doing 'truss -f' on the master dtlogin process (the one whose parent PID is 1) and then doing something to trigger SRSS into telling dtlogin to launch a new Xsun. One easy(-ish) way to do that is to: - disconnect the Sun Rays - 'utrestart -c' - wait a few seconds and then start the 'truss -f' against the master dtlogin process. (And use '-o' to direct the output to a file, there'll be lots of it. - reconnect _one_ Sun Ray, so that dtlogin gets told to launch one Xsun instead of cluttering the truss output with lots of Xsuns and their corresponding slave dtlogins and dtgreets OttoM. __ ottomeister Disclaimer: These are my opinions. I do not speak for my employer. -- ___________________________________________________________ Sign-up for Ads Free at Mail.com http://promo.mail.com/adsfreejump.htm _______________________________________________ SunRay-Users mailing list [email protected] http://www.filibeto.org/mailman/listinfo/sunray-users
