cleaning up after XDRIVER
paul at cs.keele.ac.uk
Wed Dec 18 16:07:26 EST 1996
We use GRASS 4.1 (Spring 1993) Update package 4 under Solaris 2.5
to support some GIS teaching, and the only display devices we use
are XDRIVERs on our Sun workstations.
Students sometimes forget to do
and this causes problems when a subsequent user tries to start GRASS,
especially when the XDRIVER process has been killed or otherwise
We have tried removing the lock files, but subsequent attempts to
start an XDRIVER can nevertheless fail for reasons which are not
apparent (even to our sys admin).
Rebooting SunOS (something we almost never otherwise have to do)
seems to be the only cure.
I suspect that the "named pipes" are kept open, or that there is
data in them. Whatever, can anyone tell me how to clean up after
an improperly closed XDRIVER without rebooting?
_ _ Paul Singleton PhD CEng MBCS email:
p.singleton at keele.ac.uk
|_) (_` Dept. of Computer Science tel/fax: +44 1782 583477 /
| . __). Keele University, Newcastle, in U.K.: (01782) 583477 /
Staffs ST5 5BG, U.K. road: UK M6 J15 follow
More information about the grass-user