You may be hitting 6237669 _check_services() SMF logic causing svc.configd overwork or 6276854 NO_RESOURCES caused svc.startd to spin
What version of Solaris are you running? Can you get a gcore(1) of both processes when the problem occurs? -- Renaud Sh wrote: > Why these two daemons often start(when no service failure occurs) and consume > a lot of cpu for a long time? > 103302 root 6268K 4528K run 22 0 0:18:36 18% svc.configd/5 > 103304 root 6356K 4748K run 31 0 0:18:27 17% svc.configd/5 > 100711 root 2952K 1460K sleep 33 0 0:42:25 16% svc.startd/3 > 102874 root 2952K 1636K sleep 32 0 0:18:59 16% svc.startd/3 > (Sometimes it's 25%(startd) and 30 %(configd)) > No way to disable them.What's wrong? > > > This message posted from opensolaris.org > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org
