[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference turris::digital_unix

Title:DIGITAL UNIX(FORMERLY KNOWN AS DEC OSF/1)
Notice:Welcome to the Digital UNIX Conference
Moderator:SMURF::DENHAM
Created:Thu Mar 16 1995
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:10068
Total number of notes:35879

8695.0. " Wall command forks an uninterruptable process" by HEN::MEHTA () Tue Feb 04 1997 08:55

         OS : Digital Unix 4.0 A
         window manager : CDE
         Platform : Alpha server 1000 A
         Problem : Here's the sequence
                   1. Boot the server
                   2. wall command is working from console
                   3. let the server run for a few days
                   4. issue wall command from console
                      it takes the message text
                      after i hit cntrl-d to send the msg
                      the session hangs
                   5. I log in from  another terminal and look for the wall
                      process. The process is uninterruptable U.
    
    Scenerio: I have created a sh script to shutdown the server on sunday
              and then reboot the server in single user mode to take a
              full backup, after which init 3 brings the server to a multi
              user + n/w mode.
              shutdown fails after server is up for 7 days,  because wall
              is hanging so my script is no good. If the server is up for
              a few hours the script works okay.
    
    
                                                             
              
T.RTitleUserPersonal
Name
DateLines
8695.1get a stack traceSMURF::DUSTINTue Feb 04 1997 11:499
    you need to trace the process using dbx on the kernel, ie.
    
    	# dbx -k /vmunix
        set $pid=2174          (the pid of stuck process)
        t
    
    
    John
    
8695.2Found Patch to fix the problemHEN::MEHTAFri Feb 07 1997 10:066
    
     I found a patch kit OSF400-107 that will ( hopefully ) fix my problem.
     The problem is actually due to the wall and ntalkd  processes that 
     remain hanging due to  the abnormal termination of LAT sessions.
    
     Ajay