| Title: | sco_unix |
| Moderator: | AVNGRS::BOELKE |
| Created: | Mon Mar 26 1990 |
| Last Modified: | Thu May 22 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 2574 |
| Total number of notes: | 9709 |
My application locks ths serial port /dec/tty2D for exclusive use to transfer data. This port is the 4th serial "4-port card" port, which use the AST 4-port driver provided by SCO ODT 3.0. We observed the driver did not process the write system call issued by my application.This is intermittent. I tried to "kill -9" this process, it's not work. I tried to "cu" this port status, it's hangs forever. The only way I can restart ths application is "reboot". SCO HongKong support center suggests us using "crash" utility to see if there's any way we can avoid the "reboot". But,the following was happened: #crash > proc ! grep scfly #scfly is my process name > defproc 18 # 18 is the process id of scfly *** out of range Does anyone can tell me how it happen ? or Suggest any other way to stop the process ? Gary [Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 2561.1 | Specify process slot | CSCMA::EARNEST | Thu Jan 30 1997 20:34 | 13 | |
Gary, When you use the defproc command in crash, you need to specify the process slot rather than the process id. For example, # crash dumpfile = /dev/mem, namelist = /unix, outfile = stdout > proc ! grep named 25 s 344 1 344 0 26 0 f0178cc0 named load nxec > defproc 25 Procslot = 25 | |||||