SOFPJF@VM.UOGUELPH.CA (Peter Jaspers-Fayer) (08/31/90)
I'm running 3.3 on my PI, and for some reason, for users having files ~/.4sight, user.ps and startup.ps, X applications & demos would not start. They WILL start from an xterm window. They also start OK if the standard windows are used. I accidentally stumbled on a partial explanation when I did a man on `xstart`. So I checked the swich in chkconfig called xSGINeWS. It is set to 'on' on my system. So it's being overridden by something. none of the id's have the $HOME/.xSGINeWS file, so that's not it. Since I stumbled on xstart, the work around is to call this 1st before calling any X programs, but something is still not right here. Any ideas? /PJ SofPJF@VM.UoGuelph.Ca (Probably also reachable (until ?) at SOFPJF@UOGUELPH.BITNET) Klein bottle for rent, apply within.
msc@ramoth.esd.sgi.com (Mark Callow) (09/05/90)
In article <9008301644.aa04610@VGR.BRL.MIL>, SOFPJF@VM.UOGUELPH.CA (Peter Jaspers-Fayer) writes: |> I'm running 3.3 on my PI, and for some reason, for users having files |> ~/.4sight, user.ps and startup.ps, X applications & demos would not |> start. They WILL start from an xterm window. They also start OK if |> the standard windows are used. In release 3.3 the mechanism for autostarting the X server had to be changed. The reasons escape me right now. The new mechanism involves the config option xSGINeWS and the xstart program that you discovered. The array basicRestartActions in the file /usr/NeWS/lib/NeWS/init.ps contains a call to a PostScript function called startXsgi which starts Xsgi via the xstart command. The user.ps file in the accounts where autostarting fails must be redefining basicRestartActions so that they don't include calling startXsgi. -- From the TARDIS of Mark Callow msc@ramoth.sgi.com, ...{ames,decwrl}!sgi!msc "There is much virtue in a window. It is to a human being as a frame is to a painting, as a proscenium to a play. It strongly defines its content."