stray matlab process after logout from CDE (running solaris 2.6)

stray matlab process after logout from CDE (running solaris 2.6)

Post by Alex Sau-Leung L » Tue, 08 Dec 1998 04:00:00



Hi,

    Recently, we observed that when users log out of their workstations
    directly from their CDE desktop before quitting matlab.  Then the
    following processes will remain stray in the workstations :

$>ps -ef | grep lmfok
lmfok  8429     1 80 11:29:16 ?   19:53 /usr/local/matlab52/bin/sol2/matlab
lmfok  8481  8429 80              0:07 <defunct>
lmfok  8490     1 80 11:30:02 ?   0:01 windu_registryd41 -d /home/student/yr97/97lmfok
  -vers 2 -prog 805505148

   These processes consume quite a lot system resources and usually we
   need to kill them manually.

   I wondering if this is a bug.  For your information, we are running
   solaris 2.6 on SUN SPARC 20, 10, 5 and ultra 5 workstations and the
   matlab version is 5.2.1.

   Any pointers and comment are appreciated.

-----------
Alex Lee

Mechanical and Automation Engineering
The Chinese University of Hong Kong

 
 
 

stray matlab process after logout from CDE (running solaris 2.6)

Post by Steve Bellen » Tue, 08 Dec 1998 04:00:00




Quote:

>Hi,

>    Recently, we observed that when users log out of their workstations
>    directly from their CDE desktop before quitting matlab.  Then the
>    following processes will remain stray in the workstations :

>$>ps -ef | grep lmfok
>lmfok  8429     1 80 11:29:16 ?   19:53 /usr/local/matlab52/bin/sol2/matlab
>lmfok  8481  8429 80              0:07 <defunct>
>lmfok  8490     1 80 11:30:02 ?   0:01 windu_registryd41 -d /home/student/yr97/97lmfok
>  -vers 2 -prog 805505148

>   These processes consume quite a lot system resources and usually we
>   need to kill them manually.

>   I wondering if this is a bug.  For your information, we are running
>   solaris 2.6 on SUN SPARC 20, 10, 5 and ultra 5 workstations and the
>   matlab version is 5.2.1.

>   Any pointers and comment are appreciated.

1. Find out what the process is doing. Use my favorite solaris feature
"truss" to attach to the process and see what that wayward program is
tring to do. (In 2.7 truss is even better, it will trace user-level function
calls too.)
2. But it looks like pid 8429 forked pid 8481 and has not "waited" for
the return status. But what 8429 is doing instead?
--


 
 
 

stray matlab process after logout from CDE (running solaris 2.6)

Post by Alex Sau-Leung L » Wed, 09 Dec 1998 04:00:00




: >
: >Hi,
: >
: >    Recently, we observed that when users log out of their workstations
: >    directly from their CDE desktop before quitting matlab.  Then the
: >    following processes will remain stray in the workstations :
: >
: >$>ps -ef | grep lmfok
: >lmfok  8429     1 80 11:29:16 ?   19:53 /usr/local/matlab52/bin/sol2/matlab
: >lmfok  8481  8429 80              0:07 <defunct>
: >lmfok  8490     1 80 11:30:02 ?   0:01 windu_registryd41 -d /home/student/yr97/97lmfok
: >  -vers 2 -prog 805505148
: >
: >   These processes consume quite a lot system resources and usually we
: >   need to kill them manually.
: >
: >   I wondering if this is a bug.  For your information, we are running
: >   solaris 2.6 on SUN SPARC 20, 10, 5 and ultra 5 workstations and the
: >   matlab version is 5.2.1.
: >
: >   Any pointers and comment are appreciated.

: 1. Find out what the process is doing. Use my favorite solaris feature
: "truss" to attach to the process and see what that wayward program is
: tring to do. (In 2.7 truss is even better, it will trace user-level function
: calls too.)
: 2. But it looks like pid 8429 forked pid 8481 and has not "waited" for
: the return status. But what 8429 is doing instead?

matlab is not doing anything but sleeping (waiting for user input).
I have not tried using truss yet.  I will try.

--------------------------
Alex Lee

Mechanical and Automation Engineering
The Chinese University of Hong Kong

 
 
 

1. Solaris 2.6, CDE, and spontaneous logouts

Every few days,  I sit down at my trust Sparc 10 and find myself staring at
the CDE login screen.  This is odd since my mean time between logouts is
somewhere around a month and no one else even has access to this machine.

My only clue is two lines from /var/adm/messages:

Jul 16 10:08:46 spica /usr/dt/bin/ttsession[6581]:
child (14066) exited due to signal 1
Jul 16 10:08:46 spica /usr/dt/bin/ttsession[6581]:
child (6622) exited due to signal 1

Now that's fair enough.  ttsession exists because it received a hangup signal.
But who sent the signal and why?

I have installed the very latest recomended patches but the problem persists.

Any ideas?

--
Real courtesy requires human effort and understanding.  
Never let your machine or your habit send courtesy copies.

2. Newbie Question: How do you tinker with LILO?

3. CDE/1.2 (Solaris/2.6) vs CDE/1.0.2 (Solaris/2.5.1) -- Login-Screen Question

4. CDROM for Sparc & x86

5. Running a home-made shell with CDE 1.2 / Solaris 2.6

6. ANNOUNCE: Linux Software Archive

7. SOLARIS 2.6 CDE AppMgr-dtterm-not running

8. X312F Problems with TVGA9440 !!!!!!

9. SPARC Solaris 2.6/CDE 1.2 Sun CDE extension question

10. Random CDE logouts on 2.6

11. Solaris 2.6 Machine (CDE) as Xterm to HP-UX 10.20 (CDE)

12. csh .logout script, running matlab

13. Matlab solaris 2.6 x86