Forum Replies Created

Viewing 15 posts - 106 through 120 (of 125 total)
  • Author
    Posts
  • in reply to: OSSuite Enterprise Software #356024
    ElgertS
    Participant

    Step 4: Permissions and Links

    Now that the application is installed, we must verify permission settings and symbolic links required for full functionality.

    Within the terminal change your location to the virtual host directory and make the following permission changes:

    chmod -R 755 ossuite
    chmod -R 777 ossuite/images
    chmod -R 777 ossuite/logs
    chown -R root ossuite

    There should be several symbolic links configured already, but you need to verify these are all in place. I found some folders and links missing during my installation and had to create them. For me these were the “images” and the “logs” folders. Since these folders were missing I had to create several of the symbolic links while other links were already in place.

    cd /ossuite/oserp
    ln -s ../images images
    ln -s ../uploads images

    cd /ossuite/oscatalog
    ln -s ../images images

    cd /ossuite/osadmin
    ln -s ../images images

    in reply to: OSSuite Enterprise Software #356023
    ElgertS
    Participant

    Step 3: Install OSSuite

    Download the source for installation:

    http://sourceforge.net/project/showfiles.php?group_id=65144&release_id=167102

    If Stuffit has not already done the job for you, decompress the archive:

    tar -zvxf ossuitev101.tar.gz

    This will create a folder called ossuite with many files and subdirectories. Move the entire ossuite folder to the virtual host directory from which you want to host the application.

    in reply to: OSSuite Enterprise Software #356022
    ElgertS
    Participant

    Step 2: Verify register_globals is turned on within PHP.

    Notes: by default PHP 4.3.2 ships with register_globals turned off for heightened security. While it is far more attractive to leave this feature off, OSSuite and many other PHP applications have not been updated to support the new register_globals off configuration.

    Within the PHP.ini file (located within /Library/PHP4/lib) do a search for register_globals and change it to “On”.

    in reply to: OSSuite Enterprise Software #356021
    ElgertS
    Participant

    Step 1: Installation of support packages.

    OSSuite 1.0.2 requires installation of the following support software packages. I have separated the first three from the rest of the crowd. OpenSSL and curl come already installed on OS X Server. GD comes as a standard library within PHP 4.3.2. The remaining libraries must be installed individually on OS X Server 10.2.

    Open_SSL 0.9.6g http://www.openssl.org
    Curl 7.10 http://curl.haxx.se
    GD 1.8.4 http://www.boutell.com/gd

    Pdflib 4.0.3 http://www.pdflib.com
    Mcrypt 2.6.3 http://mcrypt.hellug.gr
    Mhash 0.8.17 http://mhash.sourceforge.net
    Libmcrypt 2.5.3 http://mcrypt.hellug.gr/#_libmcrypt
    Libpng 1.2.5 http://www.libpng.org/pub/png/libpng.html
    JPegsrc 6b http://www.optix.org/~dxy/solaris/jpegsrc
    Tiff v3.5.7 http://www.libtiff.org
    Zlib 1.1.4 http://www.gzip.org/zlib

    Notes: most of these libraries will install with little or no problem with just a few exceptions. Libmcrypt must be installed prior to installation of Mcrypt. Pdflib comes in either a light open source version or a full commercial release. To use the open source version, download both PDFliblite and the full PDFllib demo. The full PDFlib contains a binary extension for PHP that must be placed in the PHP extensions directory located at /Library/PHP4/lib. The PHP.ini file, located in the same directory, must be altered by adding the following two lines of instructions:

    [PDFLib]
    extension = libpdf_php.so

    At this point you can compile the source for PDFliblite which will then include support for PHP.

    in reply to: Sympa Mailing List manager #356017
    ElgertS
    Participant

    Step 6: Configure startup scripts

    The instructions for Sympa suggest altering /etc/rc.local. Mac OS X doesn’t use this so I would imagine a startup item would be most appropriate to launch the following items:

    ~sympa/bin/sympa.pl
    ~sympa/bin/archived.pl
    ~sympa/bin/bounced.pl
    ~sympa/bin/task_manager.pl

    in reply to: Sympa Mailing List manager #356016
    ElgertS
    Participant

    Step 5: Create Sympa database in MySQL

    Create a database named “sympa” in MySQL. When the Sympa perl script is first launched it will populate this with the appropriate tables.

    in reply to: Sympa Mailing List manager #356015
    ElgertS
    Participant

    Step 4: Install Sympa

    The installation is a standard Unix compile operation.

    http://www.sympa.org/distribution/sympa-3.4.4.1.tar.gz

    The instructions suggest you copy the source to the sympa home drectory as such:

    /home/sympa/src

    unless Stuffit has taken care of it already:

    gzip -dc sympa-3.4.4.1.tar.gz | tar xf –

    followed by:

    $ ./configure
    $ make
    $ make install

    in reply to: Sympa Mailing List manager #356014
    ElgertS
    Participant

    Step 3: Create user and group

    Sympa needs to have a user and a group, both of which are suggested to be “sympa”. They prefer the user’s home directory be /home/sympa.

    in reply to: Sympa Mailing List manager #356013
    ElgertS
    Participant

    Step 2: CPAN modules

    Sympa relies on a wide variety of CPAN modules. Some of these will already be installed. Many of those not installed will install easily via CPAN. In my installation, I found several that would not install well under CPAN and had to be installed manually. The following is the order I was able to install the CPAN modules along with the methodology required for each:

    NET::LDAP – CPAN standard install
    CGI – updated within CPAN
    Encode – updated within CPAN
    Net::FTP – CPAN standard install
    Net::LDAP – CPAN standard install
    MIME::Tools – CPAN standard install
    Crypt::CipherSaber – CPAN standard install
    FCGI – CPAN standard install
    MIME::Base64 – CPAN standard install
    DBI – CPAN standard install
    LWP – had to force install within CPAN
    DBD::mysql – would not install through CPAN as it tests itself after install using demo user and password against a demo database. This would only work if these settings were valid. Had to download manually and edit the file to have valid authentication and db information. After this change, module installed without a problem.
    IO::Socket::SSL – CPAN standard install
    Net::SSLeay – CPAN standard install
    MHonArc – manually installed
    suidperl – I was not able to install this file as I have not yet located its installer. It is required by the web interface. If anyone has ideas on how to install this module I would be extremely interested.

    in reply to: Sympa Mailing List manager #356012
    ElgertS
    Participant

    Step 1: Berkeley DB

    Apple ships Mac OS X Server 10.2 with Berkeley DB installed. Unfortunately, the release is not current and it has serious bugs in it. It is necessary to upgrade to the latest release.

    http://www.sleepycat.com/update/snapshot/db-4.1.25.tar.gz

    in reply to: Instructions in progress forum #355981
    ElgertS
    Participant

    I would love to help out in any way towards such an effort. I am glad to hear you thought it was a positive concept. Let me know how you would like to move forward with it.

    in reply to: Waiting for NetInfo #355971
    ElgertS
    Participant

    Have you changed your IP address since first configuring the server?

    in reply to: Sympa Mail List Software #355944
    ElgertS
    Participant

    If anyone can also tell me what information needs to be done in Exim I would very much appreciate it. Looking at the Mailman instructions there appears to be quite a bit of work which I don’t have a grasp of.

    Thanks!

    in reply to: CPAN not installing modules for Amavis #355933
    ElgertS
    Participant

    I believe I have installed all the required modules for Amavis now. I had to manually install some and a few had to be forced.

    in reply to: CPAN not installing modules for Amavis #355927
    ElgertS
    Participant

    I have worked for several more days on my CPAN sorrow. After reconfiguring it a few times and fighting with things to download I was able to get most of the modules loaded. The remaining two that Amavis demands are Compress::Zlib and Archive::Zip (which depends on Compress::Zlib). Also, by doing the “r” command to get a list of modules that should be updated I get four that are outdated, but get errors when I try to load them. Previously this list was around 12 but I have managed to get most to load. Some of the failures express known incompatibiliities with the Berkeley DB that ships wtih Mac OS X 10.2. I therefore loaded the latest release in hopes of solving the problem. It installed fine, but the problems remain.

Viewing 15 posts - 106 through 120 (of 125 total)