Bill,
Looks okay on the -headless argument. I wonder what would happen if you
dropped the -memory statement?
I'm launching my Linux Swikis like this:
./squeak2 -headless Squeak.image &
I made copies of the VM with different names so that they would be unique
in a process list. We run more than one Swiki on the same box.
- Steve
On 4/8/02 7:35 PM, "Bill Denney" <[EMAIL PROTECTED]> wrote:
> This is my command line. The machine has 192M of ram with few other
> services running, and so I don't think that 64M is killing it for memory.
>
> /usr/local/ComSwiki/squeak -headless -memory 64m \
> /usr/local/ComSwiki/squeak.image &
>
> Bill
>
> On Mon, 8 Apr 2002, Stephan B. Wessels wrote:
>
>> What command line are you using to launch this?
>>
>> - Steve
>> On 4/8/02 4:19 PM, "Bill Denney" <[EMAIL PROTECTED]> wrote:
>>
>>> On the system I'm working on, the system has already reached the
>>> responsive state, and it continues to use the entire processor (has been
>>> doing so for ~3 hours now). It is still relatively responsive. I'm
>>> thinking that a poor hack of a fix will be to just renice the process to
>>> about 2 or so if I can't figure something else out.
>>>
>>> Bill
>>>
>>> On Mon, 8 Apr 2002, Pierre Baillet wrote:
>>>
>>>> just as Stephan stated, I have the exactly same behaviour when starting
>>>> the swiki. This startup time seems necessary for the smalltalk vm to
>>>> start well and the swiki is almost unreachable during that time. Then
>>>> the CPU usage drops and everything runs correctly...
>>>
>>> -=- Bill Denney -=- [EMAIL PROTECTED] -=-
>>> Sum ergo cogito.
>>>
>>>
>>
>>
>
> -=- Bill Denney -=- [EMAIL PROTECTED] -=-
> Sum ergo cogito.
>
>
