Subject:   -41- Why are there "satwrite failure: inetd" messages in my
                SYSLOG in IRIX 5.3?
Date: 31 May 1995 00:00:01 EST

  Says Ellen Desmond <desmond@orange.engr.sgi.com>:
  This is due to a bug in inetd that is manifest only when eoe2.sw.audit
  has been installed.  Inetd calls satwrite() to generate an audit
  record every time it spawns a server.  The bug is that the call to
  satwrite() is made after the process has done a setuid() to the user
  specified for that server in inetd.conf.  Because satwrite() is a
  superuser-only call, it fails for servers that don't run as root, such
  as fingerd.

  The bug is fixed by patch 327. If you don't use auditing, you can just
  ignore the messages or remove the eoe2.sw.audit subsystem and rebuild
  your kernel.