Hi!
It depends a lot on your network infra-structure. Some network
switches may only allow you to communicate after 30 seconds (it has
something to do with spanning trees, don't know the detail). Also,
some switches may be slower negotiating network speed.
Also, if you have many CPUs/
On Aug 24, 2007, at 7:11 PM, Galen Rhodes wrote:
I have a 8-core Mac Pro running OS X server and had to set it to
sleep 20.
BUT! I don't think the speed of the machine itself is all of the
equation. If you think about it, everything should be faster too
including bringing up the network
I have a 8-core Mac Pro running OS X server and had to set it to
sleep 20.
--
Galen Rhodes
[EMAIL PROTECTED]
On Aug 24, 2007, at 5:23 PM, Miguel Arroz wrote:
Hi!
On 2007/08/24, at 20:29, Art Isbell wrote:
With no WO startup item script on OS X Server, "sleep 5" should
be added as the f
Hi!
On 2007/08/24, at 20:29, Art Isbell wrote:
With no WO startup item script on OS X Server, "sleep 5" should be
added as the first statement in the /System/Library/WebObjects/
JavaApplications/wotaskd.woa/wotaskd shell script.
On our G5 xServe, I had to raise the 5 seconds limit. Intel
Hello,
OK, updated w/ all the details:
http://en.wikibooks.org/wiki/Programming:WebObjects/
Web_Applications/Deployment/Tomcat_Deployment_Details
Paul Charles Leddy
[EMAIL PROTECTED]
IT/NOC
Systems Administration and Engineering
On Aug 21, 2007, at 5:50 PM, Paul Charles Leddy wrote:
Hel
On Aug 24, 2007, at 10:00 AM, Chuck Hill wrote:
Yes, that was it! Thank you. I was struggling to recall the
details of Cliff's fix.
Thanks for reminding me of Cliff's fix. In my early morning
(Hawaiʻi) grogginess, my brain hadn't retrieved that bit of data.
Aloha,
Art
___
On Aug 24, 2007, at 12:29 PM, Art Isbell wrote:
On Aug 24, 2007, at 8:53 AM, Chuck Hill wrote:
Is the the problem that Cliff posted a fix for?
If the ownership and permissions are correct, that would be the
next suspect.
The new machines are so fast that WO starts before the network
On Aug 24, 2007, at 8:53 AM, Chuck Hill wrote:
Is the the problem that Cliff posted a fix for?
If the ownership and permissions are correct, that would be the next
suspect.
The new machines are so fast that WO starts before the network
interfaces are initialized leading to its failure.
Is the the problem that Cliff posted a fix for? The new machines are
so fast that WO starts before the network interfaces are initialized
leading to its failure. Cliff's solution was to put a sleep in the
startup script for WO.
Chuck
On Aug 24, 2007, at 11:51 AM, Art Isbell wrote:
On
On Aug 24, 2007, at 8:35 AM, Jeremy Matthews wrote:
We noticed that after rebooting the intel xserves, you get the
"Cannot find the specified application", when attempting to connect
to the woapp...and looking at the lists of hosts, it says the IP
address is "unspecified". DNS is DEFINITELY
Recently we added 3 intel xserves to a location...added a wo app
(Traditional WO Deployment)...running 5.3.3 WO and 10.4.10 Intel
Xserves, fully patched.
We noticed that after rebooting the intel xserves, you get the
"Cannot find the specified application", when attempting to connect
to t
11 matches
Mail list logo
