Page 3 of 7 FirstFirst 12345 ... LastLast
Results 21 to 30 of 61

Thread: My Notes for Installing Zimbra OSE on Ubuntu Server 10.04 LTS

  1. #21
    LHammonds's Avatar
    LHammonds is offline Special Member
    Join Date
    Sep 2011
    Location
    Texas
    Posts
    150
    Rep Power
    3

    Default

    Mailbox Size Notifications

    My company wants end-users to be notified when their mailbox is approaching a certain size but does not want an functionality to be diminished if maximums are exceeded. So this calls for a custom script to check mailbox sizes and send notifications. However, they also want certain people to have different limitations than the masses and some people completely excluded from any warnings.

    This solution calls for a quota definition file to handle special cases. Anyone not in the quota file will be handled using system-wide default values. Here is a sample of the quota definition file:

    /var/scripts/data/quota-data.txt
    Code:
    ;AccountName, WarningSizeInMB, MaxSizeInMB, Exempt?
    ceo@mydomain.com, 0, 0, Y
    cio@mydomain.com, 0, 0, Y
    hr@mydomain.com, 270, 300, N
    webmaster@mydomain.com, 360, 400, N
    boss@mydomain.com, 180, 200, N
    In the above sample, the CEO and CIO are exempt from notifications and thus, will never be warned about mailbox size usage.
    The HR person will receive warning messages when the mailbox size is between 270MB and 300MB. Once the mailbox is over 300MB, the message will turn into an alert message with slightly different text.
    The webmaster will receive warnings between 360MB and 400MB and alerts over 400MB.
    The boss will receive warnings between 180MB and 200MB and alerts over 200MB.

    Here is a sample warning message:
    Code:
    From: admin@mydomain.com
    To: lhammonds@mydomain.com
    Sent: Saturday, May 5, 2012 11:21:12 AM
    Subject: WARNING: Mailbox size
    
    Your mailbox size is about to reach the maximum limit. Please delete or archive messages to reduce the size of your mailbox.
    
    Mailbox size = 200MB.  You have 50MB before you reach the maximum of 250MB.
    Here is a sample alert message:
    Code:
    From: admin@mydomain.com
    To: lhammonds@mydomain.com
    Sent: Saturday, May 5, 2012 10:48:47 AM
    Subject: ALERT: Mailbox full
    
    Your mailbox has reached the maximum limit. Please delete or archive messages to reduce the size of your mailbox.
    
    Mailbox size = 200MB.  You are 50MB over the maximum of 150MB.
    Here is the code for the notification script:

    /var/scripts/prod/mailbox-size-notification.sh
    Code:
    #!/bin/bash
    #############################################
    ## Name          : mailbox-size-notification.sh
    ## Version       : 1.0
    ## Date          : 2012-05-04
    ## Author        : LHammonds
    ## Purpose       : Check mailbox size usage.
    ## Compatibility : Verified on Ubuntu Server 10.04.4 LTS, Zimbra 7.2.0 OSE
    ## Requirements  : Must be run as root user
    ## Run Frequency : As needed.  Recommend once per day.
    ## Parameters    : None
    ## Exit Codes    :
    ##    0 = Success
    ##    1 = Failure
    ################ CHANGE LOG #################
    ## DATE       WHO WHAT WAS CHANGED
    ## ---------- --- ----------------------------
    ## 2012-05-04 LTH Created script.
    #############################################
    
    ## Import common variables and functions.
    source /var/scripts/common/standard.conf
    
    ## Define local variables.
    LOGFILE="${TEMPDIR}/mailbox-size-notification.log"
    DATAFILE="${SCRIPTDIR}/data/quota-data.txt"
    ACCTFILE="${TEMPDIR}/mailbox-size-notification-accts.txt"
    ## Default minimum threshold in MB when email notifications start getting sent.
    DefaultMin=180
    ## Default maximum mailbox size in MB (fake limit).
    DefaultMax=200
    DefaultExempt="N"
    ## Convert bytes to megabytes.
    ConversionMultiplier=1048576
    ConversionUnit="MB"
    ReturnCode=0
    ErrorFlag=0
    ## Message to send when mailbox is over the threshold but under the max.
    WarningMessage="Your mailbox size is about to reach the maximum limit. Please delete or archive messages to reduce the size of your mailbox."
    ## Message to send when mailbox is over the max.
    AlertMessage="Your mailbox has reached the maximum limit. Please delete or archive messages to reduce the size of your mailbox."
    
    echo "`date +%Y-%m-%d_%H:%M:%S` - Quota check started." >> ${LOGFILE}
    ## Build a list of user accounts and their mailbox size.
    su - zimbra -c "zmprov gqu ${MYDOMAIN}" > ${ACCTFILE}
    ReturnCode=$?
    if [ ${ReturnCode} -ne 0 ]; then
      echo " ERROR: zmprov return code was ${ReturnCode}" >> ${LOGFILE}
      echo "`date +%Y-%m-%d_%H:%M:%S` - Quota check aborted." >> ${LOGFILE}
      exit 1
    fi
    if [ ! -s "${ACCTFILE}" ]; then
      echo " ERROR: Account listing file is empty." >> ${LOGFILE}
      echo "`date +%Y-%m-%d_%H:%M:%S` - Quota check aborted." >> ${LOGFILE}
      exit 1
    fi
    while read AcctLine
    do
      ## Loop through each mailbox account.
      AcctName=`echo ${AcctLine} | cut -d ' ' -f1`
      AcctSize=`echo ${AcctLine} | cut -d ' ' -f3`
      AdjAcctSize=$((${AcctSize}/${ConversionMultiplier}))
      QuotaData=`grep ${AcctName} ${DATAFILE}`
      if [ -z "${QuotaData}" ]; then
        ## Set variable as if it were read from the file but using defaults.
        QuotaData="${AcctName} ${DefaultMin} ${DefaultMax} ${DefaultExempt}"
      fi
      ## Obtain quota values and exemption info.
      QuotaMin=`echo ${QuotaData} | cut -d ' ' -f2`
      QuotaMax=`echo ${QuotaData} | cut -d ' ' -f3`
      QuotaExempt=`echo ${QuotaData} | cut -d ' ' -f4`
      if [[ "${QuotaExempt}" = "N" || "${QuotaExempt}" = "n" ]]; then
        ## User is not exempt from notification messages.
        if [[ ${AdjAcctSize} > ${QuotaMin} ]]; then
          ## A notification email needs to be sent.
          if [[ ${AdjAcctSize} < ${QuotaMax} ]]; then
            ## Mailbox size has not gone over the maximum.
            SpaceAvailable=$((${QuotaMax}-${AdjAcctSize}))
            echo "  WARNING: ${AcctName} Mailbox=${AdjAcctSize}${ConversionUnit} Min=${QuotaMin} Max=${QuotaMax}" >> ${LOGFILE}
            f_sendusermail "${AcctName}" "WARNING: Mailbox size" "${WarningMessage}\n\nMailbox size = ${AdjAcctSize}${ConversionUnit}.  You have ${SpaceAvailable}${ConversionUnit} before you reach the maximum of ${QuotaMax}${ConversionUnit}."
          else
            ## Mailbox size is now larger than maximum.
            echo "  ALERT: ${AcctName} Mailbox=${AdjAcctSize}${ConversionUnit} Min=${QuotaMin} Max=${QuotaMax}" >> ${LOGFILE}
            SpaceOver=$((${AdjAcctSize}-${QuotaMax}))
            f_sendusermail "${AcctName}" "ALERT: Mailbox full" "${AlertMessage}\n\nMailbox size = ${AdjAcctSize}${ConversionUnit}.  You are ${SpaceOver}${ConversionUnit} over the maximum of ${QuotaMax}${ConversionUnit}."
          fi
        fi
      fi 
    done < ${ACCTFILE}
    
    ## Remove the temporary file.
    if [ -f ${ACCTFILE} ]; then
      rm ${ACCTFILE}
    fi
    echo "`date +%Y-%m-%d_%H:%M:%S` - Quota check finished." >> ${LOGFILE}
    exit 0
    The default values in this script have been set to 180 (GB) and a max of 200 (GB). That means the "boss" line in the sample quota definition file is unnecessary and can be removed from that file since he matches the system-wide default thresholds.

    Here is a sample of the log file output:

    /var/temp/mailbox-size-notification.log
    Code:
    2012-05-03_06:00:00 - Quota check started.
      ALERT: lhammonds@mydomain.com Mailbox=250MB Min=180 Max=200
      WARNING: joedirt@mydomain.com Mailbox=190MB Min=180 Max=200
      WARNING: hr@mydomain.com Mailbox=280MB Min=270 Max=300
    2012-05-03_06:00:05 - Quota check finished.
    2012-05-04_06:00:00 - Quota check started.
      ALERT: lhammonds@mydomain.com Mailbox=280MB Min=180 Max=200
      WARNING: joedirt@mydomain.com Mailbox=181MB Min=180 Max=200
    2012-05-04_06:00:04 - Quota check finished.
    2012-05-05_06:00:00 - Quota check started.
    2012-05-05_06:00:05 - Quota check finished.
    EDIT 2012-05-05: I have edited the Scripting post on the 1st page and updated the "standard.conf" file which includes an additional global variable and end-user email function.
    Last edited by LHammonds; 05-05-2012 at 12:19 PM.
    Type su - zimbra -c "zmcontrol -v" to get your version and copy that into your profile (more info here)

  2. #22
    LHammonds's Avatar
    LHammonds is offline Special Member
    Join Date
    Sep 2011
    Location
    Texas
    Posts
    150
    Rep Power
    3

    Default

    ToDoList (version 1.0)

    I use the portable version of ToDoList to keep track of projects and things that need to get done.

    This is a copy of my rollout project for Zimbra. Save the text into a file such as ZimbraRollout.xml

    EDIT: Could not paste XML text here...too big. So I used PasteBin.



    Next Tasks on my List:
    - Manually add Distribution Groups to somewhat match Exchange groups
    - Manually add external contacts to the global address list (have not figured out this one just yet)
    - Test-run a mass mailbox conversion from Exchange to Zimbra and note amount of time required.
    - End-user documentation (normal use and conversion/migration info)
    - Admin-user documentation (for other admins that are not necessarily unix admins)
    Last edited by LHammonds; 05-07-2012 at 03:20 PM.
    Type su - zimbra -c "zmcontrol -v" to get your version and copy that into your profile (more info here)

  3. #23
    davidkillingsworth is offline Loyal Member
    Join Date
    Feb 2012
    Location
    Hong Kong
    Posts
    77
    Rep Power
    3

    Default

    Wow. That's very thorough and details instructions.

    Thank You for taking the time to provide that to the community.

    Can I make a request that I don't see throughout your thread.

    What are the steps for upgrading Zimbra on Ubuntu 10.04

    7.1.2 to 7.2.0 for example.

    Thanks, in advance.
    Release 7.2.4_GA_2900.UBUNTU10_64 UBUNTU10_64 FOSS edition.

  4. #24
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,480
    Rep Power
    56

    Default

    Quote Originally Posted by davidkillingsworth View Post
    What are the steps for upgrading Zimbra on Ubuntu 10.04
    That would be exactly the same steps as upgrading any other release of ZCS, run the install.sh script as per the information in the Release Notes with the added proviso of taking a full backup before any upgrade.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  5. #25
    davidkillingsworth is offline Loyal Member
    Join Date
    Feb 2012
    Location
    Hong Kong
    Posts
    77
    Rep Power
    3

    Default

    Quote Originally Posted by phoenix View Post
    That would be exactly the same steps as upgrading any other release of ZCS, run the install.sh script as per the information in the Release Notes with the added proviso of taking a full backup before any upgrade.
    I'm aware of the release notes, but was hoping for some of LHammonds extraordinarily detailed "tell it to me like I'm 5 years old" step by step instructions.

    I just want to make sure that I'm thinking of all the steps.
    Release 7.2.4_GA_2900.UBUNTU10_64 UBUNTU10_64 FOSS edition.

  6. #26
    phoenix is offline Zimbra Consultant & Moderator
    Join Date
    Sep 2005
    Location
    Vannes, France
    Posts
    23,480
    Rep Power
    56

    Default

    If you already have a backup strategy in place then take a full backup, while it's running read the Release Notes for anything that may be needed then then run the update, what else is there to know? How much more simple can it be? If my comments aren't simple enough then feel free to ignore them and wait for something more detailed.
    Regards


    Bill


    Acompli: A new adventure for Co-Founder KevinH.

  7. #27
    LHammonds's Avatar
    LHammonds is offline Special Member
    Join Date
    Sep 2011
    Location
    Texas
    Posts
    150
    Rep Power
    3

    Default

    Quote Originally Posted by davidkillingsworth View Post
    Wow. That's very thorough and details instructions.

    Thank You for taking the time to provide that to the community.
    Thank you and you are welcome.

    Quote Originally Posted by davidkillingsworth View Post
    Can I make a request that I don't see throughout your thread.

    What are the steps for upgrading Zimbra on Ubuntu 10.04

    7.1.2 to 7.2.0 for example.
    As phoenix has already mentioned, it is fairly straight-forward to upgrade 7.1 to 7.2. I did not perform an upgrade for the current 7.2 instructions but the main steps are to backup your data, read the release notes thoroughly, run the install (which detects the current installation and performs an upgrade), make another backup and test everything out.

    I did document my experience when I upgraded a test system from 7.1.2 to 7.1.3 in another thread that was deleted. Here is a copy of it (which includes an issue I had with the upgrade which may not be repeatable using the same versions or newer upgrades but I made note of it anyway)

    Also, when comparing how these old notes might apply to the current thread and release, you would obviously need to download and use the current version which is 7.2.0 and the "temp" folder in this server layout is /var/temp

    EDIT: And as an additional note, since this particular upgrade, I have found that the error regarding lock tables is related to temp tables and has been a "known" issue / bug in MySQL that has never been resolved. I'm not sure why the "integrity" report script was not slightly modified to ignore that particular error on temp tables...or at the very least change it from a critical show-stopper to just an FYI with a bit of info about it such as a link to the long-existing bug report.

    Upgrade Zimbra 7.1.2 to 7.1.3

    Before Upgrading


    1. Read and understand the release notes before doing anything else.
    2. Make a verified offline backup and be sure to place it at an offsite location as well.
    3. Since this is a virtual environment, might as well shutdown the server and create a snapshot of the server. Give it a name like Before 7.1.3 Upgrade and description of Ubuntu Server 10.04.4 LTS, Zimbra 7.1.3 OSE installed, Static IP: 192.168.107.25.
    4. Once the snapshot is complete, start up the Ubuntu server.


    Upgrade Steps


    1. At the login prompt, login with your administrator account (administrator / myadminpass) and then type su and the root password (myrootpass)
    2. Update the package database by typing aptitude update
    3. Install the latest updates by typing aptitude -y safe-upgrade
    4. Download the Open Source Edition from Open Source Edition Downloads: Enterprise Messaging and Collaboration Software by Zimbra

      Method #1 - Download from your PC

      A. Download the .tgz file and copy it to the Ubuntu share --> \\mail\share or \\192.168.107.25\share
      B. Once copied to the server, access the console and type the following:

      Code:
      mv /srv/samba/share/zcs* /temp
      Method #2 - Download directly from the server

      A. Obtain the download URL from the Zimbra OSE page
      B. Type the following commands on the server console (using the correct URL)

      Code:
      cd /temp
      wget http://files.zimbra.com/downloads/7.1.3_GA/zcs-7.1.3_GA_3346.UBUNTU10_64.20110928134610.tgz
    5. Extract the archive by typing the following commands:

      Code:
      mkdir /temp/install
      tar -C /temp/install --strip-components=1 -xzf /temp/zcs*
    6. Start the installation program by typing the following:

      Code:
      cd /temp/install
      ./install.sh
    7. The following is displayed:
      Code:
      Operations logged to /tmp/install.log.3865
      Checking for existing installation...
          zimbra-ldap...FOUND zimbra-ldap-7.1.2_GA_3268.UBUNTU10_64
          zimbra-logger...FOUND zimbra-logger-7.1.2_GA_3268.UBUNTU10_64
          zimbra-mta...FOUND zimbra-mta-7.1.2_GA_3268.UBUNTU10_64
          zimbra-snmp...FOUND zimbra-snmp-7.1.2_GA_3268.UBUNTU10_64
          zimbra-store...FOUND zimbra-store-7.1.2_GA_3268.UBUNTU10_64
          zimbra-apache...FOUND zimbra-apache-7.1.2_GA_3268.UBUNTU10_64
          zimbra-spell...FOUND zimbra-spell-7.1.2_GA_3268.UBUNTU10_64
          zimbra-convertd...NOT FOUND
          zimbra-memcached...NOT FOUND
          zimbra-proxy...NOT FOUND
          zimbra-archiving...NOT FOUND
          zimbra-cluster...NOT FOUND
          zimbra-core...FOUND zimbra-core-7.1.2_GA_3268.UBUNTU10_64
      ZCS upgrade from 7.1.2 to 7.1.3 will be performed.
      
      Saving existing configuration file to /opt/zimbra/.saveconfig
      
      PLEASE READ THIS AGREEMENT CAREFULLY BEFORE USING THE SOFTWARE.
      ZIMBRA, INC. ("ZIMBRA") WILL ONLY LICENSE THIS SOFTWARE TO YOU IF YOU
      FIRST ACCEPT THE TERMS OF THIS AGREEMENT. BY DOWNLOADING OR INSTALLING
      THE SOFTWARE, OR USING THE PRODUCT, YOU ARE CONSENTING TO BE BOUND BY
      THIS AGREEMENT. IF YOU DO NOT AGREE TO ALL OF THE TERMS OF THIS
      AGREEMENT, THEN DO NOT DOWNLOAD, INSTALL OR USE THE PRODUCT.
      
      License Terms for the Zimbra Collaboration Suite:
        http://www.zimbra.com/license/zimbra_public_eula_2.1.html
    8. Agree to license agreement? Press y {ENTER}
    9. If you are missing any prerequisites, exit the installation and install them. You can install all at one time by separating each name with a space after apt-get install such as the following:
      Code:
      aptitude install sysstat sqlite3
    10. Do you want to verify message store database integrity? Press y {ENTER}
    11. You will probably see the following output:
      Code:
      Verifying integrity of message store databases.  This may take a while.
      Starting mysqld...done.
      mysqld is alive
      Database errors found.
      /opt/zimbra/mysql/bin/mysqlcheck --defaults-file=/opt/zimbra/conf/my.cnf -S /opt/zimbra/db/mysql.sock -A -C -s -u root --password=gHEZvnZd323VvkK0uaUcDprGtYI --auto-repair
      mysql.general_log
       Error    : You can't use locks with log tables.
       mysql.slow_log
       Error    : You can't use locks with log tables.
      mysqld is alive
      Stopping mysqld... done.
      
      Checking for installable packages
      
      Found zimbra-core
      Found zimbra-ldap
      Found zimbra-logger
      Found zimbra-mta
      Found zimbra-snmp
      Found zimbra-store
      Found zimbra-apache
      Found zimbra-spell
      Found zimbra-memcached
      Found zimbra-proxy
      
      The Zimbra Collaboration Suite appears already to be installed.
      It can be upgraded with no effect on existing accounts,
      or the current installation can be completely removed prior
      to installation for a clean install.
    12. Do you wish to upgrade? Press y {ENTER}
    13. Install zimbra-memcached? Press n {ENTER} (this is not a multi-server)
    14. Install zimbra-proxy? Press n {ENTER} (this is not a multi-server)
    15. The system will be modified. Continue? Press y {ENTER}
    16. See notes below: I could never get past this step unless I answered "no" when asked to verify database integrity a few steps earlier.
    17. Notify Zimbra of your installation? Press n {ENTER} (feel free to answer yes if this is not a test system)
    18. Press {ENTER} to exit setup. NOTE: Log files placed in /opt/zimbra/log


    After Upgrading


    1. Make a verified offline backup and be sure to place it at an offsite location as well.
    2. Since this is a virtual environment, might as well shutdown the server and create a snapshot of the server. Give it a name like After 7.1.3 Upgrade and description of Ubuntu Server 10.04.4 LTS, Zimbra 7.1.3 OSE installed, Static IP: 192.168.107.25.
    3. Once the snapshot is complete, start up the Ubuntu server.
    4. Now go through your checklist of things to verify that your server is online and fully functional. If something is not working right, now is your opportunity to restore.
    5. If you are satisfied that everything is solid, delete the snapshots.


    --------------------------- Start of notes after step 15 above ------------------------------

    EDIT: I just did a remote VPN to work to check on how things were going but after 2 hours, it has not progressed much since I left it.

    When I left work, the last message displayed was "Shutting down zimbra mail"

    Two hours later, it only added one additional message saying "Backing up the ldap database"

    If nothing has gone wrong, I suppose this would be a REALLY long upgrade if it actually had a bunch of users and a large mail storage.

    EDIT: It is now 5 hours since I started the upgrade and it is still sitting on the "Backing up the ldap database" message. That is at least 3 hours just on this part alone. I suppose something is broken somewhere. hmmm....with a simple one-off install / upgrade and having a problem with the upgrade, it is not inspiring a lot of confidence at this point. I'll assume it is something stupid that I did (or failed to do). I'll do some problem analysis and resolution research tomorrow morning.

    EDIT: I was just too curious to go to bed and sleep on it. So I pressed CTRL+Z to send the install into the background as a paused process. I then typed bg 1 which told it to continue running in the background while I did some research. The 1st thing I checked was my drive space even though the install script checks for enough space at the beginning. I typed df -h and it does show I have quite a bit of space available so running out of room was not the issue. I did notice it took several seconds to complete the command, which was the display of the remote Windows server mount. Thinking that the mount might be causing a slowdown, I typed umount /mnt/backup to temporarily unmount my remote backup server. But that did not seem to be the problem either. I then looked at the /tmp/install.log file and sure enough, I found the problem:

    Code:
    Stopping ldap...Failed.
    Killing slapd with pid 874............................................................................................................................................................................................................................................................................................................ gave up waiting!
    COMMAND: /opt/zimbra/libexec/zmslapcat /opt/zimbra/data/ldap
    hdb_db_open: database "": unclean shutdown detected; attempting recovery.
    hdb_db_open: database "": recovery skipped in read-only mode. Run manual recovery if errors are encountered.
    For whatever reason, the ldap service failed to stop for the install script. That makes no sense to me whatsoever. I have run /etc/init.d/zimbra stop both manually and through scripts and never once had a problem stopping or starting the services. I'm at a loss for how to resolve the problem or keep it from happening again in the future.

    I've read several times before to simply run the install script again after an error to see if it can get past it so I'll give that a shot right now (after I manually try to control the services). Since the install is still running in the background, I'm going to type fg 1 to bring it back to the foreground so I can press CTRL+C to break out and stop the install script and try again.

    EDIT: Several hours later (after I woke up from falling asleep in my chair) I have finally figured out how to get past that problem. It did not matter if zimbra services were stopped or started before running install.sh, it always hung up during the ldap backup if I answered yes when asked to verify message store database integrity. Answering no to that question allowed the install to proceed past the ldap backup step.

    --------------------------- End of notes after step 15 above ------------------------------


    As a side note, I was logged into my mailbox on one of my browser tabs and did not realize it before starting the upgrade. When I went back to that tab to login and see if things were working, I was greeted with the following awesome and convenient little message:

    Code:
    Warning
    -------
    The server software has been updated. It is recommended that you reload your browser so that you are up to date.
    
    Old version: 7.1.2_GA_3268 20110804130819 20110804-1312 FOSS
    New version: 7.1.3_GA_3346 20110928134610 20110928-1350 FOSS
    
    Would you like to reload the browser now? Warning: if you choose not to reload, there is a chance you will encounter errors.
    [Yes] [No]
    This popup box was sitting on top of another popup box that said the following (which must have popped up 1st):
    Code:
    Zimbra
    ------
    Cannot connect to server.
    [Show Details] [OK]
    Last edited by LHammonds; 05-08-2012 at 07:19 AM.
    Type su - zimbra -c "zmcontrol -v" to get your version and copy that into your profile (more info here)

  8. #28
    edgarosy is offline New Member
    Join Date
    May 2012
    Location
    Salt Lake City
    Posts
    3
    Rep Power
    3

    Smile

    Very nice post. I woul like to get similar information for a fresh installation of Zimbra on a Red-Hat 6 server and migrating from openldap server instead of Active Directory.

  9. #29
    ccelis5215 is offline Elite Member
    Join Date
    Jun 2011
    Location
    Caracas Venezuela
    Posts
    461
    Rep Power
    4

    Default

    Very nice post. I woul like to get similar information for a fresh installation of Zimbra on a Red-Hat 6 server and migrating from openldap server instead of Active Directory.
    edgarosy, pls let us know!

    ccelis

  10. #30
    dream_liner2k2 is offline Active Member
    Join Date
    Feb 2012
    Location
    India
    Posts
    35
    Rep Power
    3

    Default

    Dear LH,

    You are the MAN !!!

    Think of some feature and search for the script, and all roads are leading me to the RoMAN !!!

    Thank you so so much and that much more for your efforts.

    At the juncture, seeing notes on upgrading to 7.2, I'm utterly butterly jittery.

    Thanks all the more

Page 3 of 7 FirstFirst 12345 ... LastLast

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. /tmp filling
    By Nutz in forum Administrators
    Replies: 8
    Last Post: 02-22-2008, 02:00 AM
  2. Replies: 31
    Last Post: 12-15-2007, 09:05 PM
  3. Post instsallation problems
    By Assaf in forum Installation
    Replies: 14
    Last Post: 01-29-2007, 11:38 AM
  4. 3.1 on FC4 problems
    By cohnhead in forum Installation
    Replies: 8
    Last Post: 05-26-2006, 11:16 AM
  5. Zimbra server crashed
    By goetzi in forum Administrators
    Replies: 6
    Last Post: 03-25-2006, 01:00 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •