Andreas, I use the dmstatus tool only occasionally but have never seen the problem you described. My sum of dmstatus is exactly like yours (on a SPARC Ultra 5, AW51D). The information is kept in /tmp/_dm<DMNAME> so you may want to check there to see if something has happened to those little text files. (I have a home-brewed command to do the same thing as dmstatus. Although mine is nowhere near as slick as dmstatus, old habits die hard, and I mostly use my command instead of dmstatus.) Duc -----Original Message----- From: foxboro-bounce@xxxxxxxxxxxxx [mailto:foxboro-bounce@xxxxxxxxxxxxx] On Behalf Of Weiss, Andreas Sent: Wednesday, April 26, 2006 2:54 AM To: foxboro@xxxxxxxxxxxxx Subject: [foxboro] legacy Display Manager and dmstatus failure Hi, is anyone out there who uses the dmstatus tool on a machine with legacy Display Manager? It generates sometimes a wrong output. # dmstatus fcntl error fcntl error fcntl error fcntl error fcntl error O Q7014F View_Only 129:230 22303 root 2006/04/26 07:31:33 fcntl error fcntl error O Q7017F View_Only Available fcntl error # # sum dmstatus 52280 19 dmstatus # A reboot helps always but that isn't the way that I want to go. Regards, Andreas =20 _______________________________________________________________________ This mailing list is neither sponsored nor endorsed by Invensys Process Systems (formerly The Foxboro Company). Use the info you obtain here at your own risks. Read http://www.thecassandraproject.org/disclaimer.html foxboro mailing list: //www.freelists.org/list/foxboro to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave