Search the FAQ Archives

3 - A - B - C - D - E - F - G - H - I - J - K - L - M
N - O - P - Q - R - S - T - U - V - W - X - Y - Z
faqs.org - Internet FAQ Archives

SGI admin Frequently Asked Questions (FAQ)
Section - -45- Why are there "satwrite failure: inetd" messages in my SYSLOG in IRIX 5.3?

( Single Page )
[ Usenet FAQs | Web FAQs | Documents | RFC Index | Counties ]


Top Document: SGI admin Frequently Asked Questions (FAQ)
Previous Document: -44- Why can't I 'rdist' files between Suns and SGIs?
Next Document: -46- What is causing the "get interface flags" error in my syslog?
See reader questions & answers on this topic! - Help others by sharing your knowledge
Date: 4 Jun 1997 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 1268. If you don't use auditing, you can just
  ignore the messages or remove the eoe2.sw.audit subsystem and rebuild
  your kernel.

User Contributions:

Comment about this article, ask questions, or add new information about this topic:



Top Document: SGI admin Frequently Asked Questions (FAQ)
Previous Document: -44- Why can't I 'rdist' files between Suns and SGIs?
Next Document: -46- What is causing the "get interface flags" error in my syslog?

Single Page

[ Usenet FAQs | Web FAQs | Documents | RFC Index ]

Send corrections/additions to the FAQ Maintainer:
sgi-faq@viz.tamu.edu (The SGI FAQ group)




Last Update March 27 2014 @ 02:12 PM