Modify ↓
Ticket #587 (closed defect: fixed)
New service spec'ed in Bundle doesn't get started immediately
Reported by: | [email protected]… | Owned by: | desai |
---|---|---|---|
Priority: | critical | Milestone: | Bcfg2 0.9.6 Release |
Component: | bcfg2-client | Version: | 0.9.x |
Keywords: | service bundle | Cc: |
Description
If I specify a service in a Bundle:
<Bundle name='syslog-ng' version='2.0'> <Group name='basic'> <ConfigFile name='/etc/syslog-ng/syslog-ng.conf'/> <Package name='syslog-ng'/> <Service name='syslog-ng'/> </Group> </Bundle>
and the associated status attribute in a Svcmgr file:
... <Service name='syslog-ng' status='on'/> ...
the init script is added to rc via the chkconfig cmd but the service is not started. It only starts once I've changed run levels. I've confirmed this behavior with 0.9.5.7 on RHEL 5.1 and solj has seen it on debian as well. This is especially annoying when adding a brand new bundle/service since I cant work around it by touching a config file.
-cj
Attachments
Change History
comment:1 Changed 14 years ago by cjherman <[email protected]…>
comment:2 Changed 14 years ago by desai
- Status changed from new to closed
- Resolution set to fixed
- Milestone set to Bcfg2 0.9.6 Release
Resolved in [869e7596ca805151b049c1034e4e5a58a67c73ac] (SVN r4940)
Note: See
TracTickets for help on using
tickets.
As per Desai's suggestion, I've added the supervised attribute to the service and moved it all into a Rules/basic.xml file:
I am seeing some different, but still incorrect behaviour: