I believe midmand is started in the /etc/rc.tcpip script, go to bottom of 
script and comment out the lines that start midmand.

-----Original Message-----
From:   Matt Ashfield [SMTP:mda AT UNB DOT CA]
Sent:   Friday, July 16, 1999 1:26 PM
To:     NV-L AT UCSBVM.ucsb DOT edu
Subject:        Re: NWays Installation Help!

James

Is there a way to keep the midmand daemon from starting at startup? I'm
thinking that my NWays daemons might not start right at reboot because
initially midmand is running, and therefore trapd doesn't start. I thought
this might be what is causing them to reach an UNSTARTABLE state...
Once I stop midmand, trapd is able to run. But my NWays daemons are all in
an unstartable state....


Thanks for your time!

Matt
mda AT unb DOT ca


-----Original Message-----
From: James Shanks <James_Shanks AT tivoli DOT com>
To: NV-L AT ucsbvm.ucsb DOT edu <NV-L AT ucsbvm.ucsb DOT edu>
Date: Thursday, July 15, 1999 5:47 PM
Subject: Re: NWays Installation Help!


>Do netstat -an.  Is 162/udp shown?  Then some process or other has it and
you
>will have to find that one and kill it for trapd to start.  Do a ps -ef
(or
>even ovstatus) and see what you find.  If Nways installed midmand, then
kill it,
>as he cannot run in the same box as NetView without reconfiguration.  Not
him?
>Then find what new stuff is running and kill it one at a time.  Or kill all
the
>daemons down to nvsecd, ovstart trapd, and then ovstart.  I'll bet the guy
who
>has trapd's port won't start if trapd comes up first.   This should get you
back
>and running while you review what took place.
>
>James Shanks
>Tivoli (NetView for UNIX) L3 Support
>