On 02/10/2015 09:16 AM, Alberto Ruiz wrote: > On Tue, 2015-02-10 at 14:38 +0100, Marek Skalický wrote: >> Matthew Miller píše v Út 10. 02. 2015 v 06:19 -0500: >>> On Tue, Feb 10, 2015 at 12:12:15PM +0100, Marek Skalický wrote: >>>> does someone know what are Fedora Guidelines (or something similar) >>>> saying about this bug >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1077369 ? >>>> Is is possible to change default configuration file depending on >>>> available free space? >>> >>> Generally, making such a decision at install time is bad, because that >>> might not reflect _runtime_. For example, in the cloud image, we use a >>> / filesystem as small as Anaconda will allow, but that grows to fill >>> available storage when the image is booted. >>> >>> Is there a way to make this decision when mongodb runs? >>> >> >> It should be possible to code this into sysv init script. But I am not >> sure if it is possible to do the same in systemd service...? >> >> My question was also about whether this should be done by mongoDB? Or >> there should be default configuration and user can easily change it in >> configuration file? > > It should be done by MongoDB, I would get in touch with the upstream and > discuss the problem with them. > >> Marek I don't think there should be run- *or* install-time determination on this. Smallfiles is used for more than just free space reasons and only the end operator knows whether they need it or not. There's a documented upstream default, and it's the operator's job to change it if they need to. -- Ryan Brown / Software Engineer, Openstack / Red Hat, Inc. -- devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/devel Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
