|
|
Heads-Up: Starcat/Starfire dcs daemonDate: Wed, 14 Dec 2005 15:24:29 -0800 From: Michael Bergknoff <Michael dot Bergknoff at Sun dot COM> To: onnv-gate at onnv dot eng dot sun dot com, on-all at eng dot sun dot com Subject: Heads-Up: Starcat/Starfire dcs daemon (If you do not upgrade or bfu a Starcat or Starfire system then no need to read further.) With my putback of 4792021 per-socket level IPsec policy for dynamic reconfiguration The dcs(1M) service will now run as a daemon not controlled by inetd. This was done in order to allow it to use per-socket IPsec options. With my set of changes error messages will be generated on the console after reboot. The error messages on console will appear similar to the following: xc69p20-b6 console login: Dec 12 15:12:21 inetd[387]: Property 'name' of instance svc:/platform/sun4u/dcs:default is missing, inconsistent or invalid Dec 12 15:12:21 inetd[387]: Property 'endpoint_type' of instance svc:/platform/sun4u/dcs:default is missing, inconsistent or invalid Dec 12 15:12:21 inetd[387]: Property 'isrpc' of instance svc:/platform/sun4u/dcs:default is missing, inconsistent or invalid Dec 12 15:12:21 inetd[387]: Property 'wait' of instance svc:/platform/sun4u/dcs:default is missing, inconsistent or invalid Dec 12 15:12:21 inetd[387]: Unspecified inetd_start method for instance svc:/platform/sun4u/dcs:default Dec 12 15:12:21 inetd[387]: Invalid configuration for instance svc:/platform/sun4u/dcs:default, placing in maintenance This will occur only once during reboot after the initial changes for this service has been installed. The reason why the error messages are produced is from the fact that when svc.startd starts up, it sees that dcs's restarter is inetd, and sends the messages for inetd to control it, which queue up until it starts. Then the service is upgraded to be controlled by startd, and startd starts it, but when inetd starts up it sees the pending messages and tries to start dcs, but finds it mis-configured. So once the messages are gone and startd realizes that it is supposed to control dcs, inetd shouldn't complain any more. This does not cause any problems and can be resolved by issuing a restart for the service, as follows: # svcadm restart svc:/platform/sun4u/dcs:default If you have any questions/concerns please e-mail me directly. Mike |