#48248 lib389 - create ldif creation function that properly sets the ownership
Closed: wontfix Opened by mreynolds.

Add a function to create an ldif using db-gen.pl that also sets the ownership of the new ldif file to match the user that the DS runs as, as opposed to the user that is running the script.


{{{
os.chmod(ldif_file, 0o777)
}}}
I think it should be 0644

note that if you are running this as non-root, you will not be able to chown

Replying to [comment:3 rmeggins]:

{{{
os.chmod(ldif_file, 0o777)
}}}
I think it should be 0644

note that if you are running this as non-root, you will not be able to chown

Yeah nice catch. New patch attached.

{{{
os.chmod(ldif_file, 0o644)
}}}
Do you really need the "o" between the "0" and the "644"? That looks wrong to me.

Replying to [comment:5 rmeggins]:

{{{
os.chmod(ldif_file, 0o644)
}}}
Do you really need the "o" between the "0" and the "644"? That looks wrong to me.

It's for python 3 compliance, and python 2.7 handles it correctly.

To ssh://git.fedorahosted.org/git/389/lib389.git
6847117..49f1155 master -> master
commit 49f11558c761a419540b5d34f840055132026505
Author: Mark Reynolds mreynolds@redhat.com
Date: Thu Aug 13 16:12:23 2015 -0400

Updated 389-ds-base testsuite

To ssh://git.fedorahosted.org/git/389/ds.git
70ccd9b..dfb1c31 master -> master
commit dfb1c315d009e7a4c6798a7ae05f139b77d506dc

c16382c..7ea4487 389-ds-base-1.3.4 -> 389-ds-base-1.3.4
commit 7ea4487f81aec3aef17c82d20f6067fa36c1cf7c

20f6bc6..dc22924 389-ds-base-1.3.3 -> 389-ds-base-1.3.3
commit dc2292408a571c488a78ded4f1c37ff5e445625c

Milestone lib389 1.0 deleted

Metadata Update from @mreynolds:
- Issue assigned to mreynolds

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/1579

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

Metadata