[pkg-discuss] pkgrecv -c cache size

[shri.k...@oracle.com]

Is there any way to control the size of the cache used by pkgrecv on
space limited systems?

Thanks,

--shri

_______________________________________________
pkg-discuss mailing list
pkg-d...@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/pkg-discuss

[Shawn Walker]

On 02/27/12 23:17, shri.k...@oracle.com wrote:
> Is there any way to control the size of the cache used by pkgrecv on
> space limited systems?

No.

However, it will clear the cache after each package is copied to the
destination repository though. So the maximum size of the repository
should be a few hundred megabytes at the most during operations.

-Shawn

[shri.k...@oracle.com]

On 2/28/2012 7:15 AM, Shawn Walker wrote:
> On 02/27/12 23:17, shri.k...@oracle.com wrote:
>> Is there any way to control the size of the cache used by pkgrecv on
>> space limited systems?
>
> No.
>
> However, it will clear the cache after each package is copied to the
> destination repository though. So the maximum size of the repository
> should be a few hundred megabytes at the most during operations.

I'm seeing my cache at 6GB and growing, effectively doubling my space
requirements,
so I'm not sure if I'm doing something wrong here:

pkgrecv --key key --cert cert -c /var/tmp/cache/mycache -s
https://pkg.oracle.com/solaris/support -d /var/tmp/testrepo -m
all-versions '*'
Processing packages for publisher solaris ...
Retrieving and evaluating 7597 package(s)...
PROCESS ITEMS GET (MB)
SEND (MB)
editor/gnu-emacs/gnu-emacs-gtk 3295/7597 5609.7/14232.5
15160.5/43793.6
system/kernel 3748/7597 6399.2/14232.5
17350.5/43793.6
...

# du -sk /var/tmp/cache/mycache/
6345486 /var/tmp/cache/mycache

# du -sk /var/tmp/testrepo/
6471435 /var/tmp/testrepo

--shri

[Shawn Walker]

On 02/28/12 08:26, shri.k...@oracle.com wrote:
>
>
> On 2/28/2012 7:15 AM, Shawn Walker wrote:
>> On 02/27/12 23:17, shri.k...@oracle.com wrote:
>>> Is there any way to control the size of the cache used by pkgrecv on
>>> space limited systems?
>>
>> No.
>>
>> However, it will clear the cache after each package is copied to the
>> destination repository though. So the maximum size of the repository
>> should be a few hundred megabytes at the most during operations.
>
> I'm seeing my cache at 6GB and growing, effectively doubling my space
> requirements,
> so I'm not sure if I'm doing something wrong here:
>
> pkgrecv --key key --cert cert -c /var/tmp/cache/mycache -s
> https://pkg.oracle.com/solaris/support -d /var/tmp/testrepo -m
> all-versions '*'
> Processing packages for publisher solaris ...
> Retrieving and evaluating 7597 package(s)...
> PROCESS ITEMS GET (MB) SEND (MB)
> editor/gnu-emacs/gnu-emacs-gtk 3295/7597 5609.7/14232.5 15160.5/43793.6
> system/kernel 3748/7597 6399.2/14232.5 17350.5/43793.6
> ...

What OS build are you using? The cache behaviour was changed in later
builds nearer to FCS.

[Shawn Walker]

On 02/28/12 08:26, shri.k...@oracle.com wrote:
>
>

> On 2/28/2012 7:15 AM, Shawn Walker wrote:
>> On 02/27/12 23:17, shri.k...@oracle.com wrote:
>>> Is there any way to control the size of the cache used by pkgrecv on
>>> space limited systems?
>>
>> No.
>>
>> However, it will clear the cache after each package is copied to the
>> destination repository though. So the maximum size of the repository
>> should be a few hundred megabytes at the most during operations.
>
> I'm seeing my cache at 6GB and growing, effectively doubling my space
> requirements,
> so I'm not sure if I'm doing something wrong here:
>
> pkgrecv --key key --cert cert -c /var/tmp/cache/mycache -s
> https://pkg.oracle.com/solaris/support -d /var/tmp/testrepo -m
> all-versions '*'
> Processing packages for publisher solaris ...
> Retrieving and evaluating 7597 package(s)...
> PROCESS ITEMS GET (MB) SEND (MB)
> editor/gnu-emacs/gnu-emacs-gtk 3295/7597 5609.7/14232.5 15160.5/43793.6
> system/kernel 3748/7597 6399.2/14232.5 17350.5/43793.6
> ...

Sorry, I missed that you were specifying your own cache directory.

If you specify your own cache directory, pkgrecv will assume that it
cannot remove any files from the cache specified.

The -c option is not to specify a custom cache directory, it is really
only to resume a large, interrupted transfer operation. pkgrecv(1)
tries to explain this.

As mentioned in pkgrecv(1), if you want to control the default location
of cached data during operations, set TMPDIR in your environment
instead. See pkgrecv(1) ENVIRONMENT VARIABLES for more information.