I see your point, but we are working in a collaborative
environment, and the node ops time is important too.
Maybe less that the core developers one, but still important.
This is the Stable release, and 5087
is crap^h^h^h^h er... unworkable.
... the user too deserve some attention when
Just to sing a different tune than the one everyone else is
singing, I upgraded to 5088 last night and it seems to work
relatively well. The load is considerably higher than with
5084 and the same configuration but, as far I can see without
studying logs, everything works as it should. Perhaps
What does the message 'CANNOT RENAME NODE FILE node-temp TO node' suggest ?
stable build 5088 / Linux kernel 2.6.7 / Sun
Java HotSpot(TM) Client VM (build 1.4.2_04-b05, mixed mode)
ciao
--klaus
___
Support mailing list
[EMAIL PROTECTED]
On Thu, Jul 29, 2004 at 07:35:06PM -0400, [EMAIL PROTECTED] wrote:
man... the recent changes knocked me right off the network.
Had it working in OSX for a bit using an old version
What happens exactly? RNFs? How many connections are open?
Trying in Linux, firewall on/off nothing seems to
I posted same message on devel list by mistake...
Addresses detected by network section of the Environment page says this:
IPv4: 192.168.0.30 1
IPv4: xxx.xxx.xxx.xxx 81
The address on the second line is my address, but the address on the first line
has never been my address. What is
