Restarting too quickly, changing state to maintenance

Question

I'm trying to add a new resource to stop/start at reboot time. It's a single process that needs to be started, but everytime I enable the resource it keeps stopping and starting it until eventually it goes into maintenance saying "Restarting too quickly, changing state to maintenance".
I have the following in the /lib/svc/method (start) file :
#!/sbin/sh -xv
# Start method script for the xcom service
. /lib/svc/share/smf_include.sh
case "$1" in
'start')
if [ `pgrep xcomd` ]
then
echo "$0: XCOM is already running..."
exit $SMF_EXIT_ERR_NOSMF
fi
if [ -x /etc/xcomd ]
then
echo "Starting XCOM..."
/etc/xcomd
else
echo "XCOM is not installed or not executable..."
exit $SMF_EXIT_ERR_NOSMF
fi
'stop')
if [ `pgrep xcomd` ]
then
echo "Stopping XCOM..."
/etc/xcomd -s
else
echo "XCOM is not running..."
fi
esac
exit $SMF_EXIT_OK
And the following in /var/svc/manifest/application/xcom.xml :
<?xml version='1.0'?>
<!DOCTYPE service_bundle SYSTEM '/usr/share/lib/xml/dtd/service_bundle.dtd.1'>
<service_bundle type='manifest' name='export'>
<service name='application/xcomd' type='service' version='0'>
<create_default_instance enabled='true'/>
<single_instance/>
<dependency name='usr' grouping='require_all' restart_on='none' type='service'>
<service_fmri value='/system/filesystem/minimal'/>
</dependency>
<exec_method name='start' type='method' exec='/lib/svc/method/xcomd %m' timeout_seconds='60'>
<method_context/>
</exec_method>
<exec_method name='stop' type='method' exec='/lib/svc/method/xcomd %m' timeout_seconds='60'>
<method_context/>
</exec_method>
<stability value='Unstable'/>
<template>
<common_name>
<loctext xml:lang='C'>XCOM file transfer program</loctext>
</common_name>
<documentation>
<manpage title='xcomd' section='8'/>
<manpage title='xcomcfg' section='8'/>
</documentation>
</template>
</service>
</service_bundle>
Any ideas where this is going wrong??? I've pulled the manifest file togeher looking at other things so I'm not surprised if there's errors in there. Any help greatly appreciated.

Answer 1

Change the name of the script to be anything other
than 'xcomd' or 'svc-xcomd' and it would work. That's
what I've done now. The start/exec and stop/exec now
call a different script. One problem I had with this
was even though when doing a 'listprop' it showed it
had taken the change, and I'd exported it out to the
manifest file, when trying to enable the resource it
would complain that it couldn't find the old script
[ Feb 15 18:12:53 Executing start method ("/lib/svc/method/svc-xcomd") ]
/sbin/sh: /lib/svc/method/svc-xcomd: not found
[ Feb 15 18:12:53 Method "start" exited with status 1]
Is there a way of refreshing things one you make a
change??? When I'm exiting out I'm either using 'end'
or 'exit'.Yes, you have to run "svcadm refresh xcomd". This is
because svc.startd uses the property values from the
"running" snapshot of the service. svcprop does that by
default as well. A plain listprop in svccfg, though, will only
show you the current values of the properties. (You can use
selectsnap to select the running snapshot and examine its
property values with listprop.) svcadm refresh updates the
running snapshot with the current property values, so that must
be done after changing properties.