On 06/02/09 21:35, Liane Praza wrote: > Sangeeta Misra wrote: >> On 06/02/09 20:00, Liane Praza wrote: >>> Sangeeta Misra wrote: > [...] >>>> Ah I remember. So daemon invokes smf_maintain_instance() to put >>>> the service in maintanance mode. THen we want the user to use some >>>> non- ilbadm command to wipe out the ilb config in SCF and then >>>> issue the svcadm enable <ilb service manually> >>>> >>>> So any imput on what is the correct scf command to wipe out ilb >>>> config in SCF? >>> >>> Take a look at svccfg selectsnap and revert. They're documented in >>> the manpage. I believe there's a procedure for using them in the >>> System Administration Guide as well, but could be wrong. >>> >> Will do >>> I'd really expect that reverting to the snapshot would be an >>> exceptional operation, not a normal one though. >> >> Correct - the above discussion was about what to do if ilbd >> experiences a fatal error. In such a case, we want the ilbd daemon to >> automatically make the ILB service go into maintanence mode. The >> user would send us configuration, and a description of what >> happened, so we can work on the problem. > > OK. I'd also recommend sensible error messages from your daemon/start > method either to its own logfile, syslog, or its stdout (which will be > redirected to the service logfile). That way the user can make > progress on their own too. We do have error messages from daemon that will go to syslog. We dont have a start method as all the start method does is start the ilbd daemon. See attached ilbd_xml
Sangeeta > >> >> But while the user waits for the problem to be identified, they *may* >> wish to run the ILB service from scratch. Hence the question about >> wiping out the config via SCF. >> > > Sure. > > liane -------------- next part -------------- A non-text attachment was scrubbed... Name: ilbd.xml Type: text/xml Size: 2992 bytes Desc: not available URL: <http://mail.opensolaris.org/pipermail/smf-discuss/attachments/20090602/2e8a3d39/attachment.xml>
