bug-inetutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

address@hidden: Re: [bug-inetutils] Inetutils-1.4.2 not registering sgi_


From: Alfred M. Szmidt
Subject: address@hidden: Re: [bug-inetutils] Inetutils-1.4.2 not registering sgi_fam]
Date: Mon, 19 Jun 2006 19:12:03 +0200 (CEST)

I guess we can ignore this bug, for now...

------- Start of forwarded message -------
From: "address@hidden" <address@hidden>
Date: Mon, 19 Jun 2006 17:07:56 GMT
To: address@hidden
Subject: Re: [bug-inetutils] Inetutils-1.4.2 not registering sgi_fam

This has been a while back, I've forgotten the exact circumstances.  It
turned out FAM was the only thing I had inetd starting, so as a
workaround I started it in rc3.d.  My understanding is "sunrpc" is the
port that needs to be in services.


Paul Rogers  (address@hidden)
http://www.xprt.net/~pgrogers/
Rogers' Second Law: "Everything you do communicates."
(I do not personally endorse any additions after this line. TANSTAAFL :-)


- -- "Alfred M. Szmidt" <address@hidden> wrote:
   Mar 4 15:34:34 pallas inetd[2160]: sgi_fam/1-2/rpc/tcp: unknown
   service

Is the service "sgi_fam/1-2/rpc" defined in /etc/services (from the
looks `sgi_fam/1-2' is defined, but the syntax for this error message
is stupid so maybe it needs a /rpc in /etc/services)?  As I understand
it, it worked on one platform, and then when you moved the binaries it
stopped working, so maybe it is just a /etc/services disreprency.
Could you check the content of those files on both systems?

I'll install a patch that chanes the log message for this particular
message to differentiate between the protocol and the service, the new
format will be:

syslog (LOG_ERR, "%s (%s): unknown service", sep->se_service,
sep->se_proto);

instead of:

syslog (LOG_ERR, "%s/%s: unknown service", sep->se_service, sep->se_proto);

Thank you for your bug report.
------- End of forwarded message -------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]