On 03/24/10 02:18 PM, Girish Moodalbail wrote:
> On 03/24/10 17:17, Dave Miner wrote:
>> On 03/24/10 04:31 PM, Girish Moodalbail wrote:
>>> Folks,
>>>
>>> Could somebody please let me know the memory requirements to run DC?
>>>
>>> distro_const has already failed on me several times since morning, due
>>> to memory issues. I am running on a system with 2GB physical memory.
>>> Does it require more than that?
>>>
>>> I see following messages on the terminal:
>>>
>>> bash: fork: retry: Resource temporarily unavailable
>>> bash: fork: retry: Resource temporarily unavailable
>>> bash: fork: retry: Resource temporarily unavailable
>>> bash: fork: retry: Resource temporarily unavailable
>>> bash: fork: Resource temporarily unavailable
>>> bash: fork: retry: Resource temporarily unavailable
>>> bash: fork: retry: Resource temporarily unavailable
>>> bash: fork: retry: Resource temporarily unavailable
>>> bash: fork: retry: Resource temporarily unavailable
>>>
>>> and in the detail log, I see
>>>
>>> pkg: There is not enough memory to complete the requested operation. At
>>> least
>>> 475MB of virtual memory was in use by this command before it ran out of
>>> memory.
>>> You must add more memory (swap or physical) or allow the system to
>>> access more
>>> existing memory, or quit other programs that may be consuming memory,
>>> and try
>>> the operation again.
>>>
>>
>> The message actually indicates it's pkg that is running out of 
>> memory, so this is somewhat out of DC's control.  This has been an 
>> issue with upgrades on smaller machines recently, but first I've 
>> heard of DC running out.
>>
>>> The document here
>>> http://dlc.sun.com/osol/docs/content/dev/DistroConst/docinfo.html
>>> doesn't talk about 'memory' requirements.
>>>
>>
>> Typically, there aren't, but then again it mostly gets run on build 
>> machines that have a lot more memory than 2 GB.  I'd try adding swap, 
>> getting rid of other big processes that may be running as well, or 
>> use a bigger machine.
>
> Thank you all. I will move to more powerful machine and retry.

Part of the problem may be that DC manifests still use the "old style" 
pkg names, so the pkg commands have to do a lot of extra work to 
translate those into new names during the DC run. You may consider 
manually modifying the pkg= lines to use the new hierarchical names to 
see if that helps.

- Keith

>
> thanks
> ~Girish
> _______________________________________________
> caiman-discuss mailing list
> caiman-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss

Reply via email to