Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!uwvax!tank!msuinfo!sharkey!cfctech!rel!edsews!williams
From: williams@edsews.eds.com (Dave Williams)
Newsgroups: comp.sys.apollo
Subject: How can I get rid of Apollo IOT traps?
Keywords: IOT traps
Message-ID: <24866@edsews.eds.com>
Date: 4 May 90 19:54:03 GMT
Distribution: usa
Organization: EDS/TSD - Troy, MI
Lines: 36

I would like to know what an Apollo IOT trap is,
what causes it, and how to get rid of it.

We have some unix shell scripts that add/change/delete user accounts on the
Apollos. Twice, after a test periods of about 2 months, these IOT traps start
showing up. For about 2 months, testing goes along fine. Then all of a sudden,
IOT traps show up. We are only changing our own test accounts and not the root
accounts.

We have not been able to find out if IOT traps are related to:

                         registries
                         nfs
                         remsh
                         other/all?

- We are logged onto a machine (may or may not be an Apollo) as root.
- The machine we are logged into is a trusted host to the Apollo machine.
- We remsh into an Apollo to access a nfs mounted file system and receive an IOT
  trap.

 Example:  remote_machine_prompt==> remsh apollo_node ls /nfs_mounted_filesystem

This even happens if we are logged onto the Apollo that we are trying to remsh
to.

I am wondering if the registries cannot handle 30-50 changes per day over this
length of time. Any other ideas?

How do we get rid of this problem when it shows up? So far, the only way we have
found to get rid of the problem is to completely rebuild the registries.
-- 
Dave Williams                       |  My opinions are not necessarily those
EDS Technical Systems Development   |  of my employer.
williams@eds.com                    |
UUCP: {uunet|sun|sharkey}!edsews!williams