T.R | Title | User | Personal Name | Date | Lines |
---|
2838.1 | Any old files arround? | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Thu Apr 23 1992 16:48 | 6 |
| The only time we have seen this type of message is when someone
mixes executables from two different baselevels.
Might you have any pre-T1.2.7 executables still on the system?
Or perhaps some DECmcc process (an event sink?) was running
during an upgrade?
|
2838.2 | | SUBWAY::REILLY | Mike Reilly - New York Bank District | Thu Apr 23 1992 18:43 | 4 |
| I just did an ls -l on the /usr/mcc/mmexe and /usr/mcc/mcc_system
directories and all executables were created at installation time.
- Mike
|
2838.3 | QAR 2807 | TOOK::MINTZ | Erik Mintz, DECmcc Development, dtn 226-5033 | Thu Apr 23 1992 20:11 | 1 |
| QAR 2807
|
2838.4 | old processes? | DADA::DITMARS | Pete | Fri Apr 24 1992 11:17 | 8 |
| What about the second question:
>Or perhaps some DECmcc process (an event sink?) was running
>during an upgrade?
Is there any possibility of that? If you can, can you either kill every
mcc process on the system (mcc_kill won't do it all) or just reboot and
let us know if the problem persists.
|
2838.5 | also, I've heard udm can interfere with proper behavior | DADA::DITMARS | Pete | Fri Apr 24 1992 11:58 | 2 |
| if you're using the assett udm, try turning it off and reproducing the
problem, and please let us know if this has any impact.
|