Bug 1272907 - samba: After making changes to configuration file and then doing an yum update the back up of configuration (rpmsave) file is not created along with a new smb file
Summary: samba: After making changes to configuration file and then doing an yum updat...
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: samba
Version: rhgs-3.1
Hardware: x86_64
OS: Unspecified
Target Milestone: ---
: ---
Assignee: rhs-smb@redhat.com
QA Contact: storage-qa-internal@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2015-10-19 07:59 UTC by Vivek Das
Modified: 2015-10-19 12:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2015-10-19 12:48:18 UTC
Target Upstream Version:

Attachments (Terms of Use)

Description Vivek Das 2015-10-19 07:59:00 UTC
Description of problem:
After yum update of samba there is no new configuration file as well as there is no rpmsave back up file of the configuration file. There was difference in smb.conf file so it is expected to keep a back up and create a new file.

Version-Release number of selected component (if applicable):
samba 4.2.4

How reproducible:

Steps to Reproduce:
1.On samba 4.1 create a share on smb.conf
2.yum update
3.ls -l /etc/samba

Actual results:
No new smb configuration file and no rpmsave of configuration file is present

Expected results:
As there is a difference is configuration file so after yum update smb.conf.rpmsave file should be present along with new smb.conf.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.