OpenSolaris

1. Community: OS/Net (ON)
   1. Blogs
   2. Development Process
   3. Developer's Reference
      1. Introduction
      2. Prerequisites
      3. The Source Tree, part 1
      4. The Source Tree, part 2
      5. Building OpenSolaris
      6. Installing and Testing OpenSolaris
      7. Integration Procedure
      8. Best Practices and Requirements
      9. Glossary
   4. Discussions
   5. Installation (from source) Quickstart
      1. Annotated nightly(1) Mail Example
   6. Currently Known Issues
   7. CRT
      1. Advocates & Sponsors
      2. Becoming a CRT Advocate
      3. Charter
      4. RTI nits to avoid
      5. Sponsor Tasks
      6. Becoming a Sponsor
   8. Schedule
   9. ONNV Flag Days, Heads Ups, and Project Integration History
      1. All
      2. Builds 96-100
      3. Builds 91-95
      4. Builds 86-90
      5. Builds 81-85
      6. Builds 76-80
      7. Builds 71-75
      8. Builds 66-70
      9. Builds 61-65
      10. Builds 56-60
      11. Builds 51-55
      12. Builds 46-50
      13. Builds 41-45
      14. Builds 36-40
      15. Builds 31-35
      16. Builds 26-30
      17. Builds 21-25
      18. ONNV Flag Days, Heads-Ups and Project Integration History (snv_101 - snv_105)
   10. Leaders
   11. Observers
   12. Putback Logs
   13. Developing Solaris
       1. Quality Death Spiral
   14. wx
   15. findunref and unreferenced files
   16. Bourne/Korn Shell Coding Conventions

heads-up: inetd warnings on systems installed before S10FCS

Date: Wed, 2 Nov 2005 13:17:32 -0800 (PST)
From: David Stafford <David dot Stafford at eng dot sun dot com>
To: onnv-gate at onnv dot eng dot sun dot com
Subject: heads-up: inetd warnings on systems installed before S10FCS



After the fix of 6311192 smf/inetd no longer allows duplicate RPC services.
If you BFU a computer that was installed before S10FCS to onnv_27, "svcs"
will show you something like

....
maintenance    15:29:52 svc:/network/rpc-100083_1/rpc_tcp:tcp
maintenance    15:29:52 svc:/network/rpc-100068_2-5/rpc_udp:udp
maintenance    11:08:53 svc:/network/rpc-100424_1/rpc_ticotsord:ticotsord

You will aso see syslog errors like:

Nov  1 14:08:24 coupe inetd[100421]: [ID 702911 daemon.error] Too many 
bind failures for instance svc:/network/rpc-100083_1/rpc_tcp:tcp, 
transitioning to maintenance
Nov  1 14:08:24 coupe inetd[100421]: [ID 702911 daemon.error] Too many 
bind failures for instance svc:/network/rpc-100068_2-5/rpc_udp:udp, 
transitioning to maintenance
Nov  1 14:08:24 coupe inetd[100421]: [ID 702911 daemon.error] Too many 
bind failures for instance 
svc:/network/rpc-100424_1/rpc_ticotsord:ticotsord, transitioning to 
maintenance


This is because the instance names of those services were changed late in 
S10 and the old FMRIs were never cleaned off your computer.  In fact, the 
services are probably running just fine under the newer FMRIs (which end 
in :default). You can safely destroy the services with

svccfg disable svc:/network/rpc-100083_1/rpc_tcp:tcp
svccfg disable svc:/network/rpc-100068_2-5/rpc_udp:udp
svccfg disable svc:/network/rpc-100424_1/rpc_ticotsord:ticotsord
svccfg delete svc:/network/rpc-100083_1/rpc_tcp:tcp
svccfg delete svc:/network/rpc-100068_2-5/rpc_udp:udp
svccfg delete svc:/network/rpc-100424_1/rpc_ticotsord:ticotsord

Do not delete the ":default" instances of the services.   If the default
instances of any of these services were placed into maintenance mode,
execute "svcadm clear <service-name>" after aplying the above to restart it.

Thanks to Andrei Dorofeev for noticing and reporting the problem. Sorry 
for the inconvenience.