Custom Query (894 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (43 - 45 of 894)

Ticket Owner Reporter Resolution Summary
#658 desai somekool <[email protected]…> wontfix the "proactive" mode should not be the default
Description

running the bcfg2 client should not be destructive by default.

it could be either interactive or error out asking the user to specify a mode

-n (no) / -I (interactive) / -y (yes/proactive)

#659 desai somekool <[email protected]…> fixed the prune option in a directory should work for reporting as well
Description

at the moment, using the prune attributes in a directory tag such as ...

<Directory name="/etc" prune="true" />

... only cause all unmanaged files to be deleted on my system when running the client.

i would expect it to create extra-configfile items in the reporting databases when running the client with -n or -I

thanks

#660 desai somekool <[email protected]…> fixed being able to whitelist an item for a specific reason.
Description

I have made myself a function that reads the fields in the reports_reason table row to determine a "cause" for the bad item.

  def cause
    case
    when (not(current_exists))
      "Missing"
    when !(current_version.empty? and version.empty?)
      "Version"
    when !current_diff.empty?
      "NDiff"
    when !(current_owner.empty? and current_group.empty? and current_perms.empty?)
      "File attributes"
    when current_status.to_s == "on"
      "Unrequired Service"
    when current_status.to_s == "off"
      "Service down"
    when !current_status.empty?
      "Status problem"
    when !(current_to.empty? and to.empty?)
      "To"
    else
      "Unknown"
    end
  end

I wish I could set whitelist element to act upon this cause. for example, I want to install all missing packages but I do not want to upgrade any package that would be bad per version.

missing configfile could also be install harmlessly but I do not want to overwrite configfile for those I have a diff entry in the reason table.

and so on.

thanks

Note: See TracQuery for help on using queries.