Its not the first time the witango installers have had problems, the
5.0 mac installer was broken for a long time.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Mar 16, 2007, at 9:15 AM, Dale Graham wrote:
This is a developer machine, so it doesn't matter. For a server,
I'd need a more robust solution, but I am sure the Witango guys
will be on it... 8)
I think my sys admin got this fixed on my quad processor XServe,
but somehow or other I kept missing some setting/file or whatever
to take the place of the final installs.
On Mar 16, 2007, at 11:46 AM, Robert Garcia wrote:
its been a while for me, running this on os x, but If I remember
correctly, running as witango -u is a good temporary workaround,
but not a good permanent fix. I don't remember all the reasons,
but I do remember that witango runs the way it does, from the
SystemStarter, to be more secure.
Anyway, I would double check on that, sorry I can't remember all
the reasons why. Maybe someone else can chime in.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Mar 16, 2007, at 4:06 AM, Dale Graham wrote:
Thanks for the help from you and from Witango customer support. I
appreciate it, as the Witango server is now running.
Here's the round up so far.
1] The installer fails to run the postinstaller script
This means that all the stuff that needs to be set up like the
Startup and various other file edits does not happen. I figured
that out by myself, BUT had not been unable to manually
reconstruct this sufficiently to make the server run.
That is, I copied over the Startup items directory, checked
permissions on it, etc. Tried it with and without changing /etc/
hostconfig by adding WITANGO=-YES-
no joy
What worked was this advice from the Witango customer support folks
In the terminal, cd to the directory containing witangod
run this command
./witangod -uo
I also found out that you need to start things in the following
sequence
Witangod
Apache2
or else I got a clients.ini error
On Mar 15, 2007, at 10:04 PM, Robert Garcia wrote:
SystemStarter will also work with
WITANGO55=-NO-
Witango just won't start at boot. If this server is a dev
machine, I usually leave it at NO, and only start when I need.
If a server, def make it YES.
--
Robert Garcia
President - BigHead Technology
VP Application Development - eventpix.com
13653 West Park Dr
Magalia, Ca 95954
ph: 530.645.4040 x222 fax: 530.645.4040
[EMAIL PROTECTED] - [EMAIL PROTECTED]
http://bighead.net/ - http://eventpix.com/
On Mar 15, 2007, at 6:38 PM, Customer Support wrote:
For SystemStarter to work you need to have the Witango_5.5 in /
Library/StartupItems and the /etc/hostconfig needs to have
WITANGO55=-YES- in it. You can then use the following system
starter commands
___________________________________________________________________
_____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
____________________________________________________________________
____
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
_____________________________________________________________________
___
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
______________________________________________________________________
__
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
________________________________________________________________________
TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
