I appreciate everybody's help and quick responses to this problem,
unfortunately I still don't have a working solution.
I've tried both of these settings in the .xml file
<property_group name='startd' type='framework'>
<propval name='duration' type='astring' value='child' />
<propval name='ignore_error' type='astring' value='core,signal' />
</property_group>
and
<property_group name='startd' type='framework'>
<propval name='duration' type='astring' value='child' />
</property_group>
Deleting the service, and re-importing the xml file each time.
I also set stunnel to run in the foreground.
% ps -ef | grep stunnel
root 4678 7 0 08:24:06 ? 0:00 /sbin/sh
/lib/svc/method/stunnel-4-syslog start
nobody 4682 4678 0 08:24:06 ? 0:00 /usr/local/sbin/stunnel
/usr/local/etc/stunnel/stunnel-4-syslog.conf
I've also tried:
<exec_method
type='method'
name='start'
exec='/usr/local/sbin/stunnel /usr/local/etc/stunnel/stunnel-4-syslog.conf
|| exit $SMF_EXIT_ERR_FATAL'
timeout_seconds='60'/>
and
exec='/usr/local/sbin/stunnel /usr/local/etc/stunnel/stunnel-4-syslog.conf &&
exit $SMF_EXIT_ERR_FATAL'
and
exec='/usr/local/sbin/stunnel /usr/local/etc/stunnel/stunnel-4-syslog.conf ;
exit $SMF_EXIT_ERR_FATAL'
I've also tried all 3 exec methods in the startup script so that the exec is
the normal "script start" and in the script it will run:
/usr/local/sbin/stunnel /usr/local/etc/stunnel/stunnel-4-syslog.conf || exit
$SMF_EXIT_ERR_FATAL
All settings allow the service to start successfully. But killing the service
results in SMF successfully restarting stunnel.
There was one configureation option that I tried that started the service but
reported it as in "maintenance" even though it was running as expected.
I'm still holding to my logic. The param states to "start the service
[b]or[/b] fail with exit code" Since the service is starting successfully the
[b]or[/b] never happens. At least thats how it looks in my head.
I'm not giving up yet and if there is something else that I'm missing please
let me know. I can post the entire xml file, startup script, and logs if that
will help.
This message posted from opensolaris.org
