HEHE i never imagine such a discussion for "simple" question I made/..
Its good to read all what people think.
So far then I need no mod in the server because its a G% OS X server,
but we are thinking that this computer a mac pro, its on the end of
life, so we are figuring out to move to a linux box PITA first time I
tried....
PS:
Damn will be good that apple release an aluminiun keboard with backlit.
On Sep 2, 2009, at 5:43 PM, Mike Schrag wrote:
I wrote that years ago and lost a lot of time trying to find out
why
everything stopped working. It was certainly true at the time. I
have
no idea about now. I think it's much nicer to stop using global
WebObjects.properties files for properties on particular servers
and
to use per user files like Properties.wolive and
Properties.wostaging.
I guess that requires using Wonder.
Sure, but it's the same kind of stupid that doesn't really allow
you to add WOPort=1234 into you WebObjects.properties. wotask will
pick that up and also start on this port.
So basically, IMO wotaskd would need to ignore WO.properties
alltogether.
I'm totally on-board with how ~/WO.properties works -- it's global.
If you set a global port, everything should get it, wotaskd
included. You should just never use it. Problem solved.
ms
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/webobjectspicora%40gmail.com
This email sent to [email protected]
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com
This email sent to [email protected]
