Someone had this error, and we recommended to them to just remove the lock and continue. In this case, there would have been no difference to the server doing it automatically.
Perhaps we should start with what caused this. * What creates this lock? * Under what circumstances would this lock exist without X running? * What is the worst case senario for ignoring the error, removing the lock, and continuing? JohnFlux On Wed, Jan 29, 2003 at 09:35:57AM +0000, Dr Andrew C Aitchison wrote: > On Wed, 29 Jan 2003, John Tapsell wrote: > > > > On Tue, 28 Jan 2003, Andrew V. Stiegmann wrote: > > > > If this server is no longer running, remove /tmp/.X0-lock > > > > and start again. > > Couldn't we have X look for a running process, and if none found, > > delete the lock? > > > > If not automatically, then ask the user whether to. > > > > It does seem rather silly to bother the user about this. > > Care to write platform independent code to do that. > Sorry make that code that runs on all our platforms, warts and all. > > More seriously, if the lock file is there but no process is running, > then something nasty happened. > I think that the user ought to know about that, > so that they can take corrective action. > > Don't forget that things like xdm run X repeatedly. > If something like this happens I'd rather have a tight loop > if X start, notice a problem and stop, than have a tight loop > of notice a problem, pretend it didn't happen and then perhaps > go on to do something that might well make a confused graphics card worse. > > -- > Dr. Andrew C. Aitchison Computer Officer, DPMMS, Cambridge > [EMAIL PROTECTED] http://www.dpmms.cam.ac.uk/~werdna > > _______________________________________________ > XFree86 mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xfree86 -- _______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
