Ticket #1075 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

Extra services not being turned off

Reported by: Owned by:
Priority: major Milestone: Bcfg2 1.2.1 Release (Bugfix)
Component: bcfg2-client Version: 1.0
Keywords: Cc: [email protected]


I'm running 1.2.0rc2 server/client on RHEL6 machines and am not getting extra services to turn off when requested. I have a few services on a new machine that aren't mentioned in any bundles and are listed as extra with bcfg2 -q -v -n -e, but trying to remove them with bcfg2 -q -v -I -r all prompts me for removal, but doesn't appear to actually do anything. After running, the services remain. Note that these services aren't mentioned anywhere in my configs - they just came with packages, but I want them off without needing to hunt for them.


Change History

comment:1 Changed 11 years ago by solj

After thinking about this more, I think I see where this would be a problem. What exactly does service removal mean? To me, it would mean removing the service completely (i.e. rm /etc/init.d/foo). But that would mean the package that provides this service would no longer verify properly. What exactly are you wanting the client to do in this case?

comment:2 Changed 11 years ago by

In my opinion, "removing" a service should just shut it off. The package manager should be the manager of the service's files, and bcfg should be the manager of whether or not it is running. This way I can install a package that includes a service and know that unless I explicitly say I want its service running, then it will be turned off without me needing to periodically see what new services I might have gained on running machines.

comment:3 Changed 11 years ago by

Well, I guess "stop it and then chkconfig it off" is more specific.

comment:4 Changed 11 years ago by solj

  • Milestone changed from Bcfg2 1.2.0 Release to Bcfg2 1.2.1 Release (Bugfix)

comment:5 Changed 11 years ago by

  • Owner changed from desai to
  • Status changed from new to assigned

comment:6 Changed 11 years ago by

  • Status changed from assigned to closed
  • Resolution set to fixed

WARNING! You need to establish a session before you can create or edit tickets. Otherwise the ticket will get treated as spam.


Add a comment

Modify Ticket

Change Properties
<Author field>
as closed
The resolution will be deleted. Next status will be 'reopened'

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.