Bernd Gruber wrote: > hi, > i wanted to change 2 properties of /network/finger > i did so by using the inetadm command > when i have a look at the properties by using the inetadm -l command it shows > the right changes > > inetadm -m finger user="xxx" > inetadm -m finger exec="/etc/myscript xxx" > > bash-3.00# inetadm -l finger > ..... > isrpc=FALSE > wait=FALSE > exec="/etc/myscript xxx" > user="xxx" > default bind_addr="" > ..... > > > thats' okay!! > > BUT!!! > > scvprop has i think a problem with the widespace because it shows > exec="/etc/myscript\ xxx". so at the end of myscript an backslash. > > when i use svccfg and type: > select finger > listprop > > the listprop command shows the wrong (the old) properties. > > and the finger command is in the maintenance status (maybe because of the > backslash?!?!?!?) > > maintenance 10:27:13 svc:/network/finger:default > > 1) what can i do to fix this (the maintenance problem and the thing with the > svccfg command, that it show the right properties) > 2.) how can i change the .xml file (not with vi, with the svccfg command (i > hope that this is possible)) >
I ran into something like this a while ago. My problem was that the inetd service and its instance had some different properties. I think if you use inetadm, it changes the property value of the service. When you use svccfg to look, you will see a difference in the values set at the service level and at the instance level. exec="" is one of those properties existing at both levels. This can cause a mild heart-attack if you're troubleshooting your service in the wee hours of the morning after being awaken by your pager. I would rather just have unique properties in the service or the instance, and not both. I think we had a brief discussion about this on this list at one time, but for some reason, no doubt valid then, I did not file a bug. I don't really use inetadm, not sure if there's functionality there that's not in svccfg. I just use svccfg, make sure I'm in the instance, and enclose the values in double-quotes. I don't think the XML file can be changed by manipulating svccfg, unless you dump out the XML yourself by exporting the service and overwriting your original XML. And THEN, export only works on the service, not the instance, so just keep that in mind. CT
