Well Bill, it looks as if you have tried all the "easy stuff". Let's try some other ideas. Could it be data related? For example, move all of the swikis out of the swiki directory except for the original distribution and launch it virgin. Or is that the case already and you don't have any existing swikis being opened?
What about the image? There's a couple of things to look at, just first thoughts. Is there a debug log getting generated and I wonder how large it is (a recursive error being trapped perhaps?). Is the image clean? In other words, is there any possibility that something else is running? You mentioned in an earlier message that your swiki would stay in this state for longer than even 3 hours. Does it ever operate? That is, while all this busy-ness (sp?) is going on does the admin page come up from a Browser? Do you get the same behavior using another port? I'm wondering what other kind of troubleshooting has been done and mostly, if the swiki is even serving pages or not while all this is going on. - Steve On 4/8/02 10:36 PM, "Bill Denney" <[EMAIL PROTECTED]> wrote: >> Looks okay on the -headless argument. I wonder what would happen if you >> dropped the -memory statement? > > I changed the command from > > /usr/local/ComSwiki/squeak -headless -memory 64m \ > /usr/local/ComSwiki/squeak.image & > > to > > /usr/local/ComSwiki/squeak -headless \ > /usr/local/ComSwiki/squeak.image & > > with no effect on the processor usage. > > I also tried changing the squeak executable from version 3.0 that comes > with the swiki to version 3.1beta. This did not change the processor > usage either. > > Bill > > -=- Bill Denney -=- [EMAIL PROTECTED] -=- > Sum ergo cogito. > >
