[OGo-Users] Startup script for CentOS?

[Ben Trafford]

At 09:45 AM 2/14/2008, Adam Tauno Williams wrote:
>I'm confused.  PostgreSQL and Apache startup scripts are provided by
>their respective packages.  You just enable those in the normal manner;
>just chkconfig postgresql on; chkconfig httpd2 on; and PostgreSQL and
>Apache will start when the system boots.

         Y'know, people might be a lot more inclined to use OGo if 
they got less yelled at and more helped when they asked questions. As 
it is, I'm about an inch away from just telling my company to go with 
MS-Exchange for our needs.

         Yes, I'm aware of how to make Apache and PostgreSQL start. 
What is less than clear is which order to start ogo-*.

>You want a startup script but "rather than go through the effort" of
>using the script provided in the CentOS packages you want a startup
>script???  What are you actually trying to accomplish, because this
>doesn't make any sense?

         I'm trying to start the application from one init.d script, 
instead of several.

>Documentation is not lacking -
>http://docs.opengroupware.org/Members/whitemice/wmogag/file_view
>  - and even the presentation [linked to from the *HOME PAGE*] enumerates
>what is required (PostgreSQL, Cyrus, Apache, & some MTA) and the general
>setup procedure.

         Oh -really-?

         Go to http://www.opengroupware.org. Click on "Docs". In 
"Docs," click on "Plone Manual Site." You go...-nowhere-! This is 
because the link in the docs area is different than the links on the 
sidebar. Many reasonable users will go to the documentation overview 
to see what's available, and then click on that link, and find nothing.

         So, let's say I actually figure out that the link is 
different in two locations, and find the right link for the Plone. 
Aha! I'm on the front page. Look! A link to an OGo user guide!

         Oh, wait. It doesn't work, either.

         Well, let's click on "All Docs." Oh, grand. Ten+ pages of results.

         It is, at this point, that a reasonable user will go to the 
mailing list, because figuring out how to get the application to run 
should not involve debugging the OGo site, or, alternately, digging 
through ten+ pages of documentation titles to find the one I'm looking for.

         Ergo -- the documentation is lacking.

--->Ben