| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
I'm running an AM on Ultrix. I have 2 sessions, and do the
following:
session 1 ->
manage> enroll mcc_tps_am
session 2 -> manage> enroll mcc_tps_am
On session 1, I get "Detached process failure: Bad file
number".
I know that the 2nd enrollment kills the first process and
starts another, but that that message isn't very clear,
(or user friendly) Is this going to change?
In note 2634.4, there was an indication that this might
be a problem in the PM, and would be fixed in x1.2.19.
Would that have been changed in EXT Update (which I'm running)
Does someone have an update on this error?
thanks,
Bonnie
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3274.1 | TOOK::SWIST | Jim Swist LKG2-2/T2 DTN 226-7102 | Tue Jun 30 1992 13:37 | 5 | |
Why would you enroll an MM twice from two different sessions?
The message may not be clear but it's a pretty strange thing to be
doing.
| |||||
| 3274.2 | Well, it's better than nothing. Or is it? | TOOK::GUERTIN | It fall down, go boom | Wed Jul 01 1992 11:23 | 11 |
The message is only saying that the first process detected that the
child process it started up died. It is picking up an errno which
may or may not be valid, but it is better than not giving you any
clue whatsoever. A better error message might be:
"A child process died unexpectedly, maybe because of a bad file
number? or maybe because someone just killed it."
Is this a case where the less information we give the user, the
better?
-Matt.
| |||||
| 3274.3 | more on 1 | MICROW::LANG | Wed Jul 01 1992 12:14 | 21 | |
>Why would you enroll an MM twice from two different sessions?
In our situation, we may enroll without knowing that a process already
exists. We are doing a number of things, so have different windows.
It probably isn't that common, but I'm sure some user would run
into it. (In other words, we didn't plan on doing it, but the
message was unclear to the developers, when it did happen.)
I think its good to have information, because in all those
cases where its not enrollment, its helpful to know what happened.
I would think it would be helpful to know that its a management
module that died, and that its ok, because it was done intentially.
So I would think a clear message would be (assuming you can't
determine when a MM died because of enroll and when it was killed
for some other reason)
" A management process just terminated either because of
enrollment, someone killed it, or due to a bad file number."
| |||||