Thanks Michael! I appreciate the response.
Oracle seems to have their own special way of doing things, for sure.
On Fri, Mar 31, 2017 at 5:54 PM, Michael Hrivnak
wrote:
> I just looked at the repo, and other.xml is 720MB compressed!!! Wow! I
> wonder what's in there.
>
> For comparison, just fo
I just looked at the repo, and other.xml is 720MB compressed!!! Wow! I
wonder what's in there.
For comparison, just for fun, I checked RHEL 6.8. The other.xml file there
is under 5MB compressed.
The setting to change where the working directory lives is intended to help
in a scenario where you're
>
> The short answer is that if you need to sync Oracle Linux sync one distro
> at a time and leave enough space.
Yes, I understand and suspected as much. My question was primarily about
setting the working_directory setting in server.conf, since this does not
seem to be well documented.
Thanks
>
> This may be unrelated to the sync problem - but do you have the export
> distributor configured on that repo?
Hi Mihai,
No, we aren't using the export distributor - but I'll keep that in mind if
we end up needing it later.
Thanks,
Christina
___
Pul
This may be unrelated to the sync problem - but do you have the export
distributor configured on that repo?
It doesn't affect syncing at all, but there is a publish operation at the
end of the sync. The export distributor tries hard to burn all your CPU
while running mkisofs (for my usecase we don
Hello all,
I am running Pulp 2.9.2. We are facing issues with our /var filesystem
filling up when we do our nightly syncs - in particular, when we sync the
Oracle Linux channel:
http://public-yum.oracle.com/repo/OracleLinux/OL6/latest/x86_64/
Syncing this one repo uses 5+ GB of space on /var whil