https://wiki.koozali.org/api.php?action=feedcontributions&user=Byte&feedformat=atom
SME Server - User contributions [en]
2024-03-29T06:21:10Z
User contributions
MediaWiki 1.35.5
https://wiki.koozali.org/index.php?title=SME_Server:About&diff=15252
SME Server:About
2010-11-17T15:15:24Z
<p>Byte: /* Product Reviews */</p>
<hr />
<div>==Introduction==<br />
Why spend a fortune on Windows server software when you can get more for so much less?!<br />
<br />
SME Server is an Open Source Linux Server distribution and provides a flexible, worry-free, secure, network and communications server solution you won't outgrow. It is designed to be:<br />
* Simple to setup and use: Installation and basic configuration takes less than 20 minutes, and every configuration option can be set via a web-based interface.<br />
* Secure and stable to operate: SME Server only includes what is necessary, which translates into the entire ISO being around 500MB. Stability comes from using proven, supported rpm packages and from an update system that notifies you with available updates.<br />
* Cross-platform and extendible to meet future needs: SME Server already has everything necessary to provide the core services most people need to network Linux, Macintosh, and Windows systems.<br />
* And it's completely free!<br />
* Download the ISO from http://wiki.contribs.org/SME_Server:Download <br />
<br />
Exceptionally reliable and easy to use, SME Server can be installed and configured in less than 20 minutes - yet it's powered by a secure and open Linux platform that's fully upgradeable and customizable. Simply install it on any standard PC and in minutes you'll have a robust Linux-based LAMP server capable of fully replacing those expensive Windows server licenses and providing a full range of services - including e-mail, firewall, file and print-sharing, web hosting, remote access and more.<br />
<br />
SME Server integrates easily with Windows, Macintosh, and Unix/Linux clients, and within a Windows network environment. It's as simple to use as a server appliance, but unlike a "sealed-box" appliance the entire system is modular and extensible, so it can be tailored to the needs of individual businesses.<br />
<br />
==Features and Benefits==<br />
<br />
===Ease of Administration===<br />
SME Server software uses a web-based interface to enable easy administration from any web browser on the internal network, password protected and accessible remotely via SSH or PPTP.<br />
<br />
===File and Print Sharing===<br />
The core of any network environment is easy and simple access to shared files and printers. SME Server software allows for the easy sharing of files and printers to Windows and Macintosh clients. The "Information Bay" (i-bay) feature provides easy and convenient information storage and retrieval by multiple groups via web, ftp, or file sharing.<br />
<br />
===Internet Connection===<br />
Small business customers are looking for a simple solution that works with different types of connections to the Internet. SME Server automates the process of connecting to the Internet. Just connect the server and supply your ISP account information. The server solution acts as a gateway for your entire network and requires no additional client software and minimal configuration. Users can immediately start browsing the Web, using email, and access other Internet services.<br />
<br />
===Email===<br />
With the pervasiveness of email, small businesses increasingly need to support email for all their employees. SME Server provides a secure reliable email server and allows easy creation of individual and group addresses. For greater versatility, it works with any mail client that uses the industry-standard IMAP, POP3, and SMTP protocols. Secure webmail allows users to access the server from a web browser anywhere on the Internet, to send and receive e-mail via an encrypted (128-bit SSL) link. On top of that it is equipped with ClamAV Antivirus and SpamAssassin to reduce the amount of unsolicited mail.<br />
<br />
===Firewall===<br />
Security is always a priority when a company starts using the Internet. SME Server offers a multi-layer architecture, protecting the external interface through packet-filtering and service restriction. It offers selective address or port binding, application-level access control lists, and protects the internal network from any intrusion.<br />
<br />
===Remote Access===<br />
Businesses with remote or branch sites or telecommuting employees require remote access to their email and to other resources on the local network. SME Server provides multiple tools such as webmail access to email using any browser, 128-bit PPTP (for secure client-to-server VPNs) and open secure shell (SSH) to provide encrypted access to the internal network and server resources for administrators.<br />
<br />
===Directory Services===<br />
Companies typically require a central directory of email addresses that all users can access. SME Server features a robust directory service that can be used by most email clients (including Outlook, Outlook Express, and Netscape Communicator). This feature is implemented using the industry-standard LDAP protocol.<br />
<br />
===Web Hosting===<br />
Small businesses also need a secure and reliable web presence and an intranet to communicate with employees. SME Server includes the Apache web server used by over 60% of the Internet. The content can be easily edited and updated from desktop clients (including dynamic content). It also supports the use of Secure Sockets Layer (SSL) connections for e-commerce.<br />
<br />
===Raid and Backup===<br />
SME Server software supports both hardware and software disk mirroring (RAID 1), USB Disk backup & tape backup for additional data protection.<br />
<br />
===Automatic Updates===<br />
Almost all of the packages that SME Server includes from upstream vendors are included unmodified. The purpose of doing so is to take advantage of the stability that comes from the huge user base that uses these packages, for security, and to allow automatic updates as soon as an update is available from the upstream vendor. Security updates from Redhat/Centos should be available until 2012 for Centos 4<br />
<br />
===Extensible===<br />
The SME Server architecture explicitly supports developers by making it easy to drop software into place and remove it without needing to modify existing files. Extensions can easily add new features, a few popular examples are Asterisk VOIP PBX, HylaFax server, DansGuardian web content filter, Joomla CMS, Jinzorra jukebox, Mediawiki, Thin client server, OsCommerce online shop.<br />
<br />
==Platform Specifics==<br />
SME Server v7.5 is the latest stable version of the award-winning Mitel/e-smith based Server and Gateway, the world's leading open-source server software for small and medium-sized enterprises. The heart of SME Server 7 is based on the GPL'd sources of the unsupported developer release of SME 7.0 alpha from Mitel, who is the copyright holder for much of what makes SME Server what it is. Mitel's commercial offering is known as the "Mitel Managed Application Server", and in the past was known as e-Smith. Mitel has been very generous to fund development of the alpha and beta versions and to keep to the spirit of the GPL by sharing their source code freely.<br />
<br />
SME Server 7 uses many packages from CentOS and RPMForge. CentOS 4 is built from publicly available open source Red Hat Enterprise Linux SRPMS and aims to be binary compatible. RPMForge is a collaborative effort of several RPM packagers that build RPMs not included with CentOS. Almost all of the packages that SME Server includes from these upstream vendors are included unmodified. The purpose of doing so is to take advantage of the stability that comes from the huge user base that uses these packages, for security, and to allow automatic updates as soon as an update is available from the upstream vendor. Security updates from Redhat/Centos should be available until 2012 for Centos 4.<br />
<br />
SME Server v7.5 is based upon Centos v4.8 with the following major package versions (as of May 2010 - these are subject to minor revision updates and bug fixes from upstream):<br />
* Linux Kernel - 2.6.9<br />
* Apache web server - 2.0.52<br />
* MySQL database - 4.1.22<br />
* PHP - 4.3.9<br />
* Python - 2.3.4<br />
* Perl - 5.8.5<br />
* Qmail mail server - 1.03 <br />
* Samba file and printer sharing - 3.0.33<br />
<br />
==Product Reviews==<br />
The community’s forums and wiki are very active and there are lots of HowTos available. Additional repositories are also available for many extra packages that could not be included in the download because of the limitations of a single CD ISO file.<br />
<br />
[...]<br />
<br />
SME Server is pretty much the original ready-rolled server distribution. Although it has changed hands – and names – a few times, it's been around since 1999, when it was known as e-Smith, a name you'll still see in a few places.<br />
<br />
[http://www.theregister.co.uk/2010/11/17/review_sme_server/ The Register: SME Server: A Linux server OS that's had 11 years to improve], November 17, 2010<br />
<br />
"In 2001, SME Server was bought by enterprise VOIP vendor Mitel, which for a while offered unified office servers based around e-Smith, which it renamed Managed Application Server. Mitel donated the product back to the community in 2004, where today it is developed cooperatively by a community based around the contribs.org website – originally a home for third-party extensions to the software.<br />
<br />
[...]<br />
<br />
Perhaps you’re thinking: “So what, I can do that with [your favourite distro here].” What makes SME server special is that its features are well integrated and that after the installation there is no need for end users to see the command line again. You can install it and forget about it.<br />
<br />
[http://www.tectonic.co.za/?p=4649 Tectronix: SME Server: The Linux solution for growing businesses], April 14, 2009<br />
<br />
"SME server makes it really easy for the user to place an adequate Intranet environment in the net without profound Linux knowledge. The distribution is primarily meant for smaller and medium-size enterprises, in addition, private people profit from the outstanding characteristics of the operating system as Mail and file servers.<br />
<br />
[...]<br />
<br />
The developers of SME Server did their documentation homework to the best. Appropriate assistance text described really each point of the Web-based configuration, smaller text left refers to the appropriate site for on-line assistance."<br />
<br />
[http://www.linux-user.de/ausgabe/2006/10/014-sme-server/index.html LinuxUser (in German)], October, 2006<br />
<br />
"E-Smith SME Server is a Linux distribution designed to serve as a dedicated firewall/gateway server, allowing you to share an Internet connection over a LAN. The distribution is a heavily-modified version of Red Hat Linux, with most of the latter, including the GUI, removed, leaving only what is required to run a firewall/gateway in a small 380MB package."<br />
<br />
[http://www.pcworld.idg.com.au/index.php/id;1093996607;fp;2;fpid;1039317049 Australian PC World], December 10, 2003<br />
<br />
"Installing and configuring SME Server couldn't be easier. For our tests, we installed the software on a Dell PowerEdge 2300 with a fresh 18GB hard drive. The installation process is almost completely automated; at the "boot" prompt, we had to type "proceed" to accept the license agreement and begin the installation, and then sat back while the software installed and configured itself based on our installed hardware without our intervention.<br />
<br />
[...]<br />
<br />
SME Server is built on a standard Linux operating system which includes common applications and utilities freely available to the Linux community. Although the functionality provided by SME Server is certainly readily available to any knowledgeable Linux administrator, the product's custom management tools and automated installation process let virtually anyone with a modicum of Linux experience install and maintain a network file server with minimal effort. The software is free to download<br />
<br />
[...]<br />
<br />
SME Server is ideally suited for enterprise environments in which remote servers must be installed to support a user base, and also in cases where on-site technical support to maintain the server is not readily available. Its remote administration and management features--absent from Windows 2000 environments--provide additional flexibility. Also, SME Server requires no client access licenses, so a corporation can serve a dozen or a thousand users from an SME-based server without breaking the bank to pay license fees. Enterprises looking for a flexible, cost-effective alternative to Microsoft's network services should take a close look at SME Server 5."<br />
<br />
[http://techupdate.zdnet.com/techupdate/stories/main/0,14179,2840241,00.html ZDNet TechReview], January 17, 2002 <br />
<br />
"If you're looking to roll your own Net appliance for either yourself or customers on a shoestring budget, but don't want to sacrifice ease-of-use or performance, definitely give the March Networks SME Server 5 a spin."<br />
<br />
[http://64.233.183.104/search?q=cache:d_ZcofScejgJ:www.linux-mag.com/id/933/+sme+server+review&hl=en&ct=clnk&cd=8 Linux Magazine (from Google cache)], December 15, 2001<br />
<br />
"The e-smith package is a fine piece of software, and when you take into consideration the company's high regard for your network's security, it definitely merits a look-see. We have no problem recommending the e-smith server and gateway to small to midsize businesses looking to test the Linux waters." <br />
<br />
Network Computing, April 2, 2001<br />
<br />
"It can be networked with Windows- and Mac OS-based computers, which means you can buy a no-name PC, load e-Smith Server and Gateway on it, then network your IBM ThinkPad and your graphics designer's Macintosh. . . . The server, [e-smith customer James Hertz] said, has been `rock-solid'." <br />
<br />
Business Week, October 9, 2000</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=15086
SME Server 8
2010-08-20T21:21:05Z
<p>Byte: /* Status: Beta */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. SME Server 8.0beta6 is based on CentOS 5.5.<br />
<br />
See the [http://forums.contribs.org/index.php/topic,46452.0.html Release Announcement for Beta6].<br />
<br />
A copy of the latest CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8/iso/i386/ here].<br />
<br />
===Testing===<br />
<br />
All users are encouraged to test, see our draft quality assurance testing page for tasks [[SME8.0 QA]]<br />
<br />
All testing should be based on the released version plus updates from smeupdates-testing.<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
<br />
Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating. For testing of contribs in advance of release see [[SME8.0 Contribs QA]]<br />
<br />
===Upgrade paths===<br />
Check for rpms installed from outside the standard yum repositories<br />
/sbin/e-smith/audittools/newrpms<br />
<br />
====CD====<br />
After Upgrading<br />
<br />
Reset repositories to SME 8, see below, bug 5705. This is fixed for SME Server 8.0 Beta 6<br />
<br />
====Yum====<br />
Check for known issues, here [[SME8.0 QA]] and at open bugs for SME 8 in bugzilla.<br />
<br />
Note especially Bug 5316, detach all USB drives, ie your backup <br />
<br />
=====Pointing repositories to SME 8=====<br />
Update the MirrorList property to point to the sme8 lists...<br />
<br />
db yum_repositories print | grep '^sme' | cut -d= -f1 | while read repo<br />
do<br />
db yum_repositories setprop $repo MirrorList \<br />
<nowiki>http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/$repo-8</nowiki><br />
done<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====Performing the upgrade=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
<ol></li><li>Clean out the yum cache so upgrades work:<br />
rm -rf /var/cache/yum/*<br />
</li><li>Perform the upgrade:<br />
yum --disablerepo=smeextras --enablerepo=smeupdates-testing upgrade<br />
</li><li>Remove outdated rpm database and rebuild it (zeros not O's)<br />
rm -f /var/lib/rpm/__db.00*<br />
rpm --rebuilddb<br />
</li><li>Reset yum updates repositories to defaults, (will delete local changes)<br />
mv /home/e-smith/db/yum_repositories /home/e-smith/db/yum_repositories.pre8<br />
/etc/e-smith/events/actions/initialize-default-databases<br />
</li><li>Perform a post-upgrade and reboot<br />
signal-event post-upgrade<br />
signal-event reboot<br />
</li></ol><br />
<br />
=====Potential issues that may arise=====<br />
If you are running a 7.0 system you may need to upgrade smeserver-yum.<br />
<ol></li><li>Check which version of smeserver-yum you are running:<br />
rpm -q smeserver-yum<br />
</li><li>If it isn't at least <b>1.2.0-25.el4.sme</b> install an updated version:<br />
rpm -Uvh \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/smeserver-yum-1.2.0-25.el4.sme.noarch.rpm</nowiki> \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/yum-plugin-fastestmirror-0.2.4-3.c4.noarch.rpm</nowiki><br />
</li></ol><br />
<br />
If you receive the following error while trying to upgrade:<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
Solve it by installing the correct version of yum-metadata-parser:<br />
rpm -Uvh --oldpackage \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
<br />
If you a < 7.2 system and have errors with yum upgrade try without '--disablerepo=smeextras'<br />
yum --enablerepo=smeupdates-testing upgrade<br />
<br />
===Upgrading samba===<br />
The Samba packages in SME Server 8.0 Beta 6 have reverted to those provided by CentOS to simplify the support needed. This version of samba provides support for Windows 7<br />
domain logins. Due to this change from samba-3.4 to samba3x-3.3 it is necessary to remove samba if samba-3.4.x has been installed.<br />
All users of SME Server 8.0 Beta 5 are affected. Users of other versions of SME Server can check their samba version.<br />
<br />
rpm -q samba samba3x<br />
<br />
Here is the example output showing samba 3.4 packages installed which need removal.<br />
<br />
samba-3.4.3-1.1.el5.sme<br />
package samba3x is not installed<br />
<br />
Here is the example output showing samba3x 3.3 packages installed which need no further steps<br />
<br />
package samba is not installed<br />
samba3x-3.3.8-0.52.el5_5<br />
<br />
If samba-3.4.x then you need to run:<br />
<br />
rpm -e --nodeps libtalloc libtdb samba samba-client samba-common samba-winbind<br />
<br />
Now you are ready to upgrade to SME Server 8.0 Beta 6<br />
<br />
=== Additional steps and potential changes ===<br />
<br />
==== VMWare ====<br />
VMware-server installations need some tweaking at this stage, see [[VMware_server_on_SME8.0beta5]].<br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=15051
SME Server 8
2010-07-13T19:52:29Z
<p>Byte: /* Potential issues that may arise */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. SME Server 8.0beta5 is based on CentOS 5.4.<br />
<br />
See the [http://forums.contribs.org/index.php/topic,45681.0.html Release Announcement for Beta5].<br />
<br />
A copy of the latest CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8/iso/i386/ here].<br />
<br />
===Testing===<br />
<br />
All users are encouraged to test, see our draft quality assurance testing page for tasks [[SME8.0 QA]]<br />
<br />
All testing should be based on the released version plus updates from smeupdates-testing.<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
<br />
Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating. For testing of contribs in advance of release see [[SME8.0 Contribs QA]]<br />
<br />
===Upgrade paths===<br />
Check for rpms installed from outside the standard yum repositories<br />
/sbin/e-smith/audittools/newrpms<br />
<br />
====CD====<br />
After Upgrading<br />
<br />
Reset repositories to SME 8, see below, bug 5705<br />
<br />
====Yum====<br />
Check for known issues, here [[SME8.0 QA]] and at open bugs for SME 8 in bugzilla.<br />
<br />
Note especially Bug 5316, detach all USB drives, ie your backup <br />
<br />
=====Pointing repositories to SME 8=====<br />
Update the MirrorList property to point to the sme8 lists...<br />
<br />
db yum_repositories print | grep '^sme' | cut -d= -f1 | while read repo<br />
do<br />
db yum_repositories setprop $repo MirrorList \<br />
<nowiki>http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/$repo-8</nowiki><br />
done<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====Performing the upgrade=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
<ol></li><li>Clean out the yum cache so upgrades work:<br />
rm -rf /var/cache/yum/*<br />
</li><li>Perform the upgrade:<br />
yum --disablerepo=smeextras --enablerepo=smeupdates-testing upgrade<br />
</li><li>Remove outdated rpm database and rebuild it (zeros not O's)<br />
rm -f /var/lib/rpm/__db.00*<br />
rpm --rebuilddb<br />
</li><li>Reset yum updates repositories to defaults, (will delete local changes)<br />
mv /home/e-smith/db/yum_repositories /home/e-smith/db/yum_repositories.pre8<br />
/etc/e-smith/events/actions/initialize-default-databases<br />
</li><li>Perform a post-upgrade and reboot<br />
signal-event post-upgrade<br />
signal-event reboot<br />
</li></ol><br />
<br />
=====Potential issues that may arise=====<br />
If you are running a 7.0 system you may need to upgrade smeserver-yum.<br />
<ol></li><li>Check which version of smeserver-yum you are running:<br />
rpm -q smeserver-yum<br />
</li><li>If it isn't at least <b>1.2.0-25.el4.sme</b> install an updated version:<br />
rpm -Uvh \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/smeserver-yum-1.2.0-25.el4.sme.noarch.rpm</nowiki> \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/yum-plugin-fastestmirror-0.2.4-3.c4.noarch.rpm</nowiki><br />
</li></ol><br />
<br />
If you receive the following error while trying to upgrade:<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
Solve it by installing the correct version of yum-metadata-parser:<br />
rpm -Uvh --oldpackage \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
<br />
If you a < 7.2 system and have errors with yum upgrade try without '--disablerepo=smeextras'<br />
yum --enablerepo=smeupdates-testing upgrade<br />
<br />
'''Upgrade procedures for SME Server 8beta5 to SME Server 8beta6'''<br />
<br />
Note:<br />
These steps may be required from SME Server 8.beta3 ><br />
<br />
Before upgrading verify that samba >= 3.3 is installed<br />
rpm -q samba<br />
<br />
And here is an example of an out-put<br />
<br />
samba-3.4.3-1.1.el5.sme<br />
<br />
Now you have verified the above you can now run:<br />
<br />
rpm -e --nodeps libtalloc libtdb samba samba-client samba-common samba-winbind<br />
<br />
Now you are ready to continue with [[SME_Server_8#Performing_the_upgrade]]<br />
<br />
=== Additional steps and potential changes ===<br />
<br />
==== VMWare ====<br />
VMware-server installations need some tweaking at this stage, see [[VMware_server_on_SME8.0beta5]].<br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=Main_Page&diff=15023
Main Page
2010-06-27T13:06:45Z
<p>Byte: /* SME Server */</p>
<hr />
<div>__NOTOC__<br />
{{Languages}}<br />
{| style="border: solid 1px; border-color:lightgray;" width=100% cellpadding=5 cellspacing=0<br />
| align=left valign=top cellspacing=0 cellpadding=0 style="background-color: #ffff99;" | '''Current Stable Release:'''<br />
[[SME Server:7.5 |SME Server 7.5]] released on 26th May 2010. <br />
| align=left valign=top cellspacing=0 cellpadding=0 style="background-color: #ffff99;" | '''Development Releases and Statuses:'''<br />
SME Server 8.0 - Currently Beta5 - See the [[:SME_Server_8| Wiki]] page for details, and [[bugzilla:3640]] for status<br />
|- |<br />
|}<br />
{| width 100% cellpadding=5 cellspacing=0 <br />
|-<br />
| align=left valign=top rowspan="9"| <br />
===SME Server===<br />
Welcome to http://contribs.org, the home of the SME Server. We're here to provide collaborative documentation of the SME Server project. <br />
<br />
SME Server is a leading Open Source distribution for small and medium enterprises. It is a simple, powerful, secure Linux server for networking and communicating, used by thousands of individuals, companies and organizations all over the world. SME Server provides a friendly, free alternative to expensive proprietary software, standing apart from the competition by shipping with most common functionality preconfigured, and features a number of popular additional enhancements in the form of downloadable [[:Category:Contrib| Contributions]]. <br />
<br />
SME Server is built on [http://www.centos.org CentOS] using the publicly available open source [http://www.redhat.com Red Hat] Enterprise Linux sources. It's advantages include:<br />
* Simple to set up and use<br />
* Secure and stable to operate<br />
* Cross platform and extendible to meet future needs<br />
* Open source and Free to use<br />
<br />
SME Server provides the following standard functionality (See [[SME_Server:About|About SME Server]] for more detail):<br />
* Ease of Administration<br />
* File and print sharing<br />
* Sharing of a single Internet connection between multiple computers<br />
* A robust email server, which includes virus and spam filtering and webmail<br />
* A network firewall to protect against Internet intruders<br />
* Secure remote access<br />
* Directory services<br />
* Web application server, including support for Apache, MySQL, PHP and Python (LAMPP)<br />
* RAID and Backup<br />
* Automatic updates<br />
* Extendibility<br />
* Support for multiple languages<br />
* and much more ...<br />
all managed through an intuitive web interface<br />
<br />
The wiki menu bar at the left together with the links to the right provide comprehensive access to all the available Documentation for SME Server including details of the [[SME_Server:Community|Community]], [[SME_Server:Documentation|Server Manuals]] (including screenshots), [[SME_Server:Documentation:FAQ|FAQ]], [[:Category:Contrib|Contribs]] and [[:Category:Howto|How To's]]. There are also links for [[:SME_Server:Download|Downloads]], [http://bugs.contribs.org Bugzilla] to report any bugs, and the vibrant user community [http://forums.contribs.org Forums].<br />
<br />
Many individuals and corporations contribute to the ongoing development of SME Server, which is made available freely under the GNU General Public License. This license requires the public release of any modifications to the server, and allows these to be used to improve later versions.<br />
<br />
While SME Server is freely available under the GPL license, if you find SME Server useful we ask that you make a [[:Donate| Donation]] in order to help keep this project alive.<br />
====Support====<br />
Support for SME Server is via the [[SME_Server:Community|Community]] and it is highly recommended that you make yourself familiar with it and the [[SME_Server:Documentation|Documentation]] (read this at least twice) before diving in. You should also read the [[SME_Server:Advice|Advice]] for new and existing users.<br />
<br />
The three main methods of support available are:<br />
<br />
; [[:SME_Server:Documentation |Documentation]]:<br />
* The Wiki documentation is the primary source of information for SME Server. This should always be your first port of call when seeking help and support for SME Server<br />
* 'Google' is your friend (as well as all other internet search engines)<br />
<br />
; [http://bugs.contribs.org Bugzilla]:<br />
* If you do something and it doesn't 'just work', or it doesn't work as per the Wiki, raise a [http://bugs.contribs.org Bug]<br /><br />
* If you want to do, or are trying to do, something which is not ''standard'' SME or not in the Wiki, ask in the [http://forums.contribs.org Forums]<br />
* For more information on Bugzilla see the [[:Bugzilla Help]] page.<br />
{{Note box|The place of choice of the Developers to solve problems is [http://bugs.contribs.org Bugzilla], so don't be afraid to use it.<br />
}}<br />
<br />
; [http://forums.contribs.org Forums]:<br />
* Use the [http://forums.contribs.org Forums] if you want advice on how to do something not covered in the Wiki <br /><br />
* Post to the [http://forums.contribs.org Forums] if you found or did something, and you think other people might find it interesting or helpful to share <br /><br />
* If you don't know how to do something, or don't understand the Wiki, ask in the [http://forums.contribs.org Forums] <br /><br />
* If you report a problem in the forums, and it relates to how ''standard'' SME Server, a Contributed Add-on or Howto should work, you will more than likely be directed to raise it as a [http://bugs.contribs.org Bug] to be given structured advice and help you resolve it<br />
<br />
| width="60px" height="20px" align=right valign=top | <br />
| align=left valign=top |<br />
<br />
====Documentation====<br />
|-<br />
| width="60px" height="60px" align=right valign=center | <br />
[[Image:Kdict.png | link=:SME_Server:Documentation | 48px ]]<br />
|'''[[:SME_Server:Documentation|Additional Documentation]]''' <br /><br />
[[:SME_Server:Documentation:FAQ|FAQ]] - Frequently Asked Questions <br /><br />
[[:Category:Howto|HowTo's]] - Specific Help, Instructions and Tutorials<br />
|-<br />
| width="60px" height="60px" align=right valign=center | <br />
[[Image:Blockdevice.png | link=:Category:Contrib | 48px ]]<br />
|'''[[:Category:Contrib|Contributions]]''' <br /><br />
[[:Category:Contrib|Contribs]] - SME Server Contributed add-on packages<br />
|-<br />
| width="60px" height="60px" align=right valign=center | <br />
[[Image:Kdict.png | link=:Category:Categorisation | 48px ]]<br />
|'''[[:Category:Categorisation| Categorised Contribs and Howto's]]''' <br /><br />
|-<br />
| width="60px" height="60px" align=right valign=center | <br />
[[Image:Kdict.png | link=Category:Level | 48px ]]<br />
|'''Contribs and Howto's rated by Skill Level <br /><br />
[[:Category:Easy|Easy]] <br /><br />
[[:Category:Medium|Medium]] <br /><br />
[[:Category:Advanced|Advanced]] <br /><br />
[[:Category:Developer|Developer]]<br />
|-<br />
| width="60px" height="60px" align=right valign=center |<br />
[[Image:Help.png | link=Help:Contents | width=22px | height=22px ]]<br />
|'''Wiki Help''' <br /><br />
[[Help:Contents|Help]] with reading and editing this Wiki <br /><br />
[[Template:Languages| Language]] Template and Translation Help for this Wiki <br /><br />
[http://meta.wikimedia.org/wiki/Help:Contents#For_editors|Full MediaWiki Help] with editing MediaWiki's generally<br />
|-<br />
| width="60px" align=right valign=center | <br />
| valign=top |<br />
...and don't forget all the navigation links in the sidebar to the left.<br />
|}</div>
Byte
https://wiki.koozali.org/index.php?title=Funambol&diff=14928
Funambol
2010-05-12T14:13:24Z
<p>Byte: /* Verify Funambol Installation */</p>
<hr />
<div>{{Needs review}}<br />
{{Level|Advanced}}<br />
== Introduction == <br />
The Funambol middleware allows you to synchronize mobile devices with [http://wiki.contribs.org/Sogo SOGo] through the <br />
use of the Funambol [http://wiki.contribs.org/Sogo SOGo] Connector. The connector allows any SyncML enabled devices to <br />
fully synchronize contacts, events and tasks with [http://wiki.contribs.org/Sogo SOGo].<br />
<br />
This HOWTO describes the installation procedure for installing Funambol with the [http://wiki.contribs.org/Sogo SOGo] Connector on an SME8b5 installation.<br />
<br />
== Download & Install Funambol ==<br />
Goto https://www.forge.funambol.org/DomainHome.html<br />
to download Funambol 8.0. The latest GNU/Linux 32bit funambol server is 8.5, but this has not been confirmed yet for use with SOGO.<br />
<br />
wget http://download.forge.objectweb.org/sync4j/funambol-8.0.2.bin<br />
<br />
Run the binary to install:<br />
<br />
chmod +x funambol-8.0.2.bin<br />
./funambol-8.0.2.bin<br />
<br />
Agree on the licence terms and accept '''/opt''' as the directory to extract Funambol. This will install it in:<br />
<br />
/opt/Funambol<br />
<br />
At the end of the install, answer '''NO''' on the question if you want to start the server.<br />
<br />
== Setup Funambol to use MySQL ==<br />
<br />
=== Download & Configure MySQL JDBC driver ===<br />
Funambol by installation defaults to use the Hypersonic DB engine, but [http://wiki.contribs.org/Sogo SOGo] uses MySQL and for Funambol to access the [http://wiki.contribs.org/Sogo SOGo] databases it needs to be setup to also use MySQL for the Funambol database.<br />
<br />
Goto http://dev.mysql.com/downloads/connector/j/5.0.html to download the JDBC driver for MySQL. The current version is '''mysql-connector-java-5.0.8.zip'''.<br />
<br />
unzip mysql-connector-java-5.0.8.zip<br />
mkdir -p /opt/Funambol/tools/mysql/lib<br />
cp mysql-connector-java-5.0.8/mysql-connector-java-5.0.8-bin.jar /opt/Funambol/tools/mysql/lib<br />
rm -rf mysql-connector-java-5.0.8<br />
<br />
Edit the '''/opt/Funambol/ds-server/install.properties''' file to change the Funambol DB connector to MySQL.<br />
<br />
vim /opt/Funambol/ds-server/install.properties<br />
<br />
Change the line with '''dbms=''' to:<br />
<br />
# The DBMS name. One of:<br />
# - hypersonic<br />
# - postgresql<br />
# - mysql<br />
#<br />
dbms=mysql<br />
<br />
Comment out the existing jdbc driver for Hypersonic and add the MySQL connection information:<br />
<br />
# MySQL<br />
# =====<br />
jdbc.classpath=../tools/mysql/lib/mysql-connector-java-5.0.8-bin.jar<br />
jdbc.driver=com.mysql.jdbc.Driver<br />
jdbc.url=jdbc:mysql://localhost/funambol?characterEncoding=UTF-8<br />
jdbc.user=funambol<br />
jdbc.password=yourpassword<br />
<br />
=== Reconfigure MySQL for InnoDB and access from the local network ===<br />
Funambol uses MySQL with the InnoDB engine and uses networking for access.<br />
<br />
/sbin/e-smith/config setprop mysqld InnoDB enabled<br />
/sbin/e-smith/config setprop mysqld LocalNetworkingOnly no<br />
/sbin/e-smith/expand-template /etc/my.cnf<br />
/etc/rc.d/rc7.d/S50mysqld restart<br />
<br />
=== Creating MYSQL user and database ===<br />
To create the Funambol Database, you'll need to perform each of the following steps: <br />
mysqladmin create funambol --default-character-set=utf8<br />
mysql -e "grant all privileges on funambol.* to funambol@localhost identified by 'yourpassword'"<br />
mysql -e "flush privileges"<br />
{{Warning box|You may wish to alter the "funambol" and "yourpassword" information in the grant privileges line above. Be sure to configure it correctly in '''/opt/Funambol/ds-server/install.properties''' !}}<br />
<br />
== Disable Hypersonic JDBC driver ==<br />
Edit '''/opt/Funambol/bin/funambol''' and change '''COMED=true''' to '''COMED=false''' somewhere around line 44.<br />
<br />
This prevents the start/stop script from trying to start or stop the Hypersonic database, since we’re are now using MySQL.<br />
<br />
Optionally you can ''rm -rf /opt/Funambol/tools/hypersonic'' to save a bit of disk space.<br />
<br />
== Create Funambol user and group ==<br />
groupadd funambol<br />
useradd -g funambol -d /opt/Funambol funambol<br />
chmod 770 /opt/Funambol/<br />
<br />
== Set Funambol to start on system startup ==<br />
To make Funambol start automagically, create<br />
<br />
vim /etc/init.d/funambol<br />
<br />
with the following content:<br />
<br />
#! /bin/bash<br />
#<br />
# funambol Start the funambol services<br />
#<br />
NAME="Funambol 8.0 with SOGO Connector"<br />
FUNAMBOL_HOME=/opt/Funambol/bin<br />
FUNAMBOL_USER=funambol<br />
case "$1" in<br />
start)<br />
echo -ne "Starting $NAME.\n"<br />
cd $FUNAMBOL_HOME<br />
/bin/su $FUNAMBOL_USER funambol start<br />
;;<br />
stop)<br />
echo -ne "Stopping $NAME.\n"<br />
cd $FUNAMBOL_HOME<br />
/bin/su $FUNAMBOL_USER funambol stop<br />
;;<br />
*)<br />
echo "Usage: /etc/init.d/funambol {start|stop}"<br />
exit 1<br />
;;<br />
esac<br />
exit 0<br />
<br />
complete it with:<br />
<br />
chmod 755 /etc/init.d/funambol<br />
ln -s /etc/init.d/funambol /etc/rc.d/rc7.d/S98funambol<br />
ln -s /etc/init.d/funambol /etc/rc.d/rc6.d/K02funambol<br />
ln -s /etc/init.d/funambol /etc/rc.d/rc2.d/K02funambol<br />
ln -s /etc/init.d/funambol /etc/rc.d/rc1.d/K02funambol<br />
ln -s /etc/init.d/funambol /etc/rc.d/rc0.d/K02funambol<br />
<br />
== Add the SOGo Connector ==<br />
''At this stage the core Funambol installation is complete with the exception of the creation of the Funambol database tables. The sections below add the [http://wiki.contribs.org/Sogo SOGo] parts before doing so.''<br />
<br />
=== Apache Commons Components ===<br />
The Funambol [http://wiki.contribs.org/Sogo SOGo] Connector requires Apache commons collections (v3.2.1), confguration (v1.6), logging (v1.1), lang (v2.4) and the JSON.simple package. The following subsections have the command required to download and insert the .jar files into the Funambol installation.<br />
<br />
These components can be downloaded from here:<br />
<br />
http://commons.apache.org/<br />
<br />
and are copied into the following directory<br />
<br />
cd /opt/Funambol/tools/tomcat/lib/<br />
<br />
==== collections (v3.2.1) ====<br />
wget http://www.apache.org/dist/commons/collections/binaries/commons-collections-3.2.1-bin.zip<br />
unzip commons-collections-3.2.1-bin.zip<br />
cp -p commons-collections-3.2.1/commons-collections-3.2.1.jar /opt/Funambol/tools/tomcat/lib/<br />
rm -rf commons-collections-3.2.1<br />
<br />
==== confguration (v1.6) ====<br />
wget http://www.apache.org/dist/commons/configuration/binaries/commons-configuration-1.6.zip<br />
unzip commons-configuration-1.6.zip<br />
cp -p commons-configuration-1.6/commons-configuration-1.6.jar /opt/Funambol/tools/tomcat/lib/<br />
rm -rf commons-configuration-1.6<br />
<br />
==== logging (v1.1) ====<br />
wget http://www.apache.org/dist/commons/logging/binaries/commons-logging-1.1.1-bin.zip<br />
unzip commons-logging-1.1.1-bin.zip<br />
cp -p commons-logging-1.1.1/commons-logging-1.1.1.jar /opt/Funambol/tools/tomcat/lib/<br />
rm -rf commons-logging-1.1.1<br />
<br />
==== lang (v2.4) ====<br />
wget http://www.apache.org/dist/commons/lang/binaries/commons-lang-2.5-bin.zip<br />
unzip commons-lang-2.5-bin.zip<br />
cp -p commons-lang-2.5/commons-lang-2.5.jar /opt/Funambol/tools/tomcat/lib/<br />
rm -rf commons-lang-2.5<br />
<br />
==== json-simple ====<br />
wget http://json-simple.googlecode.com/files/json_simple.jar<br />
cp json_simple.jar /opt/Funambol/tools/tomcat/lib/<br />
<br />
=== Download & Configure Funambol [http://wiki.contribs.org/Sogo SOGo] Connector ===<br />
Check here: http://www.scalableogo.org/english/downloads/backend.html for the latest version of the <br />
'''Funambol SOGo Connector'''<br />
<br />
wget http://www.scalableogo.org/uploads/Funambol/funambol-sogo-1.0.7.s4j<br />
cp funambol-sogo-1.0.7.s4j /opt/Funambol/ds-server/modules<br />
<br />
Then, open the '''/opt/Funambol/ds-server/install.properties''' file <br />
<br />
vim /opt/Funambol/ds-server/install.properties<br />
<br />
and add '''funambol-sogo-1.0.7''' at the end of the "modules-to-install" line.<br />
<br />
== Install Modules and Create Funambol Database Tables ==<br />
<br />
With Funambol ready to go and the SOGo modules in place, Funambol needs to be configured and the database tables created by issuing the following commands :<br />
<br />
cd /opt/Funambol/<br />
./bin/install<br />
<br />
Answer 'yes' to all questions.<br />
<br />
Once complete, update file ownerships for all files in the '''/opt/Funambol''' tree (''the install creates a couple of configuration and log files in the /opt/Funambiol tree''):<br />
<br />
chown -R funambol:funambol /opt/Funambol/<br />
<br />
Funambol is now installed. Start the Funambol server as the '''funambol''' user using:<br />
<br />
/etc/init.d/funambol start<br />
<br />
== Verify Funambol Installation ==<br />
<br />
Have a quick look if Funambol is running correctly by accessing the web page on:<br />
<br />
http://<server_domain_name>:8080/funambol/ds<br />
<br />
if the server is running, a web page with Funambol Data Synchronization Service information will appear.<br />
<br />
== Change Funambol Admin Password ==<br />
<br />
The default Funambol admin password is '''sa'''. This can be changed with the '''admin-passwd''' utility but it needs a small fix to load the MySQL connector correctly.<br />
<br />
Edit '''/opt/Funambol/bin/admin-passwd'''<br />
<br />
vim /opt/Funambol/bin/admin-passwd<br />
<br />
and change the line with '''JDBC_JAR''' near the top of the file to:<br />
<br />
JDBC_JAR=/opt/Funambol/tools/mysql/lib/mysql-connector-java-5.0.8-bin.jar<br />
<br />
Save and run:<br />
<br />
cd /opt/Funambol<br />
./bin/admin-passwd<br />
<br />
and follow the prompts.<br />
<br />
== Public Access to Funambol ==<br />
And if you want to access Funambol outside your local network, you must open port 8080:<br />
<br />
config set funambol service access public status enabled TCPPort 8080<br />
signal-event remoteaccess-update<br />
<br />
{{Warning box|Port 8080 may conflict with other software installations!}}<br />
{{Note box|TODO: work out where the Funambol port is configured and template it for easy change.}}<br />
{{Note box|TODO: setup apache to proxy the funambol port.}}<br />
<br />
== Create SOGo Sync Sources ==<br />
The SOGo-Funambol documentation describes how to create the '''sogo-cal''', '''sogo-card''' and '''sogo-todo''' sync sources through the Funambol administration tool. There are Windows versions of this tool that can be run from a PC and connect to the Funambol server we just installed.<br />
<br />
However, the commands below emulate this process and creates entries in the funambol database and the sections below create templated versions of the required XML files, as this allows the [http://wiki.contribs.org/Sogo SOGo] database password to be inserted into these XML files.<br />
<br />
The section below inserts the required entries into the funambol database. The next sections create and expand the template files as needed to complete the configuration for [http://wiki.contribs.org/Sogo SOGo].<br />
<br />
=== Create Funambol Database Sync Source Entries ===<br />
Create a temporary SQL file:<br />
<br />
vim sogo-sync-source-insert.sql<br />
<br />
and insert:<br />
<br />
INSERT INTO `fnbl_sync_source` (`uri`, `config`, `name`, `sourcetype`) VALUES<br />
('sogo-cal', 'sogo/sogo/sogo/sogo-cal.xml', 'sogo-cal', 'sogo'),<br />
('sogo-card', 'sogo/sogo/sogo/sogo-card.xml', 'sogo-card', 'sogo'),<br />
('sogo-todo', 'sogo/sogo/sogo/sogo-todo.xml', 'sogo-todo', 'sogo');<br />
<br />
save the file and then insert the SQL into the funambol database:<br />
<br />
mysql funambol --user=funambol --password=yourpassword < sogo-sync-source-insert.sql<br />
<br />
=== Configuring the Calendar Sync connection ===<br />
mkdir -p /opt/Funambol/config/sogo/sogo/sogo<br />
mkdir -p /etc/e-smith/templates/opt/Funambol/config/sogo/sogo/sogo/sogo-cal.xml<br />
cd /etc/e-smith/templates/opt/Funambol/config/sogo/sogo/sogo/sogo-cal.xml<br />
touch template-begin<br />
<br />
Edit a new file with:<br />
<br />
vim sogo-cal.xml<br />
<br />
And insert the following. Note the ''$sogod{'DbPassword'}'' in the scripts below. This pulls in the the database password that SOGO uses to access the MySQL database.<br />
<br />
<nowiki><?xml version="1.0" encoding="UTF-8"?></nowiki><br />
<nowiki><java version="1.5.0_10" class="java.beans.XMLDecoder"></nowiki><br />
<nowiki><object class="ca.inverse.sogo.engine.source.SOGoSyncSource"></nowiki><br />
<nowiki><void property="databasePassword"></nowiki><br />
<nowiki><string>{$sogod{'DbPassword'}}</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="databaseURL"></nowiki><br />
<nowiki><string>jdbc:mysql://localhost/sogo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="databaseUsername"></nowiki><br />
<nowiki><string>sogo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="info"></nowiki><br />
<nowiki><object class="com.funambol.framework.engine.source.SyncSourceInfo"></nowiki><br />
<nowiki><void property="supportedTypes"></nowiki><br />
<nowiki><array class="com.funambol.framework.engine.source.ContentType" length="1"></nowiki><br />
<nowiki><void index="0"></nowiki><br />
<nowiki><object class="com.funambol.framework.engine.source.ContentType"></nowiki><br />
<nowiki><void property="type"></nowiki><br />
<nowiki><string>text/x-vevent</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="version"></nowiki><br />
<nowiki><string>1</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></array></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="name"></nowiki><br />
<nowiki><string>sogo-cal</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="sourceURI"></nowiki><br />
<nowiki><string>sogo-cal</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></java></nowiki><br />
<br />
And don't forget to:<br />
<br />
expand-template /opt/Funambol/config/sogo/sogo/sogo/sogo-cal.xml<br />
<br />
=== Configuring the Address Book Sync connection ===<br />
mkdir -p /etc/e-smith/templates/opt/Funambol/config/sogo/sogo/sogo/sogo-card.xml<br />
cd /etc/e-smith/templates/opt/Funambol/config/sogo/sogo/sogo/sogo-card.xml<br />
touch template-begin<br />
vim sogo-card.xml<br />
<br />
Insert the following:<br />
<br />
<nowiki><?xml version="1.0" encoding="UTF-8"?></nowiki><br />
<nowiki><java version="1.5.0_10" class="java.beans.XMLDecoder"></nowiki><br />
<nowiki><object class="ca.inverse.sogo.engine.source.SOGoSyncSource"></nowiki><br />
<nowiki><void property="databasePassword"></nowiki><br />
<nowiki><string>{$sogod{'DbPassword'}}</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="databaseURL"></nowiki><br />
<nowiki><string>jdbc:mysql://localhost/sogo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="databaseUsername"></nowiki><br />
<nowiki><string>sogo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="info"></nowiki><br />
<nowiki><object class="com.funambol.framework.engine.source.SyncSourceInfo"></nowiki><br />
<nowiki><void property="supportedTypes"></nowiki><br />
<nowiki><array class="com.funambol.framework.engine.source.ContentType" length="1"></nowiki><br />
<nowiki><void index="0"></nowiki><br />
<nowiki><object class="com.funambol.framework.engine.source.ContentType"></nowiki><br />
<nowiki><void property="type"></nowiki><br />
<nowiki><string>text/x-vcard</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="version"></nowiki><br />
<nowiki><string>1</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></array></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="name"></nowiki><br />
<nowiki><string>sogo-card</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="sourceURI"></nowiki><br />
<nowiki><string>sogo-card</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></java></nowiki><br />
<br />
And<br />
<br />
expand-template /opt/Funambol/config/sogo/sogo/sogo/sogo-card.xml<br />
<br />
=== Configuring the Todo List Sync connection ===<br />
mkdir -p /etc/e-smith/templates/opt/Funambol/config/sogo/sogo/sogo/sogo-todo.xml<br />
cd /etc/e-smith/templates/opt/Funambol/config/sogo/sogo/sogo/sogo-todo.xml<br />
touch template-begin<br />
vim sogo-todo.xml<br />
<br />
Insert the following:<br />
<br />
<nowiki><?xml version="1.0" encoding="UTF-8"?></nowiki><br />
<nowiki><java version="1.5.0_10" class="java.beans.XMLDecoder"></nowiki><br />
<nowiki><object class="ca.inverse.sogo.engine.source.SOGoSyncSource"></nowiki><br />
<nowiki><void property="databasePassword"></nowiki><br />
<nowiki><string>{$sogod{'DbPassword'}}</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="databaseURL"></nowiki><br />
<nowiki><string>jdbc:mysql://localhost/sogo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="databaseUsername"></nowiki><br />
<nowiki><string>sogo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="info"></nowiki><br />
<nowiki><object class="com.funambol.framework.engine.source.SyncSourceInfo"></nowiki><br />
<nowiki><void property="supportedTypes"></nowiki><br />
<nowiki><array class="com.funambol.framework.engine.source.ContentType" length="1"></nowiki><br />
<nowiki><void index="0"></nowiki><br />
<nowiki><object class="com.funambol.framework.engine.source.ContentType"></nowiki><br />
<nowiki><void property="type"></nowiki><br />
<nowiki><string>text/x-vtodo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="version"></nowiki><br />
<nowiki><string>1</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></array></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="name"></nowiki><br />
<nowiki><string>sogo-todo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="sourceURI"></nowiki><br />
<nowiki><string>sogo-todo</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></java></nowiki><br />
<br />
And<br />
<br />
expand-template /opt/Funambol/config/sogo/sogo/sogo/sogo-todo.xml<br />
<br />
== Auto-create Funambol user accounts ==<br />
Edit the Funambol config file<br />
<br />
vim /opt/Funambol/config/Funambol.xml<br />
<br />
And change the officer parameter:<br />
<br />
<nowiki><void property="officer"></nowiki><br />
<nowiki><string>ca/inverse/sogo/security/SOGoOfficer.xml</string></nowiki><br />
<nowiki></void></nowiki><br />
<br />
Then create the SOGoOfficer.xml file<br />
<br />
vim /opt/Funambol/config/ca/inverse/sogo/security/SOGoOfficer.xml<br />
<br />
and insert or update to:<br />
<br />
<nowiki><?xml version="1.0" encoding="UTF-8"?></nowiki><br />
<nowiki><java version="1.4.0" class="java.beans.XMLDecoder"></nowiki><br />
<nowiki><object class="ca.inverse.sogo.security.SOGoOfficer"></nowiki><br />
<nowiki><void property="host"></nowiki><br />
<nowiki><string>localhost</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki><void property="port"></nowiki><br />
<nowiki><string>20000</string></nowiki><br />
<nowiki></void></nowiki><br />
<nowiki></object></nowiki><br />
<nowiki></java></nowiki><br />
<br />
== Cleanup and Restart ==<br />
<br />
Once complete, update file ownerships for all files again in the '''/opt/Funambol''' tree<br />
<br />
chown -R funambol:funambol /opt/Funambol/<br />
<br />
Stop and Start the Funambol server as the '''funambol''' user using:<br />
<br />
/etc/init.d/funambol stop<br />
/etc/init.d/funambol start<br />
<br />
== Funambol Client Configuration ==<br />
<br />
The URL for accessing the Funambol server from mobile devices is:<br />
<br />
http://<server_domain_name>:8080/funambol/ds<br />
<br />
To connect to the SOGO Funambol sync items use:<br />
<br />
* Contacts: sogo-card<br />
* Calendar: sogo-cal<br />
* Tasks: sogo-todo<br />
<br />
== References ==<br />
* Funambol Documentation: https://www.forge.funambol.org/download/documentation.html<br />
* SOGo Documentation: http://www.sogo.nu/english/downloads/documentation.html<br />
<br />
----<br />
[[Category: Howto]]</div>
Byte
https://wiki.koozali.org/index.php?title=DB_Variables_Configuration&diff=13833
DB Variables Configuration
2009-11-27T22:35:27Z
<p>Byte: /* Database variables */</p>
<hr />
<div>== Database variables ==<br />
SME Server comes with the most used parameters set as variables in its internal configuration databases. These variables are used to store values to be used in the final configuration files. Please, read the [http://mirror.contribs.org/smeserver/contribs/gordonr/devguide/html/devguide.html#SME-INTERNALS SME Server Developer's Guide] to understand the template and database process.<br />
<br />
These variables are useful to configure your system more easily, as you do not need to modify configuration files directly for most common cases. It also makes it possible to administer the server through its server-manager as the database variables are used to set and change configuration parameters. After editing, the configuration files must be regenerated and affected services need to be restarted.<br />
<br />
For example, suppose you need to increase "memory-limit" in php.<br />
<br />
You would simply execute these commands at the server console:<br />
<br />
db configuration setprop php MemoryLimit 64M<br />
expand-template /etc/php.ini<br />
/etc/init.d/httpd-e-smith restart<br />
<br />
The first line changes the value for the memory limit of PHP, the second line regenerates the configuration file and the last line will reload Apache (and subsequently also PHP as this is configured as a module of Apache).<br />
<br />
{{Warning box|Database parameters are case sensitive so take great care when typing at the server shell because no error messages are given should you make a typo.}}<br />
<br />
The database system is based on a flat file system, but you should never edit them directly. Instead you should use the db command. More details on using the database system can be found in the [http://mirror.contribs.org/smeserver/contribs/gordonr/devguide/html/devguide.html#SME-INTERNALS SME Server Developer's Guide].<br />
<br />
<br />
=== Setting db variables to default values ===<br />
Any db variable that has a default value can be reset to the default by deleting the variable entirely, then re-initializing the default database values as follows:<br />
config delprop key prop<br />
/etc/e-smith/events/actions/initialize-default-databases<br />
<br />
<br />
===Concept of the signal-event command===<br />
Thanks for the developers work, you can simplify more the commands using the signal-event proccess.<br />
<br />
Again, for more details see [http://mirror.contribs.org/smeserver/contribs/gordonr/devguide/html/devguide.html#SME-INTERNALS SME Server Developer's Guide]<br />
<br />
<br />
=== Overview of database variables ===<br />
The next section describes the standard variables defined on SME Server. Please update this list with new standard variables in future SME Server versions.<br />
<br />
The tables below have three columns. The first is the variable, the second is the target variable (located in the final configuration file), and the third is the default value.<br />
<br />
A lot of the variables can be set using the server-manager but some can not. For example the variable DomainMaster for samba is not important here, because this can be set through server-manager. On the other hand, the variable RecycleBin is important, because it is not accessible through the server-manager.<br />
<br />
Configuration files may use database values from a single configuration key, or may use multiple keys. The latter is the case for the /etc/rc.d/init.d/masq configuration file. This file takes it values from multiple database keys such as squid and masq.<br />
<br />
It is also possible that multiple configuration files use the same key. An example of this is the httpd-admin key. This key has a variable TCPPort which is used in multiple files (/etc/httpd/admin-conf/httpd.conf and /etc/services).<br />
<br />
<br />
==== AppleTalk (atalk) ====<br />
''Usage''<br />
db configuration setprop atalk variable value<br />
signal-event workgroup-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/atalk/netatalk.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|MaxClients<br />
|AFPD_MAX_CLIENTS<br />
|20<br />
|}<br />
<br />
<br />
==== Console Mode ====<br />
''Usage'' - Choose either login or auto DB variable. <br />
config set ConsoleMode login<br />
signal-event post-upgrade<br />
signal-event reboot<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|ConsoleMode<br />
|Console Setting<br />
|login<br />
|}<br />
<br />
<br />
==== Clam AntiVirus (clamav) ====<br />
''Usage''<br />
db configuration setprop clamav variable value<br />
signal-event clamav-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/clamd.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|ArchiveBlockEncrypted<br />
|ArchiveBlockEncrypted<br />
|no<br />
|-<br />
|ArchiveBlockMax<br />
|ArchiveBlockMax<br />
|no<br />
|-<br />
|ArchiveMaxCompressionRatio<br />
|ArchiveMaxCompressionRatio<br />
|300<br />
|-<br />
|ArchiveMaxFiles<br />
|ArchiveMaxFiles<br />
|1500<br />
|-<br />
|ArchiveMaxFileSize<br />
|ArchiveMaxFileSize<br />
|15M<br />
|-<br />
|ArchiveMaxRecursion<br />
|ArchiveMaxRecursion<br />
|8<br />
|-<br />
|Debug<br />
|Debug<br />
|no<br />
|-<br />
|DetectBrokenExecutables<br />
|DetectBrokenExecutables<br />
|no<br />
|-<br />
|FilesystemScanExclude<br />
|FilesystemScanExclude<br />
|/proc,/sys,/usr/share,/var<br />
|-<br />
|IdleTimeout<br />
|IdleTimeout<br />
|60<br />
|-<br />
|LeaveTemporaryFiles<br />
|LeaveTemporaryFiles<br />
|no<br />
|-<br />
|LogClean<br />
|LogClean<br />
|yes<br />
|-<br />
|LogTime<br />
|LogTime<br />
|yes<br />
|-<br />
|LogVerbose<br />
|LogVerbose<br />
|yes<br />
|-<br />
|MaxConnectionQueueLength<br />
|MaxConnectionQueueLength<br />
|30<br />
|-<br />
|MaxDirectoryRecursion<br />
|MaxDirectoryRecursion<br />
|20<br />
|-<br />
|MaxThreads<br />
|MaxThreads<br />
|20<br />
|-<br />
|ReadTimeout<br />
|ReadTimeout<br />
|300<br />
|-<br />
|ScanArchive<br />
|ScanArchive<br />
|yes<br />
|-<br />
|ScanHTML<br />
|ScanHTML<br />
|yes<br />
|-<br />
|ScanMail<br />
|ScanMail<br />
|yes<br />
|-<br />
|ScanOLE2<br />
|ScanOLE2<br />
|yes<br />
|-<br />
|ScanPE<br />
|ScanPE<br />
|yes<br />
|-<br />
|SelfCheck<br />
|SelfCheck<br />
|1800<br />
|-<br />
|StreamMaxLength<br />
|StreamMaxLength<br />
|25M<br />
|}<br />
<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/freshclam.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Checks<br />
|Checks<br />
|24<br />
|-<br />
|DatabaseMirror<br />
|DatabaseMirror<br />
|db.local.clamav.net<br />
|-<br />
|DNSDatabaseInfo<br />
|DNSDatabaseInfo<br />
|current.cvd.clamav.net<br />
|-<br />
|LogVerbose<br />
|LogVerbose<br />
|yes<br />
|-<br />
|MaxAttempts<br />
|MaxAttempts<br />
|6<br />
|}<br />
<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /var/service/clamd/env/MEMLIMIT<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|MemLimit<br />
|MEMLIMIT<br />
|80000000<br />
|}<br />
<br />
==== DHCP daemon (dhcpd) ====<br />
''Usage''<br />
db configuration setprop dhcpd variable value<br />
signal-event remoteaccess-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/dhcpd.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Bootp<br />
|bootp<br />
|deny<br />
|-<br />
|startDynamicIPRange<br />
|range<br />
|<br />
|-<br />
|endDynamicIPRange<br />
|range<br />
|<br />
|-<br />
|}<br />
Note: the end of the dynamic IP range will be set to the value of 'endDynamicIPRange' ''minus'' the value of pptpd:sessions.<br />
<br />
==== DNS Cache Forwarder (dnscache.forwarder) ====<br />
''Usage''<br />
db configuration setprop dnscache variable value<br />
signal-event dns-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /var/service/dnscache.forwarder/config<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|CacheSize<br />
|CACHESIZE<br />
|1000000<br />
|-<br />
|DataLimit<br />
|DATALIMIT<br />
|3000000<br />
|}<br />
<br />
<br />
==== FlexBackup ====<br />
''Usage''<br />
db configuration setprop flexbackup variable value<br />
signal-event conf-backup<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/flexbackup.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Blocksize<br />
|$blksize<br />
|32<br />
|-<br />
|TapeBlocksize<br />
|$mt_blksize<br />
|0<br />
|-<br />
|BufferProg<br />
|$buffer<br />
|buffer<br />
|-<br />
|BufferMegs<br />
|$buffer_megs<br />
|20<br />
|-<br />
|erase_rewind_only<br />
|$erase_rewind_only<br />
|false<br />
|-<br />
|Type<br />
|$type<br />
|tar<br />
|}<br />
<br />
<br />
==== Horde (webmail) ====<br />
''Usage''<br />
db configuration setprop horde variable value<br />
<br />
expand-template /home/httpd/html/horde/conf.menu.aps.php<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /home/httpd/html/horde/conf.menu.aps.php<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|MenuArray<br />
|MenuArray<br />
|enabled<br />
|}<br />
<br />
<br />
expand-template /home/httpd/html/horde/config/conf.php<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /home/httpd/html/horde/config/conf.php<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Administration<br />
|Administration<br />
|disabled<br />
|}<br />
<br />
expand-template /etc/e-smith/templates/home/httpd/html/horde/config/prefs.php/200personal<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/e-smith/templates/home/httpd/html/horde/config/prefs.php/200personal<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Name<br />
|'My Company'<br />
|'Horde Webmail'<br />
|}<br />
<br />
<br />
expand-template /home/httpd/html/horde/turba/config/sources.php<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /home/httpd/html/horde/turba/config/sources.php<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|freebusy<br />
|freebusy<br />
|disabled<br />
|-<br />
|SharedAddressBooks<br />
|SharedAddressBooks<br />
|disabled<br />
|}<br />
<br />
<br />
==== Apache server ibay specific (httpd-e-smith) ====<br />
''Usage''<br />
db accounts setprop ibayname variable value<br />
signal-event ibay-modify ibayname<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/httpd/conf/httpd.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|AllowOverride<br />
|AllowOverride<br />
|None<br />
|-<br />
|FollowSymLinks<br />
|FollowSymLinks<br />
|disabled<br />
|-<br />
|Indexes<br />
|Indexes<br />
|enabled<br />
|-<br />
|PHPRegisterGlobals<br />
|register_globals<br />
|disabled<br />
|-<br />
|PHPBaseDir<br />
|open_basedir<br />
|/home/e-smith/files/ibays/ibayname<br />
|-<br />
|SSLv2<br />
|SSLProtocol<br />
|disabled<br />
|}<br />
<br />
==== Apache server-manager (httpd-admin) ====<br />
''Usage''<br />
db configuration setprop httpd-admin variable value<br />
signal-event remoteaccess-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/httpd/admin-conf/httpd.conf and /etc/services<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|TCPPort<br />
|TCPPort<br />
|980<br />
|}<br />
<br />
<br />
==== IMAP (imap) ====<br />
''Usage''<br />
db configuration setprop imap variable value<br />
signal-event email-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /var/service/imap/config<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|ConcurrencyLimit<br />
|INSTANCES<br />
|2000<br />
|-<br />
|ConcurrencyLimitPerIP<br />
|INSTANCES_PER_IP<br />
|12<br />
|-<br />
|ProcessMemoryLimit<br />
|ulimitdata<br />
|128000000<br />
|}<br />
<br />
<br />
==== IMAPS (imaps) ====<br />
''Usage''<br />
db configuration setprop imaps variable value<br />
signal-event email-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /var/service/imaps/config<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|ConcurrencyLimit<br />
|INSTANCES<br />
|2000<br />
|-<br />
|ConcurrencyLimitPerIP<br />
|INSTANCES_PER_IP<br />
|12<br />
|-<br />
|ProcessMemoryLimit<br />
|ulimitdata<br />
|128000000<br />
|}<br />
<br />
<br />
==== IPTables firewall (masq) ====<br />
''Usage''<br />
db configuration setprop masq variable value<br />
signal-event remoteaccess-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/rc.d/init.d/masq<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Logging<br />
|Logging<br />
|most<br />
|-<br />
|Stealth<br />
|Stealth<br />
|no<br />
|}<br />
<br />
<br />
{{Tip box|Special case is TCPPort and UDPPort from any DB key.<br />
<br />
Any Db key named "TCPPort" or "UDPPort" affect masq file.<br />
<br />
Currently the following keys are included in masq:<br />
<br />
'''TCPPort:'''<br />
<br />
''httpd-admin - sshd - smtpd - ssmtpd''<br />
}}<br />
<br />
<br />
=====Additional information on customizing iptables=====<br />
Create a custom-named service definition in the configuration database.<br />
<br />
db configuration set <servicename> service<br />
<br />
Apply your desired firewall restrictions to any existing SME 'service' or to a custom-named service that you have created. Combine a custom-named service with port-forwarding to create customized firewall rules.<br />
<br />
db configuration setprop <servicename> TCPPort <portnumber><br />
db configuration setprop <servicename> TCPPorts <portnumbers><br />
db configuration setprop <servicename> UDPPort <portnumber><br />
db configuration setprop <servicename> UDPPorts <portnumbers><br />
db configuration setprop <servicename> status enabled|disabled<br />
db configuration setprop <servicename> access public|private<br />
db configuration setprop <servicename> AllowHosts a.b.c.d,x.y.z.0/24<br />
db configuration setprop <servicename> DenyHosts e.f.g.h,l.m.n.0/24<br />
<br />
Effectuate the changes you have made<br />
signal-event remoteaccess-update<br />
<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/rc.d/init.d/masq<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|TCPPort<br />
| --proto tcp --dport <Ports><br />
|Pre-configured for default services; no default for custom services<br />
|-<br />
|TCPPorts<br />
| --proto tcp --dports <Ports><br />
|No default for custom services; Ranges of ports are defined with a : not a -<br />
|-<br />
|UDPPort<br />
| --proto udp --dport <Ports><br />
|Pre-configured for default services; no default for custom services<br />
|-<br />
|UDPPorts<br />
| --proto udp --dports <Ports><br />
|No default for custom services; Ranges of ports are defined with a : not a -<br />
|-<br />
|status<br />
|enabled | disabled<br />
|AllowHosts is set to "" (an empty string) unless the status is 'enabled'<br />
|-<br />
|access<br />
|public | private<br />
|AllowHosts is set to "" (an empty string) unless access is 'public'<br />
|-<br />
|AllowHosts<br />
| --src ..... --jump ACCEPT<br />
|Pre-configured for default services; no default for custom services. Default is '0.0.0.0/0' if service is ''enabled'' and ''public''.<br />
|-<br />
|DenyHosts<br />
| --src ..... --jump denylog<br />
|Pre-configured for default services; no default for custom services. If 'DenyHosts' is empty or does not exist then there are no '... --jump denylog' entries created in /etc/init.d/masq.<br />
|}<br />
<br />
==== SpamAssasin ====<br />
''Usage''<br />
db configuration setprop spamassassin variable value<br />
signal-event email-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/mail/spamassassin/local.cf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|DNSAvailable<br />
|dns_available<br />
|yes<br />
|-<br />
|OkLanguages<br />
|ok_languages<br />
|all<br />
|-<br />
|OkLocales<br />
|ok_locales<br />
|all<br />
|-<br />
|ReportSafe<br />
|report_safe<br />
|0<br />
|-<br />
|Subject<br />
|rewrite_header Subject<br />
|[SPAM]<br />
|-<br />
|SkipRBLChecks<br />
|skip_rbl_checks<br />
|0<br />
|-<br />
|TrustedNetworks<br />
|trusted_networks<br />
|127.<br />
|-<br />
|UseAutoWhitelist<br />
|use_auto_whitelist<br />
|0<br />
|-<br />
|UseBayes<br />
|use_bayes<br />
|0<br />
|-<br />
|Sensitivity<br />
|required_hits<br />
|medium<br />
|}<br />
<br />
<br />
==== MySQL (mysqld) ====<br />
''Usage''<br />
db configuration setprop mysqld variable value<br />
expand-template /etc/my.cnf<br />
sv t /service/mysqld<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/my.cnf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|InnoDB<br />
|InnoDB<br />
|disabled<br />
|-<br />
|LocalNetworkingOnly<br />
|LocalNetworkingOnly<br />
|yes<br />
|}<br />
<br />
==== Network Time Protocol (ntpd) ====<br />
''Usage''<br />
db configuration setprop ntpd variable value<br />
signal-event timeserver-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /var/service/ntpd/env/MEMLIMIT<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|MemLimit<br />
|MEMLIMIT<br />
|12000000<br />
|}<br />
<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/ntp/step-tickers and /etc/ntp.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|NTPServer<br />
|server<br />
|pool.ntp.org<br />
|-<br />
|SyncToHWClockSupported<br />
|SyncToHWClockSupported<br />
|yes<br />
|}<br />
<br />
<br />
==== Php ====<br />
''Usage''<br />
db configuration setprop php variable value<br />
expand-template /etc/php.ini<br />
/etc/init.d/httpd-e-smith restart<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/php.ini<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|MaxExecutionTime<br />
|max_execution_time<br />
|30<br />
|-<br />
|MemoryLimit<br />
|memory_limit<br />
|32M<br />
|-<br />
|PostMaxSize<br />
|post_max_size<br />
|20M<br />
|-<br />
|UploadMaxFilesize<br />
|upload_max_filesize<br />
|10M<br />
|-<br />
|AllowUrlFopen<br />
|allow_url_fopen<br />
|Off<br />
|}<br />
''Don't forget "M" unit because you get a lot of httpd errors and apache can't start!''<br />
<br />
<br />
==== Virtual Private Network (VPN) (pptpd) ====<br />
''Usage''<br />
db configuration setprop pptpd variable value<br />
signal-event remoteaccess-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/ppp/options.pptpd<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|debug<br />
|debug<br />
|no<br />
|-<br />
|mtu<br />
|mtu<br />
|not set by default, add your value (1404) after mtu<br />
|-<br />
|mru<br />
|mru<br />
|not set by default, add your value (1404) after mru<br />
-<br />
|-<br />
|Passive<br />
|passive<br />
|enabled<br />
|}<br />
<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/pptpd.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|debug<br />
|debug<br />
|no<br />
|}<br />
<br />
<br />
==== Pro FTP (proftpd) ====<br />
''Usage''<br />
db configuration setprop ftp variable value<br />
signal-event remoteaccess-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/proftpd.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|DisableAnonymous<br />
|DisableAnonymous<br />
|no<br />
|}<br />
<br />
<br />
==== Samba global settings (smbd) ====<br />
''Usage''<br />
db configuration setprop smb variable value<br />
signal-event ibay-modify <br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/samba/smb.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|RecycleBin<br />
|recycle<br />
|disabled<br />
|-<br />
|ShadowCopy<br />
|shadow_copy<br />
|disabled<br />
|-<br />
|DeadTime<br />
|deadtime<br />
|10080<br />
|-<br />
|DisplayCharSet<br />
|display charset<br />
|ISO8859-1<br />
|-<br />
|DosCharSet<br />
|dos charset<br />
|850<br />
|-<br />
|LogonDrive<br />
|logon drive<br />
|Z<br />
|-<br />
|OpLocks<br />
|oplocks<br />
|enabled<br />
|-<br />
|OsLevel<br />
|os level<br />
|65<br />
|-<br />
|ServerString<br />
|server string<br />
|SME Server<br />
|-<br />
|SMBPorts<br />
|smb ports<br />
|139<br />
|-<br />
|UnixCharSet<br />
|unix charset<br />
|UTF8<br />
|-<br />
|UseClientDriver<br />
|use client driver<br />
|yes<br />
|}<br />
<br />
<br />
==== Samba per i-bay settings (smbd) ====<br />
<br />
''Usage''<br />
db accounts setprop ibay_name variable value<br />
signal-event ibay-modify <br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/samba/smb.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Browseable<br />
|browseable<br />
|enabled<br />
|-<br />
|OpLocks<br />
|oplocks<br />
|enabled<br />
|-<br />
|RecycleBin<br />
|recycle<br />
|disabled<br />
|-<br />
|VetoOplockFiles<br />
|veto oplock files<br />
|(not set)<br />
|}<br />
<br />
==== Squid Proxy (squid) ====<br />
''Usage''<br />
db configuration setprop squid variable value<br />
signal-event proxy-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/squid/squid.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|SafePorts<br />
|acl Safe_ports port<br />
|80<br />
|-<br />
|EnforceSafePorts<br />
|EnforceSafePorts<br />
|no<br />
|}<br />
<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/squid/squid.conf and /etc/rc.d/init.d/masq<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Transparent<br />
|Transparent<br />
|yes<br />
|}<br />
<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/rc.d/init.d/masq<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|TransparentPort<br />
|TransparentPort<br />
|3128<br />
|}<br />
<br />
<br />
''Alternate Usage for Configuration of an Up-Stream Proxy Server''<br />
db configuration set squid-parent-variable value<br />
signal-event proxy-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/squid/squid.conf<br />
!squid-parent-variable<br />
!Target<br />
!Default<br />
|-<br />
|SquidParent<br />
|name-or-ip-of-upstream-proxy-server<br />
|(none)<br />
|-<br />
|SquidParentPort<br />
|port-number-used-by-upstream-proxy-server<br />
|(none)<br />
|}(un-do using 'db configuration delete SquidParent', 'signal-event proxy-update')<br />
<br />
<br />
==== SSH (sshd) ====<br />
''Usage''<br />
db configuration setprop sshd variable value<br />
signal-event remoteaccess-update<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/ssh/sshd_config<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|TCPPort<br />
|Port<br />
|22<br />
|-<br />
|Protocol<br />
|Protocol<br />
|2<br />
|-<br />
|UsePAM<br />
|UsePAM<br />
|no<br />
|-<br />
|MaxAuthTries<br />
|MaxAuthTries<br />
|2<br />
|-<br />
|MaxStartups<br />
|MaxStartups<br />
|10:30:60<br />
|-<br />
|PasswordAuthentication<br />
|PasswordAuthentication<br />
|no<br />
|-<br />
|PermitRootLogin<br />
|PermitRootLogin<br />
|no<br />
|-<br />
|AllowHosts <br />
|AllowHosts<br />
|IP address(es) list<br />
|}<br />
<br />
<br />
{{Note box|Currently in SME 7.2 and up, TCPPort is configurable via server-manager, under Remote Access menu.<br />
<br />
To configure AllowHosts:<br />
IP address(es) list is a single IP or a comma separated list of IP addresses and/or netmasks (e.g. 16.17.18.19,203.14.64.0/24).<br />
Ssh will then only be allowed from those IP addresses. The firewall code will drop ssh connections from any other hosts.}}<br />
<br />
<br />
==== smtpd ====<br />
''Usage''<br />
config setprop smtpd variable value<br />
signal-event email-update<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /var/service/qpsmtpd/runenv<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Instances<br />
|Total smtp Instances<br />
|40<br />
|-<br />
|InstancesPerIP<br />
|smtp-Instances-Per-IP<br />
|5<br />
|}<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /var/service/qpsmtpd/config/smtpgreeting<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|Greeting<br />
|Hostname portion of the greeting provided by your server to inbound SMTP connections<br />
|$SystemName.$DomainName<br />
|}<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /var/qmail/control/helohost<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|HeloHost<br />
|SMTP Helo / Ehlo value provided by your server when connecting to external SMTP servers to send email<br />
|$DomainName<br />
|}<br />
<br />
==== yum ====<br />
''Usage''<br />
config setprop yum variable value<br />
signal-event yum-modify<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
|+Affected file: /etc/yum.conf<br />
!Variable<br />
!Target<br />
!Default<br />
|-<br />
|AutoInstallUpdates<br />
|Install updates automatically?<br />
|disabled<br />
|-<br />
|check4updates<br />
|Frequency of Update Checking [[:SME_Server:Documentation:FAQ#Frequency|see here]]<br />
|daily<br />
|-<br />
|EnableGroups<br />
|Enable Groups<br />
|0<br />
|-<br />
|GPGCheck<br />
|Check GPG signature for repositories<br />
|0<br />
|-<br />
|PackageFunctions<br />
|Display individual packages in 'Software Installer'<br />
|disabled<br />
|-<br />
|RandomDelay<br />
|Random Delay<br />
|120<br />
|-<br />
|status<br />
|Yum's status<br />
|enabled<br />
|-<br />
|RestrictRepo<br />
|Repo names whose contents should be excluded from 'Available Packages' in the 'Software Installer'<br />
|none<br />
|-<br />
|RestrictRPM<br />
|All or part of an RPM name to be excluded from 'Available Packages' in the 'Software Installer'<br />
|none<br />
|}<br />
<br />
See also 'db yum_repositories'<br />
<br />
==== Miscellaneous Other DB Variables ====<br />
{{Note box|This is meant to be an easy place to add db variable information if you don't have time to put it into the correct section(s) above. You can find most of the template fragments affected by a given db variable if you execute:<br />
<br />
cd /etc/e-smith<br />
fgrep -lR ''variable'' templ<nowiki>*/* |</nowiki> less<br />
<br />
where ''variable'' is the name of the variable using correct capitalization<br />
<br />
Note that any command listed here is to be executed on one line!}}<br />
<br />
<br />
{| width="100%" border="1" cellpadding="5" cellspacing="0"<br />
!Command<br />
!service(s)<br />
!config file(s)<br />
!notes<br />
|-<br />
|db domains setprop test.com '''MailServer''' a.b.c.d<br />
|qpsmtpd; qmail; fetchmail<br />
|/var/service/qpsmtpd/config/goodrcptto; /var/service/qpsmtpd/config/peers/local; /var/service/qpsmtpd/config/peers/0; /var/service/qpsmtpd/plugins; /var/service/qmail/control/virtualdomains; /var/service/qmail/control/smtproutes; /etc/fetchmail<br />
|Forward all email for the specified domain to the IP address ''a.b.c.d''. ''a.b.c.d'' can be either local or remote. By default, the recipient address will be verified as valid on ''a.b.c.d'' before SME accepts the inbound message.<br />
|-<br />
|config set '''SquidParent''' <hostname or IP><br />
|squid, diald<br />
|/etc/diald.filter, /etc/squid/squid.conf<br />
|Configure squid to peform all web downloads from the specified upstream proxy server<br />
|-<br />
|config set '''SquidParentPort''' <portnumber><br />
|squid<br />
|/etc/squid/squid.conf<br />
|Connect to the upstream proxy server using <portnumber>. Defaults to 3128 if 'SquidParentPort' is unspecified. Ignored if SquidParent is not set.<br />
|-<br />
|config delete '''SquidParent'''<br />
|squid, diald<br />
|/etc/squid/squid.conf, /etc/diald.filter<br />
|Return squid to normal operation (no upstream proxy server)<br />
|-<br />
|db accounts setprop username Visible internal ; signal-event email-update<br />
|n/a<br />
|n/a<br />
|Make an email address invisible from outside? (see http://forums.contribs.org/index.php?topic=36302.0)<br />
|-<br />
|db accounts setprop pseudonym Visible internal ; signal-event email-update<br />
|n/a<br />
|n/a<br />
|Make an pseudonym email address invisible from outside<br />
|-<br />
|db <database> delprop key ''property'' ; /etc/e-smith/events/actions/initialize-default-databases<br />
|various<br />
|various<br />
|Restore the developers' default value for ''property''<br />
|-<br />
|db <database> delete ''key'' ; /etc/e-smith/events/actions/initialize-default-databases<br />
|various<br />
|various<br />
|Restore the developers' default value for each property belonging to the key ''key''<br />
|-<br />
|config set '''AdminIsNotRoot''' enabled<br />
|n/a<br />
|n/a<br />
|In server-manager panel, changing admin password no more change root password. root password is managed through '''passwd''' shell command and admin and root passwords can be distinct passwords.<br />
|-<br />
|config setprop smtp-auth-proxy PeerPort xxx; signal-event email-update<br />
|smtp-auth-proxy<br />
|none - the smtp-auth-proxy executable (//usr/local/sbin/smtp-auth-proxy.pl) reads the config database directly.<br />
|Used to change the port number used to connect to the upstream mail server ("SMTPSmartHost" or "Address of Internet provider's mail server"). Defaults to port 25 if PeerPort is not set; uses SSL if port 465 is selected.<br />
|-<br />
|command<br />
|service(s)<br />
|config file(s)<br />
|notes. Copy this block when adding new entries to this table.<br />
|}<br />
<br />
<br />
<br />
----<br />
<noinclude>[[Category:Howto]]</noinclude></div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=13787
SME Server 8
2009-11-07T18:30:42Z
<p>Byte: /* Performing the upgrade */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. SME Server 8.0beta4 is based on CentOS 5.3.<br />
<br />
See the [http://forums.contribs.org/index.php/topic,44334.0.html Release Announcement for Beta4].<br />
<br />
A copy of the Beta4 CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing===<br />
<br />
Coordinator<br />
* Gavin Weight<br />
<br />
All users are encouraged to test, see our draft quality assurance testing page for tasks [[SME8.0 QA]]<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
<br />
Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating. For testing of contribs in advance of release see [[SME8.0 Contribs QA]]<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Pointing repositories to SME 8=====<br />
Update the MirrorList property to point to the sme8 lists...<br />
<br />
db yum_repositories print | grep '^sme' | cut -d= -f1 | while read repo<br />
do<br />
db yum_repositories setprop $repo MirrorList \<br />
<nowiki>http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/$repo-8</nowiki><br />
done<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====Performing the upgrade=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
<ol></li><li>Clean out the yum cache so upgrades work:<br />
rm -rf /var/cache/yum/*<br />
</li><li>Perform the upgrade:<br />
yum --disablerepo=smeextras --enablerepo=smeupdates-testing upgrade<br />
</li><li>Remove outdated rpm database and rebuild it (zeros not O's)<br />
rm -f /var/lib/rpm/__db.00*<br />
rpm --rebuilddb<br />
</li><li>Reset yum updates repositories to defaults<br />
db yum_repositories delete updates<br />
/etc/e-smith/events/actions/initialize-default-databases<br />
</li><li>Perform a post-upgrade and reboot<br />
signal-event post-upgrade<br />
signal-event reboot<br />
</li></ol><br />
<br />
=====Potential issues that may arise=====<br />
If you are running a 7.0 system you may need to upgrade smeserver-yum.<br />
<ol></li><li>Check which version of smeserver-yum you are running:<br />
rpm -q smeserver-yum<br />
</li><li>If it isn't at least <b>1.2.0-25.el4.sme</b> install an updated version:<br />
rpm -Uvh \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/smeserver-yum-1.2.0-25.el4.sme.noarch.rpm</nowiki> \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/yum-plugin-fastestmirror-0.2.4-3.c4.noarch.rpm</nowiki><br />
</li></ol><br />
<br />
If you receive the following error while trying to upgrade:<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
Solve it by installing the correct version of yum-metadata-parser:<br />
rpm -Uvh --oldpackage \<br />
<nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=13673
SME Server 8
2009-11-03T17:57:33Z
<p>Byte: /* Setting up your SME Server 8 repository */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. SME Server 8.0beta4 is based on CentOS 5.3.<br />
<br />
See the [http://forums.contribs.org/index.php/topic,44334.0.html Release Announcement for Beta4].<br />
<br />
A copy of the Beta4 CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing===<br />
<br />
Coordinator<br />
* Gavin Weight<br />
<br />
All users are encouraged to test, see our draft quality assurance testing page for tasks [[SME8.0_QA]]<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
<br />
Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating. For testing of contribs in advance of release see [[SME8.0_Contribs_QA]]<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Check to make sure your server has the prerequisites:<br />
<br />
rpm -q smeserver-yum<br />
<br />
If your version isn't at least 1.2.0-21, then upgrade as below:<br />
<br />
rpm -Uvh http://mirror.contribs.org/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/smeserver-yum-1.2.0-25.el4.sme.noarch.rpm \<br />
http://mirror.contribs.org/smeserver/releases/obsolete/7.1/smeos/i386/CentOS/RPMS/yum-plugin-fastestmirror-0.2.4-3.c4.noarch.rpm<br />
<br />
Setting up the repos/yum for upgrade to take place:<br />
<br />
db yum_repositories print | grep '^sme' | cut -d= -f1 | while read repo<br />
do<br />
db yum_repositories setprop $repo MirrorList http://distro.ibiblio.org/pub/linux/distributions/smeserver/mirrorlist/$repo-8<br />
done<br />
signal-event yum-modify<br />
rm -rf /var/cache/yum/*<br />
<br />
Now perform the upgrade (--enable smeupdates-testing may be needed)<br />
<br />
yum --disablerepo smeextras upgrade<br />
<br />
Complete the final post upgrade steps:<br />
<br />
rm -f /var/lib/rpm/__db.00*<br />
rpm --rebuilddb<br />
signal-event post-upgrade<br />
signal-event reboot<br />
<br />
=====SME Server 7.4=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.4 may upgrade, detail review of upgrade paths will start with RC versions.<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os --enablerepo=sme8updates<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x, 7.2 or 7.3=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x, 7.2 or 7.3 server upgrading yum will fail with the following error:<br />
<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os --enablerepo=sme8updates<br />
<br />
</li><li>After this step completes you will see at the end of the transaction note the error in bold:<br />
<br />
xorg-x11-libs.i386 0:6.8.2-1.EL.33 yum-plugin-fastestmirror.noarch 0:0.2.4-3.c4<br />
Complete!<br />
'''rpmdb: Program version 4.3 doesn't match environment version'''<br />
'''error: db4 error(-30974) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch'''<br />
'''error: cannot open Packages index using db3 - (-30974)'''<br />
'''error: cannot open Packages database in /var/lib/rpm'''<br />
==============================================================<br />
WARNING: You now need to run BOTH of the following commands<br />
to ensure consistent system state: <br />
<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
You should run these commands unless you are certain that<br />
yum made no changes to your system.<br />
==============================================================<br />
<br />
You will need to run at command line the following before issuing step 6.<br />
<br />
rm -f /var/lib/rpm/__db.00*<br />
rpm --rebuilddb<br />
<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=Talk:SME8.0_QA&diff=13543
Talk:SME8.0 QA
2009-09-24T20:48:05Z
<p>Byte: /* comments */</p>
<hr />
<div>=comments=<br />
I feel we need more than a "Pass" as for example under the server roles the PDC test was past but with not much information about what other PDC tests were done for example does PDC pass if you create a domain admins group and try to join a XP client with a user in the domain admins group ?!<br />
<br />
Its an excellent start as I've said but we must be sure we are giving as good QA as we can so therefore we must make sure each test is tested intensively and showing that its been tested intensively.<br />
<br />
~~byte aka Gavin<br />
=comments=<br />
<br />
When doing an upgrade we need to know how an upgrade is taking place i.e CD or YUM and we need to test both upgrade paths.<br />
<br />
Also don't forget to open separate bugs as their maybe issues with the upgrade as noticed a few talking points in the bug tracker with the /root/upgrade.log<br />
<br />
=Proposed template=<br />
<br />
=Testing=<br />
<br />
<br />
==Test guidelines==<br />
<br />
<br />
=Installation x=<br />
<br />
==Installation types x==<br />
<br />
=Upgrading x=<br />
<br />
==Upgrade from older versions x==<br />
to check: /var/log/messages<br />
<br />
*from 7.4<br />
<br />
*from 7.3<br />
<br />
*from 7.2<br />
<br />
*from 7.1<br />
<br />
*older 7.0<br />
<br />
<br />
=Console x=<br />
<br />
==Check Status x==<br />
<br />
==Configure Server x==<br />
<br />
===DHCP server x===<br />
<br />
===Server-gateway x===<br />
<br />
===Server-only x===<br />
<br />
==Test internet x==<br />
<br />
==Reboot x==<br />
<br />
==Raid x==<br />
<br />
==Access Server Manger x==<br />
<br />
==View Support x==<br />
<br />
==Backup to USB x==<br />
<br />
<br />
=Server Manager x=<br />
<br />
==Collaboration x==<br />
<br />
===Users x===<br />
<br />
===Groups x===<br />
<br />
===Quotas x===<br />
<br />
===Pseudonyms x===<br />
<br />
===Information Bays x===<br />
<br />
====User access via file sharing x====<br />
<br />
====Public access via web x====<br />
<br />
====dynamic content====<br />
<br />
==Administration x==<br />
<br />
===Backup and restore x===<br />
<br />
====Backup x====<br />
<br />
=====to desktop x=====<br />
<br />
=====to tape x=====<br />
<br />
=====to workstation x=====<br />
<br />
=====to usb disk x=====<br />
<br />
====Restore x====<br />
<br />
=====from desktop (console) x=====<br />
<br />
=====from tape x=====<br />
<br />
=====from workstation x=====<br />
<br />
=====from usb disk x=====<br />
<br />
===View log files x===<br />
<br />
===Mail lof files x===<br />
<br />
===Reboot and shutdown x===<br />
<br />
==Security x==<br />
<br />
===Remote access x===<br />
<br />
====VPN / PPTP x====<br />
<br />
====Remote management x====<br />
<br />
====SSH x====<br />
<br />
====FTP x====<br />
<br />
===Local Networks x===<br />
<br />
===Port forwarding x===<br />
<br />
===Proxy settings x===<br />
<br />
====Mail x====<br />
<br />
====Web x====<br />
<br />
==Configuration x==<br />
<br />
===Software Installer x===<br />
<br />
====Updates x====<br />
<br />
====Settings x====<br />
<br />
===Date and time x===<br />
<br />
===Workgroup x===<br />
<br />
====Domain controller x====<br />
<br />
====Roaming profiles x====<br />
<br />
===Directory x===<br />
<br />
===Printers x===<br />
<br />
===Hostnames x===<br />
<br />
===Domains x===<br />
<br />
===Email x===<br />
<br />
====Access x====<br />
<br />
====Filtering x====<br />
<br />
====Reception x====<br />
<br />
====Delivery x====<br />
<br />
===Antivirus x===<br />
<br />
===Review x===<br />
<br />
==Miscellaneous x==<br />
<br />
===Support x===<br />
<br />
===Starter Website x===<br />
<br />
=Other x=<br />
<br />
==Languages x==<br />
Displays ok, translations up-to-date<br />
<br />
===Danish x===<br />
<br />
===Dutch x===<br />
<br />
===Estonian x===<br />
<br />
===French x===<br />
<br />
===German x===<br />
<br />
===Greek x===<br />
<br />
===Hungarian x===<br />
<br />
===Indonesian x===<br />
<br />
===Italian x===<br />
<br />
===Norwegian x===<br />
<br />
===Portuguese x===<br />
<br />
===Portuguese Brazil x===<br />
<br />
===Romanian x===<br />
<br />
===Russian x===<br />
<br />
===Slovenian x===<br />
<br />
===Spanish x===<br />
<br />
===Swedish x===</div>
Byte
https://wiki.koozali.org/index.php?title=2009_Project_Restructure&diff=13462
2009 Project Restructure
2009-09-12T18:05:06Z
<p>Byte: /* Community Members involved with this effort */</p>
<hr />
<div>==SME Server Project Leadership Restructure Effort==<br />
<br />
This page shall serve as an overview and agenda for the effort to re-establish the leadership structure for the SME Server project. It will be updated as necessary to reflect the state of the restructuring effort, the current plan of action, and the community members who are involved with this effort. <br />
<br />
===Background===<br />
<br />
The SME Server project is governed by [[SME Server:Constitution]]. This constitution and the leadership structure it sets out are essentially defunct. This defunct governing document and associated leadership structure have hampered the overall leadership of the project.<br />
<br />
In recent months, a movement has begun to fix this defunct leadership structure so that the SME Server project can live a long and prosperous life.<br />
<br />
===Plan of Action===<br />
<br />
* Elect an Interim Board of Directors;<br />
* Evaluate the current Constitution and update it to better serve the SME Server project and community;<br />
* Evaluate the current SME Server, Inc. non-profit corporation to determine if this entity is the best entity for the community moving forward;<br />
* Implement the new leadership structure.<br />
<br />
===Current Status===<br />
<br />
* Setting up an Oregon non-profit corporation called SME Server Foundation, Inc.<br />
* Revising the Constitution.<br />
<br />
===Interim Board of Directors===<br />
* Greg J. Zartman, P.E.<br />
* Peter Walter<br />
* Charlie Brady <br />
<br />
===Community Members involved with this effort===<br />
* Charlie Brady<br />
* Chris Burnat<br />
* Ian Wells<br />
* Filippo Carletti<br />
* Greg J. Zartman, P.E.<br />
* Gavin Weight <br />
* Jonathan Martens<br />
* Michael Doerner<br />
* Paul Floor<br />
* Peter Walter<br />
* Stephen Noble<br />
----<br />
<br />
===Work In Progress===<br />
<br />
====Resolutions====<br />
* Mission statement.<br />
To foster the creation, distribution, and maintainance of a free <br />
integrated, all-in-one server operating system with bundled applications <br />
designed for homes, small businesses, and medium-size businesses,<br />
licensed under the GNU General Public License. The server operating <br />
system will be focused on simplicity, stability and security, designed <br />
to be operated by people with no technical background, while providing <br />
a platform for technical users to extend.<br />
<br />
* Interim Board<br />
An interim Board to be formed for a period of three months. The primary purpose of this Board will be the registration a non-profit corporation called SME Server Foundation, Inc. in the state of Oregon. The initial board of directors approves the subsequent Board at expiration of its three months term. This initial Board of Directors may also do some incidental business admin tasks to complete organization of the non-profit corporation and will consist of:<br />
- Greg J. Zartman,P.E.<br />
- Peter Walter<br />
- Charlie Brady<br />
<br />
====Action Points====<br />
<br />
* Contact Greg Swallow and seek transfer of "smeserver.org" to new entity [Michael Doerner]<br />
<br />
* Attempt to register and park "Domain of interest" currently owned by [xxx] [chris burnat]<br />
<br />
* Contact JM Consulting Group of Michigan and seek transfer of domain "smeserver.net" [Michael Doerner]<br />
<br />
* Setting up an Oregon non-profit corporation called SME Server Foundation, Inc. [Greg J. Zartman, P.E.] <br />
<br />
* Develop/revise Constitution [Peter Walter]<br />
<br />
----<br />
<br />
===Draft Constitution===<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
In progress.<br />
----</div>
Byte
https://wiki.koozali.org/index.php?title=Talk:SME8.0_QA&diff=13372
Talk:SME8.0 QA
2009-08-29T14:53:45Z
<p>Byte: Created page with 'I feel we need more than a "Pass" as for example under the server roles the PDC test was past but with not much information about what other PDC tests were done for example does …'</p>
<hr />
<div>I feel we need more than a "Pass" as for example under the server roles the PDC test was past but with not much information about what other PDC tests were done for example does PDC pass if you create a domain admins group and try to join a XP client with a user in the domain admins group ?!<br />
<br />
Its an excellent start as I've said but we must be sure we are giving as good QA as we can so therefore we must make sure each test is tested intensively and showing that its been tested intensively.<br />
<br />
~~byte aka Gavin</div>
Byte
https://wiki.koozali.org/index.php?title=SME8.0_QA&diff=13362
SME8.0 QA
2009-08-28T21:03:22Z
<p>Byte: /* ClamAV */</p>
<hr />
<div>===Version 8.0 testing===<br />
This document lists tests that we need to do to get version 8.0 closer to a final release. It's an attempt to invite as many testers as possible and to coordinate our testing work.<br />
<br />
The document should be used as Work In Progress so please feel free to add additional test scenarios, comments and add "Pass" if you have finished a specific test so that other testers can see what still needs to be done.<br />
<br />
In general<br />
- check the related logfile(s) for each test<br />
<br />
- don't hesitate to raise a bug if there is an issue or something suspicious but check the Bugtracker before whether this might already be reported<br />
<br />
- A list of currently reported bugs for SME 8.0 is here: http://bugs.contribs.org/show_bug.cgi?id=3640<br />
<br />
===Test guidelines===<br />
Here are some guidelines from other users:<br />
<br />
Create a test environment, either virtually or with spare hardware. Install the latest release, add some test users/ibays/domains/websites, send some internal e-mails, copy some files to/from ibays, perform a backup and restore. Perform as many functions that you can based on your knowledge and test environment abilities. Play. :) <br />
<br />
When ready go into Bugzilla and review the open bugs. Find any that you can duplicate and report your results, even if just to confirm someone elses report is valid. If you find during your testing something does not work for you, and a bug does not exist, open a new bug.<br />
--------------<br />
The scenario's should be as complex as needed, but also as simple as possible, testing one unique feature where possible.<br />
<br />
For instance creating an ibay could mean something like this, perhaps even incomplete as I am doing this from the top of my head:<br />
<br />
- log in in server-manager<br />
<br />- create ibay<br />
<br />- test for directory created (-f /home/e-smith/ibays/ibayname)<br />
<br />- check for account (ibayname) created<br />
<br />- check for group (ibayname) created<br />
<br />- anaylze log for errors/exceptions<br />
<br />
but also (and that is the most work mostly) test exceptions (names too long, starting with a number, containing a _, as well as all other exceptions):<br />
<br />
- log in in server-manager<br />
<br />- create ibay with invalid name<br />
<br />- check the error in the server-manager screen<br />
<br />- check no account (ibayname) is created<br />
<br />- check no group (ibayname) os created<br />
<br />- check that the error is present in the log file<br />
--------------<br />
<br />
===Installation types===<br />
Different installation scenarios re. software RAID, LVM and NOSPARE usage, etc.<br />
<br />
to check: /var/log/messages; server-console, item 5; cat /proc/mdstat (which is the same as server-console, item 5;)<br />
<br />
*RAID1 (with lvm)<br />
Comments:<br />
*RAID1 "nolvm"<br />
Comments:<br />
*RAID5 (with lvm)<br />
Comments:<br />
*RAID5 "nolvm"<br />
Comments:<br />
*RAIDx (with lvm)<br />
Comments:<br />
*RAIDx "nolvm"<br />
Comments:<br />
*RAID5 "with nospare"<br />
Comments:<br />
<br />
===Upgrade from older versions===<br />
to check: /var/log/messages<br />
*from 7.4<br />
Comments:<br />
*from 7.3<br />
Comments:<br />
*from 7.2<br />
Comments:<br />
*from 7.1<br />
Comments:<br />
*older 7.0<br />
Comments:<br />
<br />
===Configurations===<br />
*server-gateway<br />
Comments:<br />
*server-only<br />
Comments:<br />
<br />
===Server roles===<br />
*PDC - setup Primary Domain Controller<br />
Steps: <br />
<br />- join PC to domain and test domain user logon on that PC<br />
<br />- domain user password change via Ctrl-Alt-Del<br />
<br />
Comments:<br />
*Workgroup server<br />
Comments:<br />
<br />
===User/groups setup===<br />
- create new user account, <br />
<br />-reset user password, <br />
<br />-lock/unlock account, <br />
<br />-add/remove user to different groups<br />
<br />-delete user account<br />
<br />-re create deleted user account<br />
<br />-reset user password user account<br />
to check: /var/log/messages, /var/log/httpd/admin_error_log, /var/log/secure<br />
<br />
===Ibay setup===<br />
- create new ibay, <br />
<br />- ibay access protected by password, <br />
<br />-copy/delete files in ibays<br />
<br />
to check: /var/log/messages, /var/log/httpd/admin_error_log<br />
<br />
===Email server===<br />
*pop3(s)<br />
Comments:<br />
*imap(s)<br />
Comments:<br />
<br />
to check: /var/log/pop3(s)/current; /var/log/imap(s)/current<br />
<br />
===ClamAV===<br />
*Clam/email integration<br />
to check: /var/log/qmail/current; /var/log/spamd/current; /var/log/qpsmtpd/current; /var/log/clamd/current; /var/log/clamd/smeserver-clamscan.log<br />
<br />
*regular Clam scans<br />
enable regular scanning in server-manager and check results (email to admin)<br />
<br />
Comments:<br />
<br />
===DHCP server===<br />
*test IP allocation for predefined MAC addresses (= 'static' IP allocation)<br />
<br />
to check: /var/log/messages<br />
<br />
===Remote access/VPN===<br />
Set a number of PPTP clients in server manager and test remote access (repeatedly)<br />
<br />
===ldap===<br />
test access from various email clients (Outlook, OE, Thunderbird, more)<br />
<br />
===Backup===<br />
<br />
===Contribs===<br />
add individual contribs here</div>
Byte
https://wiki.koozali.org/index.php?title=SME8.0_QA&diff=13361
SME8.0 QA
2009-08-28T20:59:38Z
<p>Byte: /* ClamAV */</p>
<hr />
<div>===Version 8.0 testing===<br />
This document lists tests that we need to do to get version 8.0 closer to a final release. It's an attempt to invite as many testers as possible and to coordinate our testing work.<br />
<br />
The document should be used as Work In Progress so please feel free to add additional test scenarios, comments and add "Pass" if you have finished a specific test so that other testers can see what still needs to be done.<br />
<br />
In general<br />
- check the related logfile(s) for each test<br />
<br />
- don't hesitate to raise a bug if there is an issue or something suspicious but check the Bugtracker before whether this might already be reported<br />
<br />
- A list of currently reported bugs for SME 8.0 is here: http://bugs.contribs.org/show_bug.cgi?id=3640<br />
<br />
===Test guidelines===<br />
Here are some guidelines from other users:<br />
<br />
Create a test environment, either virtually or with spare hardware. Install the latest release, add some test users/ibays/domains/websites, send some internal e-mails, copy some files to/from ibays, perform a backup and restore. Perform as many functions that you can based on your knowledge and test environment abilities. Play. :) <br />
<br />
When ready go into Bugzilla and review the open bugs. Find any that you can duplicate and report your results, even if just to confirm someone elses report is valid. If you find during your testing something does not work for you, and a bug does not exist, open a new bug.<br />
--------------<br />
The scenario's should be as complex as needed, but also as simple as possible, testing one unique feature where possible.<br />
<br />
For instance creating an ibay could mean something like this, perhaps even incomplete as I am doing this from the top of my head:<br />
<br />
- log in in server-manager<br />
<br />- create ibay<br />
<br />- test for directory created (-f /home/e-smith/ibays/ibayname)<br />
<br />- check for account (ibayname) created<br />
<br />- check for group (ibayname) created<br />
<br />- anaylze log for errors/exceptions<br />
<br />
but also (and that is the most work mostly) test exceptions (names too long, starting with a number, containing a _, as well as all other exceptions):<br />
<br />
- log in in server-manager<br />
<br />- create ibay with invalid name<br />
<br />- check the error in the server-manager screen<br />
<br />- check no account (ibayname) is created<br />
<br />- check no group (ibayname) os created<br />
<br />- check that the error is present in the log file<br />
--------------<br />
<br />
===Installation types===<br />
Different installation scenarios re. software RAID, LVM and NOSPARE usage, etc.<br />
<br />
to check: /var/log/messages; server-console, item 5; cat /proc/mdstat (which is the same as server-console, item 5;)<br />
<br />
*RAID1 (with lvm)<br />
Comments:<br />
*RAID1 "nolvm"<br />
Comments:<br />
*RAID5 (with lvm)<br />
Comments:<br />
*RAID5 "nolvm"<br />
Comments:<br />
*RAIDx (with lvm)<br />
Comments:<br />
*RAIDx "nolvm"<br />
Comments:<br />
*RAID5 "with nospare"<br />
Comments:<br />
<br />
===Upgrade from older versions===<br />
to check: /var/log/messages<br />
*from 7.4<br />
Comments:<br />
*from 7.3<br />
Comments:<br />
*from 7.2<br />
Comments:<br />
*from 7.1<br />
Comments:<br />
*older 7.0<br />
Comments:<br />
<br />
===Configurations===<br />
*server-gateway<br />
Comments:<br />
*server-only<br />
Comments:<br />
<br />
===Server roles===<br />
*PDC - setup Primary Domain Controller<br />
Steps: <br />
<br />- join PC to domain and test domain user logon on that PC<br />
<br />- domain user password change via Ctrl-Alt-Del<br />
<br />
Comments:<br />
*Workgroup server<br />
Comments:<br />
<br />
===User/groups setup===<br />
- create new user account, <br />
<br />-reset user password, <br />
<br />-lock/unlock account, <br />
<br />-add/remove user to different groups<br />
<br />-delete user account<br />
<br />-re create deleted user account<br />
<br />-reset user password user account<br />
to check: /var/log/messages, /var/log/httpd/admin_error_log, /var/log/secure<br />
<br />
===Ibay setup===<br />
- create new ibay, <br />
<br />- ibay access protected by password, <br />
<br />-copy/delete files in ibays<br />
<br />
to check: /var/log/messages, /var/log/httpd/admin_error_log<br />
<br />
===Email server===<br />
*pop3(s)<br />
Comments:<br />
*imap(s)<br />
Comments:<br />
<br />
to check: /var/log/pop3(s)/current; /var/log/imap(s)/current<br />
<br />
===ClamAV===<br />
*Clam/email integration<br />
to check: /var/log/qmail/current; /var/log/spamd/current; /var/log/qpsmtpd/current<br />
<br />
*regular Clam scans<br />
enable regular scanning in server-manager and check results (email to admin)<br />
<br />
Comments:<br />
<br />
===DHCP server===<br />
*test IP allocation for predefined MAC addresses (= 'static' IP allocation)<br />
<br />
to check: /var/log/messages<br />
<br />
===Remote access/VPN===<br />
Set a number of PPTP clients in server manager and test remote access (repeatedly)<br />
<br />
===ldap===<br />
test access from various email clients (Outlook, OE, Thunderbird, more)<br />
<br />
===Backup===<br />
<br />
===Contribs===<br />
add individual contribs here</div>
Byte
https://wiki.koozali.org/index.php?title=SME8.0_QA&diff=13360
SME8.0 QA
2009-08-28T20:58:48Z
<p>Byte: /* Ibay setup */</p>
<hr />
<div>===Version 8.0 testing===<br />
This document lists tests that we need to do to get version 8.0 closer to a final release. It's an attempt to invite as many testers as possible and to coordinate our testing work.<br />
<br />
The document should be used as Work In Progress so please feel free to add additional test scenarios, comments and add "Pass" if you have finished a specific test so that other testers can see what still needs to be done.<br />
<br />
In general<br />
- check the related logfile(s) for each test<br />
<br />
- don't hesitate to raise a bug if there is an issue or something suspicious but check the Bugtracker before whether this might already be reported<br />
<br />
- A list of currently reported bugs for SME 8.0 is here: http://bugs.contribs.org/show_bug.cgi?id=3640<br />
<br />
===Test guidelines===<br />
Here are some guidelines from other users:<br />
<br />
Create a test environment, either virtually or with spare hardware. Install the latest release, add some test users/ibays/domains/websites, send some internal e-mails, copy some files to/from ibays, perform a backup and restore. Perform as many functions that you can based on your knowledge and test environment abilities. Play. :) <br />
<br />
When ready go into Bugzilla and review the open bugs. Find any that you can duplicate and report your results, even if just to confirm someone elses report is valid. If you find during your testing something does not work for you, and a bug does not exist, open a new bug.<br />
--------------<br />
The scenario's should be as complex as needed, but also as simple as possible, testing one unique feature where possible.<br />
<br />
For instance creating an ibay could mean something like this, perhaps even incomplete as I am doing this from the top of my head:<br />
<br />
- log in in server-manager<br />
<br />- create ibay<br />
<br />- test for directory created (-f /home/e-smith/ibays/ibayname)<br />
<br />- check for account (ibayname) created<br />
<br />- check for group (ibayname) created<br />
<br />- anaylze log for errors/exceptions<br />
<br />
but also (and that is the most work mostly) test exceptions (names too long, starting with a number, containing a _, as well as all other exceptions):<br />
<br />
- log in in server-manager<br />
<br />- create ibay with invalid name<br />
<br />- check the error in the server-manager screen<br />
<br />- check no account (ibayname) is created<br />
<br />- check no group (ibayname) os created<br />
<br />- check that the error is present in the log file<br />
--------------<br />
<br />
===Installation types===<br />
Different installation scenarios re. software RAID, LVM and NOSPARE usage, etc.<br />
<br />
to check: /var/log/messages; server-console, item 5; cat /proc/mdstat (which is the same as server-console, item 5;)<br />
<br />
*RAID1 (with lvm)<br />
Comments:<br />
*RAID1 "nolvm"<br />
Comments:<br />
*RAID5 (with lvm)<br />
Comments:<br />
*RAID5 "nolvm"<br />
Comments:<br />
*RAIDx (with lvm)<br />
Comments:<br />
*RAIDx "nolvm"<br />
Comments:<br />
*RAID5 "with nospare"<br />
Comments:<br />
<br />
===Upgrade from older versions===<br />
to check: /var/log/messages<br />
*from 7.4<br />
Comments:<br />
*from 7.3<br />
Comments:<br />
*from 7.2<br />
Comments:<br />
*from 7.1<br />
Comments:<br />
*older 7.0<br />
Comments:<br />
<br />
===Configurations===<br />
*server-gateway<br />
Comments:<br />
*server-only<br />
Comments:<br />
<br />
===Server roles===<br />
*PDC - setup Primary Domain Controller<br />
Steps: <br />
<br />- join PC to domain and test domain user logon on that PC<br />
<br />- domain user password change via Ctrl-Alt-Del<br />
<br />
Comments:<br />
*Workgroup server<br />
Comments:<br />
<br />
===User/groups setup===<br />
- create new user account, <br />
<br />-reset user password, <br />
<br />-lock/unlock account, <br />
<br />-add/remove user to different groups<br />
<br />-delete user account<br />
<br />-re create deleted user account<br />
<br />-reset user password user account<br />
to check: /var/log/messages, /var/log/httpd/admin_error_log, /var/log/secure<br />
<br />
===Ibay setup===<br />
- create new ibay, <br />
<br />- ibay access protected by password, <br />
<br />-copy/delete files in ibays<br />
<br />
to check: /var/log/messages, /var/log/httpd/admin_error_log<br />
<br />
===Email server===<br />
*pop3(s)<br />
Comments:<br />
*imap(s)<br />
Comments:<br />
<br />
to check: /var/log/pop3(s)/current; /var/log/imap(s)/current<br />
<br />
===ClamAV===<br />
*Clam/email integration<br />
to check: /var/log/qmail/current; /var/log/spamd/current<br />
<br />
*regular Clam scans<br />
enable regular scanning in server-manager and check results (email to admin)<br />
<br />
Comments:<br />
<br />
===DHCP server===<br />
*test IP allocation for predefined MAC addresses (= 'static' IP allocation)<br />
<br />
to check: /var/log/messages<br />
<br />
===Remote access/VPN===<br />
Set a number of PPTP clients in server manager and test remote access (repeatedly)<br />
<br />
===ldap===<br />
test access from various email clients (Outlook, OE, Thunderbird, more)<br />
<br />
===Backup===<br />
<br />
===Contribs===<br />
add individual contribs here</div>
Byte
https://wiki.koozali.org/index.php?title=SME8.0_QA&diff=13359
SME8.0 QA
2009-08-28T20:58:21Z
<p>Byte: /* User/groups setup */</p>
<hr />
<div>===Version 8.0 testing===<br />
This document lists tests that we need to do to get version 8.0 closer to a final release. It's an attempt to invite as many testers as possible and to coordinate our testing work.<br />
<br />
The document should be used as Work In Progress so please feel free to add additional test scenarios, comments and add "Pass" if you have finished a specific test so that other testers can see what still needs to be done.<br />
<br />
In general<br />
- check the related logfile(s) for each test<br />
<br />
- don't hesitate to raise a bug if there is an issue or something suspicious but check the Bugtracker before whether this might already be reported<br />
<br />
- A list of currently reported bugs for SME 8.0 is here: http://bugs.contribs.org/show_bug.cgi?id=3640<br />
<br />
===Test guidelines===<br />
Here are some guidelines from other users:<br />
<br />
Create a test environment, either virtually or with spare hardware. Install the latest release, add some test users/ibays/domains/websites, send some internal e-mails, copy some files to/from ibays, perform a backup and restore. Perform as many functions that you can based on your knowledge and test environment abilities. Play. :) <br />
<br />
When ready go into Bugzilla and review the open bugs. Find any that you can duplicate and report your results, even if just to confirm someone elses report is valid. If you find during your testing something does not work for you, and a bug does not exist, open a new bug.<br />
--------------<br />
The scenario's should be as complex as needed, but also as simple as possible, testing one unique feature where possible.<br />
<br />
For instance creating an ibay could mean something like this, perhaps even incomplete as I am doing this from the top of my head:<br />
<br />
- log in in server-manager<br />
<br />- create ibay<br />
<br />- test for directory created (-f /home/e-smith/ibays/ibayname)<br />
<br />- check for account (ibayname) created<br />
<br />- check for group (ibayname) created<br />
<br />- anaylze log for errors/exceptions<br />
<br />
but also (and that is the most work mostly) test exceptions (names too long, starting with a number, containing a _, as well as all other exceptions):<br />
<br />
- log in in server-manager<br />
<br />- create ibay with invalid name<br />
<br />- check the error in the server-manager screen<br />
<br />- check no account (ibayname) is created<br />
<br />- check no group (ibayname) os created<br />
<br />- check that the error is present in the log file<br />
--------------<br />
<br />
===Installation types===<br />
Different installation scenarios re. software RAID, LVM and NOSPARE usage, etc.<br />
<br />
to check: /var/log/messages; server-console, item 5; cat /proc/mdstat (which is the same as server-console, item 5;)<br />
<br />
*RAID1 (with lvm)<br />
Comments:<br />
*RAID1 "nolvm"<br />
Comments:<br />
*RAID5 (with lvm)<br />
Comments:<br />
*RAID5 "nolvm"<br />
Comments:<br />
*RAIDx (with lvm)<br />
Comments:<br />
*RAIDx "nolvm"<br />
Comments:<br />
*RAID5 "with nospare"<br />
Comments:<br />
<br />
===Upgrade from older versions===<br />
to check: /var/log/messages<br />
*from 7.4<br />
Comments:<br />
*from 7.3<br />
Comments:<br />
*from 7.2<br />
Comments:<br />
*from 7.1<br />
Comments:<br />
*older 7.0<br />
Comments:<br />
<br />
===Configurations===<br />
*server-gateway<br />
Comments:<br />
*server-only<br />
Comments:<br />
<br />
===Server roles===<br />
*PDC - setup Primary Domain Controller<br />
Steps: <br />
<br />- join PC to domain and test domain user logon on that PC<br />
<br />- domain user password change via Ctrl-Alt-Del<br />
<br />
Comments:<br />
*Workgroup server<br />
Comments:<br />
<br />
===User/groups setup===<br />
- create new user account, <br />
<br />-reset user password, <br />
<br />-lock/unlock account, <br />
<br />-add/remove user to different groups<br />
<br />-delete user account<br />
<br />-re create deleted user account<br />
<br />-reset user password user account<br />
to check: /var/log/messages, /var/log/httpd/admin_error_log, /var/log/secure<br />
<br />
===Ibay setup===<br />
- create new ibay, <br />
<br />- ibay access protected by password, <br />
<br />-copy/delete files in ibays<br />
<br />
to check: /var/log/messages<br />
<br />
===Email server===<br />
*pop3(s)<br />
Comments:<br />
*imap(s)<br />
Comments:<br />
<br />
to check: /var/log/pop3(s)/current; /var/log/imap(s)/current<br />
<br />
===ClamAV===<br />
*Clam/email integration<br />
to check: /var/log/qmail/current; /var/log/spamd/current<br />
<br />
*regular Clam scans<br />
enable regular scanning in server-manager and check results (email to admin)<br />
<br />
Comments:<br />
<br />
===DHCP server===<br />
*test IP allocation for predefined MAC addresses (= 'static' IP allocation)<br />
<br />
to check: /var/log/messages<br />
<br />
===Remote access/VPN===<br />
Set a number of PPTP clients in server manager and test remote access (repeatedly)<br />
<br />
===ldap===<br />
test access from various email clients (Outlook, OE, Thunderbird, more)<br />
<br />
===Backup===<br />
<br />
===Contribs===<br />
add individual contribs here</div>
Byte
https://wiki.koozali.org/index.php?title=SME8.0_QA&diff=13358
SME8.0 QA
2009-08-28T20:54:33Z
<p>Byte: /* Upgrade from older versions */</p>
<hr />
<div>===Version 8.0 testing===<br />
This document lists tests that we need to do to get version 8.0 closer to a final release. It's an attempt to invite as many testers as possible and to coordinate our testing work.<br />
<br />
The document should be used as Work In Progress so please feel free to add additional test scenarios, comments and add "Pass" if you have finished a specific test so that other testers can see what still needs to be done.<br />
<br />
In general<br />
- check the related logfile(s) for each test<br />
<br />
- don't hesitate to raise a bug if there is an issue or something suspicious but check the Bugtracker before whether this might already be reported<br />
<br />
- A list of currently reported bugs for SME 8.0 is here: http://bugs.contribs.org/show_bug.cgi?id=3640<br />
<br />
===Test guidelines===<br />
Here are some guidelines from other users:<br />
<br />
Create a test environment, either virtually or with spare hardware. Install the latest release, add some test users/ibays/domains/websites, send some internal e-mails, copy some files to/from ibays, perform a backup and restore. Perform as many functions that you can based on your knowledge and test environment abilities. Play. :) <br />
<br />
When ready go into Bugzilla and review the open bugs. Find any that you can duplicate and report your results, even if just to confirm someone elses report is valid. If you find during your testing something does not work for you, and a bug does not exist, open a new bug.<br />
--------------<br />
The scenario's should be as complex as needed, but also as simple as possible, testing one unique feature where possible.<br />
<br />
For instance creating an ibay could mean something like this, perhaps even incomplete as I am doing this from the top of my head:<br />
<br />
- log in in server-manager<br />
<br />- create ibay<br />
<br />- test for directory created (-f /home/e-smith/ibays/ibayname)<br />
<br />- check for account (ibayname) created<br />
<br />- check for group (ibayname) created<br />
<br />- anaylze log for errors/exceptions<br />
<br />
but also (and that is the most work mostly) test exceptions (names too long, starting with a number, containing a _, as well as all other exceptions):<br />
<br />
- log in in server-manager<br />
<br />- create ibay with invalid name<br />
<br />- check the error in the server-manager screen<br />
<br />- check no account (ibayname) is created<br />
<br />- check no group (ibayname) os created<br />
<br />- check that the error is present in the log file<br />
--------------<br />
<br />
===Installation types===<br />
Different installation scenarios re. software RAID, LVM and NOSPARE usage, etc.<br />
<br />
to check: /var/log/messages; server-console, item 5; cat /proc/mdstat (which is the same as server-console, item 5;)<br />
<br />
*RAID1 (with lvm)<br />
Comments:<br />
*RAID1 "nolvm"<br />
Comments:<br />
*RAID5 (with lvm)<br />
Comments:<br />
*RAID5 "nolvm"<br />
Comments:<br />
*RAIDx (with lvm)<br />
Comments:<br />
*RAIDx "nolvm"<br />
Comments:<br />
*RAID5 "with nospare"<br />
Comments:<br />
<br />
===Upgrade from older versions===<br />
to check: /var/log/messages<br />
*from 7.4<br />
Comments:<br />
*from 7.3<br />
Comments:<br />
*from 7.2<br />
Comments:<br />
*from 7.1<br />
Comments:<br />
*older 7.0<br />
Comments:<br />
<br />
===Configurations===<br />
*server-gateway<br />
Comments:<br />
*server-only<br />
Comments:<br />
<br />
===Server roles===<br />
*PDC - setup Primary Domain Controller<br />
Steps: <br />
<br />- join PC to domain and test domain user logon on that PC<br />
<br />- domain user password change via Ctrl-Alt-Del<br />
<br />
Comments:<br />
*Workgroup server<br />
Comments:<br />
<br />
===User/groups setup===<br />
- create new user account, <br />
<br />-reset user password, <br />
<br />-lock/unlock account, <br />
<br />-add/remove user to different groups<br />
<br />-delete user account<br />
<br />
to check: /var/log/messages<br />
<br />
===Ibay setup===<br />
- create new ibay, <br />
<br />- ibay access protected by password, <br />
<br />-copy/delete files in ibays<br />
<br />
to check: /var/log/messages<br />
<br />
===Email server===<br />
*pop3(s)<br />
Comments:<br />
*imap(s)<br />
Comments:<br />
<br />
to check: /var/log/pop3(s)/current; /var/log/imap(s)/current<br />
<br />
===ClamAV===<br />
*Clam/email integration<br />
to check: /var/log/qmail/current; /var/log/spamd/current<br />
<br />
*regular Clam scans<br />
enable regular scanning in server-manager and check results (email to admin)<br />
<br />
Comments:<br />
<br />
===DHCP server===<br />
*test IP allocation for predefined MAC addresses (= 'static' IP allocation)<br />
<br />
to check: /var/log/messages<br />
<br />
===Remote access/VPN===<br />
Set a number of PPTP clients in server manager and test remote access (repeatedly)<br />
<br />
===ldap===<br />
test access from various email clients (Outlook, OE, Thunderbird, more)<br />
<br />
===Backup===<br />
<br />
===Contribs===<br />
add individual contribs here</div>
Byte
https://wiki.koozali.org/index.php?title=SME8.0_QA&diff=13357
SME8.0 QA
2009-08-28T20:53:37Z
<p>Byte: /* Installation types */</p>
<hr />
<div>===Version 8.0 testing===<br />
This document lists tests that we need to do to get version 8.0 closer to a final release. It's an attempt to invite as many testers as possible and to coordinate our testing work.<br />
<br />
The document should be used as Work In Progress so please feel free to add additional test scenarios, comments and add "Pass" if you have finished a specific test so that other testers can see what still needs to be done.<br />
<br />
In general<br />
- check the related logfile(s) for each test<br />
<br />
- don't hesitate to raise a bug if there is an issue or something suspicious but check the Bugtracker before whether this might already be reported<br />
<br />
- A list of currently reported bugs for SME 8.0 is here: http://bugs.contribs.org/show_bug.cgi?id=3640<br />
<br />
===Test guidelines===<br />
Here are some guidelines from other users:<br />
<br />
Create a test environment, either virtually or with spare hardware. Install the latest release, add some test users/ibays/domains/websites, send some internal e-mails, copy some files to/from ibays, perform a backup and restore. Perform as many functions that you can based on your knowledge and test environment abilities. Play. :) <br />
<br />
When ready go into Bugzilla and review the open bugs. Find any that you can duplicate and report your results, even if just to confirm someone elses report is valid. If you find during your testing something does not work for you, and a bug does not exist, open a new bug.<br />
--------------<br />
The scenario's should be as complex as needed, but also as simple as possible, testing one unique feature where possible.<br />
<br />
For instance creating an ibay could mean something like this, perhaps even incomplete as I am doing this from the top of my head:<br />
<br />
- log in in server-manager<br />
<br />- create ibay<br />
<br />- test for directory created (-f /home/e-smith/ibays/ibayname)<br />
<br />- check for account (ibayname) created<br />
<br />- check for group (ibayname) created<br />
<br />- anaylze log for errors/exceptions<br />
<br />
but also (and that is the most work mostly) test exceptions (names too long, starting with a number, containing a _, as well as all other exceptions):<br />
<br />
- log in in server-manager<br />
<br />- create ibay with invalid name<br />
<br />- check the error in the server-manager screen<br />
<br />- check no account (ibayname) is created<br />
<br />- check no group (ibayname) os created<br />
<br />- check that the error is present in the log file<br />
--------------<br />
<br />
===Installation types===<br />
Different installation scenarios re. software RAID, LVM and NOSPARE usage, etc.<br />
<br />
to check: /var/log/messages; server-console, item 5; cat /proc/mdstat (which is the same as server-console, item 5;)<br />
<br />
*RAID1 (with lvm)<br />
Comments:<br />
*RAID1 "nolvm"<br />
Comments:<br />
*RAID5 (with lvm)<br />
Comments:<br />
*RAID5 "nolvm"<br />
Comments:<br />
*RAIDx (with lvm)<br />
Comments:<br />
*RAIDx "nolvm"<br />
Comments:<br />
*RAID5 "with nospare"<br />
Comments:<br />
<br />
===Upgrade from older versions===<br />
to check: /var/log/messages<br />
*from 7.4<br />
Comments:<br />
*from 7.3<br />
Comments:<br />
*older 7.x<br />
Comments:<br />
<br />
===Configurations===<br />
*server-gateway<br />
Comments:<br />
*server-only<br />
Comments:<br />
<br />
===Server roles===<br />
*PDC - setup Primary Domain Controller<br />
Steps: <br />
<br />- join PC to domain and test domain user logon on that PC<br />
<br />- domain user password change via Ctrl-Alt-Del<br />
<br />
Comments:<br />
*Workgroup server<br />
Comments:<br />
<br />
===User/groups setup===<br />
- create new user account, <br />
<br />-reset user password, <br />
<br />-lock/unlock account, <br />
<br />-add/remove user to different groups<br />
<br />-delete user account<br />
<br />
to check: /var/log/messages<br />
<br />
===Ibay setup===<br />
- create new ibay, <br />
<br />- ibay access protected by password, <br />
<br />-copy/delete files in ibays<br />
<br />
to check: /var/log/messages<br />
<br />
===Email server===<br />
*pop3(s)<br />
Comments:<br />
*imap(s)<br />
Comments:<br />
<br />
to check: /var/log/pop3(s)/current; /var/log/imap(s)/current<br />
<br />
===ClamAV===<br />
*Clam/email integration<br />
to check: /var/log/qmail/current; /var/log/spamd/current<br />
<br />
*regular Clam scans<br />
enable regular scanning in server-manager and check results (email to admin)<br />
<br />
Comments:<br />
<br />
===DHCP server===<br />
*test IP allocation for predefined MAC addresses (= 'static' IP allocation)<br />
<br />
to check: /var/log/messages<br />
<br />
===Remote access/VPN===<br />
Set a number of PPTP clients in server manager and test remote access (repeatedly)<br />
<br />
===ldap===<br />
test access from various email clients (Outlook, OE, Thunderbird, more)<br />
<br />
===Backup===<br />
<br />
===Contribs===<br />
add individual contribs here</div>
Byte
https://wiki.koozali.org/index.php?title=Bounties&diff=13271
Bounties
2009-08-03T14:43:45Z
<p>Byte: /* SME Server Bounties */</p>
<hr />
<div>=== SME Server Bounties ===<br />
<br />
{{Note box|This page is work in progress as we try to structure an SME Server Bounties program}} <br />
<br />
The hunt is on!<br />
<br />
If simply contributing to an Open Source project is not enough, you now have an added incentive. The SME Server Project has organized an ongoing Bounty Hunt. Listed below are various tasks we would like to see completed or features which have been requested. If you have suggestions for possible bounties, look at the current list of [http://bugs.contribs.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=SME+Server+Future&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= enhancement requests] and [http://bugs.contribs.org/enter_bug.cgi?product=SME%20Server%20Future Submit yours] if it is not already listed.<br />
<br />
<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
|+ align="top" style="color:#000000;font-weight:bold;font-size:18px;" |''Open Bounties ''<br />
! Component<br />
! Task<br />
! Bug No.<br />
! Bounty Prize<br />
! Sponser(s)<br />
|-<br />
|e-smith-base+ldap<br />
|Integrate LDAP auth in the core distribution<br />
|[[bugzilla:4590|Bug 4590]]<br />
|xxx<br />
|Name or Names go here<br />
|}<br />
<br />
<br />
<br />
'''Rules'''<br />
<br />
To successfully claim your prize you need to follow a few rules:<br />
<br />
1. All code submitted for a bounty must be without any known intellectual property limitations. Furthermore, it must be submitted under the same license as the application to which it will be applied (for example, GPL for SME Server).<br />
<br />
2. The code must be accepted and committed into the development branch by the module's maintainers before any prize will be awarded.<br />
<br />
3. Patches must conform to SME Server coding and template/db standards. The code must work and work elegantly (i.e., no hack jobs).<br />
<br />
4. In the case of multiple submissions for a single bounty, the judging panel will select and award the highest quality one.<br />
<br />
5. Group submissions must designate a lead person who will submit the claim on behalf of the group.<br />
<br />
6. All bounty awards or rejections are at the sole discretion of the judging panel. We may refuse to award a bounty to anyone for any reason at any time (although there will certainly be a valid reason, since it is in everyone's interest for the bounty process to work smoothly).<br />
<br />
<br />
Once you have submitted your code and it has been accepted into CVS, just let the developers who handled the patch know that you're claiming the bounty. Prizes will be paid using PayPal.</div>
Byte
https://wiki.koozali.org/index.php?title=Bounties&diff=13270
Bounties
2009-08-03T14:32:32Z
<p>Byte: Bounties</p>
<hr />
<div>=== SME Server Bounties ===<br />
<br />
{{Note box|This page is work in progress as we try to structure an SME Server Bounties program}} <br />
<br />
The hunt is on!<br />
<br />
If simply contributing to an Open Source project is not enough, you now have an added incentive. The SNE Server Project has organized an ongoing Bounty Hunt. Listed below are various tasks we would like to see completed or features which have been requested. If you have suggestions for possible bounties, look at the current list of [http://bugs.contribs.org/buglist.cgi?query_format=advanced&short_desc_type=allwordssubstr&short_desc=&product=SME+Server+Future&long_desc_type=substring&long_desc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&keywords_type=allwords&keywords=&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&cmdtype=doit&order=Reuse+same+sort+as+last+time&field0-0-0=noop&type0-0-0=noop&value0-0-0= enhancement requests] and [http://bugs.contribs.org/enter_bug.cgi?product=SME%20Server%20Future Submit yours] if it is not already listed.<br />
<br />
<br />
{| border="1" cellpadding="10" cellspacing="0"<br />
|+ align="top" style="color:#000000;font-weight:bold;font-size:18px;" |''Open Bounties ''<br />
! Component<br />
! Task<br />
! Bug No.<br />
! Bounty Prize<br />
! Sponser(s)<br />
|-<br />
|e-smith-base+ldap<br />
|Integrate LDAP auth in the core distribution<br />
|[[bugzilla:4590|Bug 4590]]<br />
|xxx<br />
|Name or Names go here<br />
|}<br />
<br />
<br />
<br />
'''Rules'''<br />
<br />
To successfully claim your prize you need to follow a few rules:<br />
<br />
1. All code submitted for a bounty must be without any known intellectual property limitations. Furthermore, it must be submitted under the same license as the application to which it will be applied (for example, GPL for SME Server).<br />
<br />
2. The code must be accepted and committed into the development branch by the module's maintainers before any prize will be awarded.<br />
<br />
3. Patches must conform to SME Server coding and template/db standards. The code must work and work elegantly (i.e., no hack jobs).<br />
<br />
4. In the case of multiple submissions for a single bounty, the judging panel will select and award the highest quality one.<br />
<br />
5. Group submissions must designate a lead person who will submit the claim on behalf of the group.<br />
<br />
6. All bounty awards or rejections are at the sole discretion of the judging panel. We may refuse to award a bounty to anyone for any reason at any time (although there will certainly be a valid reason, since it is in everyone's interest for the bounty process to work smoothly).<br />
<br />
<br />
Once you have submitted your code and it has been accepted into CVS, just let the developers who handled the patch know that you're claiming the bounty. Prizes will be paid using PayPal.</div>
Byte
https://wiki.koozali.org/index.php?title=Client_Authentication:Windows&diff=13158
Client Authentication:Windows
2009-07-07T09:59:59Z
<p>Byte: /* Domain Admins group */</p>
<hr />
<div>{{Languages}}<br />
==Microsoft Windows integration with SMEserver==<br />
<br />
===Goal===<br />
Provide hints and tips to make life a bit easier in mixed environments.<br />
<br />
As suggested in this forum thread: http://forums.contribs.org/index.php?topic=39396.0<br />
<br />
=== Login to shared recources ===<br />
If you have exactly the same usernames and passwords in both clients and server, users only have to log in once (to Windows) to have direct access to shared recources on the server.<br />
<br />
=== Domain Admins group ===<br />
<br />
By default, SME Server allocates the "admin" user as the sole Domain Administrator. However, in larger environments it is often useful to have a group of users who can administer Windows workstations.<br />
<br />
To make a group of users Domain Administrators, simply name the group as normal and write "Domain Admins" as the description. When users who are members of this group next log in to a Windows workstation that is joined to the SME Server domain, they will have Local Administrator rights automatically.<br />
<br />
===How to change PDC from Windows 2003 to SME Server. ===<br />
<br />
From http://forums.contribs.org/index.php?topic=40228.new;topicseen<br />
Q: Is there any way in which '''i can do this without having to backup all the XP PC's''' and re-adding the PC's to the new Domain and then restoring all the files ?<br />
<br />
A: The Microsoft "Active Directory Migration Tool" is supposed to do all of this automatically -- but always looks like it will take 30 - 40 hours of effort to setup, debug, and test prior to hitting the "go" button...<br />
<br />
I move PC's from one domain to another as follows:<br><br />
* Setup identical usernames on the new domain controller<br><br />
* Add the computer to the new domain<br><br />
* Login to the new domain NOT as the user who uses this computer (but with local administrative rights on the workstation). <br><br />
It is important to NOT login as the intended user until after the following step, or you will create a new profile directory named for the new domain, and you'll have to use the "variation" listed below. <br />
Sometimes (if the old profile included auto-start programs that don't close on logout), you may need to reboot the computer, making sure that the first login after reboot is to a user account that is NOT the intended user for the computer in order to be able to rename the intended user's profile.<br><br />
* Rename the user's profile c:\documents and settings\username ==> c:\documents and settings\username.old<br><br />
* logout<br><br />
* login as the intended user (re-creating "c:\documents and settings\username")<br><br />
* logout<br><br />
* login as another user with local admin rights (the same user used above, for example)<br><br />
* rename the new userprofile c:\documents and settings\username ==> c:\documents and settings\username.new<br><br />
* rename the old user profile c:\documents and settings\username.old ==> c:\documents and settings\username<br><br />
* Change the ownership of the old profile to be the new user (or give the new user local administrative rights on the workstation)<br><br />
* logout<br><br />
* login as the new user - s/he should now have the exact same environment s/he had on the Windows server.<br><br />
<br />
'''Variation''' - can't use the old username, or old profile name is incorrect, or you've already created a new profile name for the intended user<br />
If the old profile name is "username.domainname", or if you're trying to change the username but keep the settings from the old system:<br><br />
* download and install the Windows 2003 Resource Kit<br><br />
* follow the above procedure, ending up with the old profile named correctly for the new login credentials<br><br />
* use "linkd.exe" (from the W2k3 resource kit) to create a "link" to the new profile with the exact name of the old profile, in case any of the registry settings include a hard-coded path to the old profile directory name. <br />
(note: you don't need to install the entire resource kit on each workstation, you only need to put "linkd.exe" somewhere where you can get to it from each system - either in c:\windows on each system, or in a network share, for example)<br />
<br />
<br />
{{Incomplete}}<br />
----<br />
<noinclude>[[Category:Howto]]</noinclude></div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=12882
SME Server 8
2009-05-12T15:38:11Z
<p>Byte: /* SME Server 7.0, 7.1.x, 7.2 or 7.3*/</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta3 is based on CentOS 5.2.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=42103.0 Release Announcement for Beta3].<br />
<br />
A copy of the Beta3 CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
Here are a list of the Testing Team for this release.<br />
<br />
====Coordinator====<br />
* Gavin Weight<br />
====Members====<br />
* Craig Jensen (~2 hrs a week [going back to school])<br />
* Brian Read (~2-3 hours per week)<br />
* [[User:Cactus|Cactus]] (~5 hours per week, or as long as the Miss can miss me ;-) )<br />
* Nenonano (~2-3 hours per week)<br />
* Kruhm (~2-3 hours per week)<br />
* Ed Form (~10-12 hours per week)<br />
* TechnologyWise team (8-10 hrs per week)<br />
* VIP-ire (2-3 hours per week)<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
/sbin/e-smith/db yum_repositories set sme8updates repository \<br />
Name 'SME Server 8 - smeupdates' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeupdates/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====SME Server 7.4=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.4 may upgrade, detail review of upgrade paths will start with RC versions.<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os --enablerepo=sme8updates<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x, 7.2 or 7.3=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x, 7.2 or 7.3 server upgrading yum will fail with the following error:<br />
<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os --enablerepo=sme8updates<br />
<br />
</li><li>After this step completes you will see at the end of the transaction note the error in bold:<br />
<br />
xorg-x11-libs.i386 0:6.8.2-1.EL.33 yum-plugin-fastestmirror.noarch 0:0.2.4-3.c4<br />
Complete!<br />
'''rpmdb: Program version 4.3 doesn't match environment version'''<br />
'''error: db4 error(-30974) from dbenv->open: DB_VERSION_MISMATCH: Database environment version mismatch'''<br />
'''error: cannot open Packages index using db3 - (-30974)'''<br />
'''error: cannot open Packages database in /var/lib/rpm'''<br />
==============================================================<br />
WARNING: You now need to run BOTH of the following commands<br />
to ensure consistent system state: <br />
<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
You should run these commands unless you are certain that<br />
yum made no changes to your system.<br />
==============================================================<br />
<br />
You will need to run at command line the following before issuing step 6.<br />
<br />
rm -f /var/lib/rpm/__db.00*<br />
rpm --rebuilddb<br />
<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=12756
SME Server 8
2009-04-19T11:47:22Z
<p>Byte: /* SME Server 7.0, 7.1.x or 7.2 */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta3 is based on CentOS 5.2.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=42103.0 Release Announcement for Beta3].<br />
<br />
A copy of the Beta3 CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
Here are a list of the Testing Team for this release.<br />
<br />
====Coordinator====<br />
* Gavin Weight<br />
====Members====<br />
* Craig Jensen (~2 hrs a week [going back to school])<br />
* Brian Read (~2-3 hours per week)<br />
* [[User:Cactus|Cactus]] (~5 hours per week, or as long as the Miss can miss me ;-) )<br />
* Nenonano (~2-3 hours per week)<br />
* Kruhm (~2-3 hours per week)<br />
* Ed Form (~10-12 hours per week)<br />
* TechnologyWise team (8-10 hrs per week)<br />
* VIP-ire (2-3 hours per week)<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
/sbin/e-smith/db yum_repositories set sme8updates repository \<br />
Name 'SME Server 8 - smeupdates' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeupdates/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====SME Server 7.4=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.4 may upgrade, detail review of upgrade paths will start with RC versions.<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os --enablerepo=sme8updates<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x or 7.2=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x or 7.2 server upgrading yum will fail with the following error:<br />
<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os --enablerepo=sme8updates<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=12755
SME Server 8
2009-04-19T11:46:58Z
<p>Byte: /* SME Server 7.4 */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta3 is based on CentOS 5.2.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=42103.0 Release Announcement for Beta3].<br />
<br />
A copy of the Beta3 CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
Here are a list of the Testing Team for this release.<br />
<br />
====Coordinator====<br />
* Gavin Weight<br />
====Members====<br />
* Craig Jensen (~2 hrs a week [going back to school])<br />
* Brian Read (~2-3 hours per week)<br />
* [[User:Cactus|Cactus]] (~5 hours per week, or as long as the Miss can miss me ;-) )<br />
* Nenonano (~2-3 hours per week)<br />
* Kruhm (~2-3 hours per week)<br />
* Ed Form (~10-12 hours per week)<br />
* TechnologyWise team (8-10 hrs per week)<br />
* VIP-ire (2-3 hours per week)<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
/sbin/e-smith/db yum_repositories set sme8updates repository \<br />
Name 'SME Server 8 - smeupdates' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeupdates/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====SME Server 7.4=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.4 may upgrade, detail review of upgrade paths will start with RC versions.<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os --enablerepo=sme8updates<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x or 7.2=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x or 7.2 server upgrading yum will fail with the following error:<br />
<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=12751
SME Server 8
2009-04-17T16:16:51Z
<p>Byte: /* Setting up your SME Server 8 repository */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta3 is based on CentOS 5.2.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=42103.0 Release Announcement for Beta3].<br />
<br />
A copy of the Beta3 CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
Here are a list of the Testing Team for this release.<br />
<br />
====Coordinator====<br />
* Gavin Weight<br />
====Members====<br />
* Craig Jensen (~2 hrs a week [going back to school])<br />
* Brian Read (~2-3 hours per week)<br />
* [[User:Cactus|Cactus]] (~5 hours per week, or as long as the Miss can miss me ;-) )<br />
* Nenonano (~2-3 hours per week)<br />
* Kruhm (~2-3 hours per week)<br />
* Ed Form (~10-12 hours per week)<br />
* TechnologyWise team (8-10 hrs per week)<br />
* VIP-ire (2-3 hours per week)<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
/sbin/e-smith/db yum_repositories set sme8updates repository \<br />
Name 'SME Server 8 - smeupdates' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeupdates/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====SME Server 7.4=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.4 may upgrade, detail review of upgrade paths will start with RC versions.<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x or 7.2=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x or 7.2 server upgrading yum will fail with the following error:<br />
<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=12750
SME Server 8
2009-04-17T14:52:21Z
<p>Byte: /* Setting up your SME Server 8 repository */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta3 is based on CentOS 5.2.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=42103.0 Release Announcement for Beta3].<br />
<br />
A copy of the Beta3 CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
Here are a list of the Testing Team for this release.<br />
<br />
====Coordinator====<br />
* Gavin Weight<br />
====Members====<br />
* Craig Jensen (~2 hrs a week [going back to school])<br />
* Brian Read (~2-3 hours per week)<br />
* [[User:Cactus|Cactus]] (~5 hours per week, or as long as the Miss can miss me ;-) )<br />
* Nenonano (~2-3 hours per week)<br />
* Kruhm (~2-3 hours per week)<br />
* Ed Form (~10-12 hours per week)<br />
* TechnologyWise team (8-10 hrs per week)<br />
* VIP-ire (2-3 hours per week)<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeos/i386/ ' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
/sbin/e-smith/db yum_repositories set sme8updates repository \<br />
Name 'SME Server 8 - smeupdates' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeupdates/i386/ ' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====SME Server 7.4=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.4 may upgrade, detail review of upgrade paths will start with RC versions.<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x or 7.2=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x or 7.2 server upgrading yum will fail with the following error:<br />
<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=12749
SME Server 8
2009-04-17T14:51:46Z
<p>Byte: /* Setting up your SME Server 8 repository */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta3 is based on CentOS 5.2.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=42103.0 Release Announcement for Beta3].<br />
<br />
A copy of the Beta3 CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
Here are a list of the Testing Team for this release.<br />
<br />
====Coordinator====<br />
* Gavin Weight<br />
====Members====<br />
* Craig Jensen (~2 hrs a week [going back to school])<br />
* Brian Read (~2-3 hours per week)<br />
* [[User:Cactus|Cactus]] (~5 hours per week, or as long as the Miss can miss me ;-) )<br />
* Nenonano (~2-3 hours per week)<br />
* Kruhm (~2-3 hours per week)<br />
* Ed Form (~10-12 hours per week)<br />
* TechnologyWise team (8-10 hrs per week)<br />
* VIP-ire (2-3 hours per week)<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section <br />
<br />
This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
/sbin/e-smith/db yum_repositories set sme8updates repository \<br />
Name 'SME Server 8 - smeupdates' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeupdates/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
signal-event yum-modify<br />
<br />
=====SME Server 7.4=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.4 may upgrade, detail review of upgrade paths will start with RC versions.<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x or 7.2=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x or 7.2 server upgrading yum will fail with the following error:<br />
<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=Top_5&diff=12211
Top 5
2009-01-22T19:31:31Z
<p>Byte: correcting amount of projects for time being.</p>
<hr />
<div>These are four (at the moment) projects that are almost ready and would be nice to have finished and documented.<br />
<br />
See if you can help test or contribute to them. <br />
We limit the projects to four (at the moment) to concentrate effort. <br />
<br />
<br />
<br />
===Backup with dar===<br />
http://wiki.contribs.org/Backup_with_dar<br />
<br />
Released in 7.4<br />
<br />
===Disable yum remove===<br />
Updated rpm currently in smeupdates-testing. For details see [[bugzilla:3133]].<br />
<br />
===Shadow Copy===<br />
This is implemented<br />
<br />
For usage see the wiki entry [[ShadowCopy]].<br />
<br />
===LDAP user account information and authentication===<br />
http://wiki.contribs.org/LDAP<br />
<br />
Storing user information and authentication in a LDAP backend would improve adding Linux workstations to the domain as well ([http://us1.samba.org/samba/docs/man/Samba-HOWTO-Collection/winbind.html#id412238 Samba man pages: Winbind: Microsoft Active Directory Services]).</div>
Byte
https://wiki.koozali.org/index.php?title=User:Cactus/Sandbox/Badges&diff=12150
User:Cactus/Sandbox/Badges
2009-01-15T21:57:42Z
<p>Byte: /* Design Challenge:Contribs.org forum badges */</p>
<hr />
<div>=Design Challenge:Contribs.org forum badges=<br />
<br />
You might have noticed that a lot of users in the forums have a badge underneath their user name ranging from tasks they have in the contribs.org community to their donation status. During the years there have been a few flavors made by enthusiast members of the community.<br />
<br />
The current ones look like this to give you a idea on what we are looking for. <br />
{{Image:Forumbadges.}}<br />
As you can see they could at least use some TLC by someone with a little more graphic skills to improve the quality, therefore we suggest a design challenge to see if we have community members with graphic skills who can do better and come up with a set of nice badges we can use in the forums.<br />
<br />
==Regulations==<br />
Since no challenge can be without rules we decided on a small set to not limit creativity to much.<br />
<br />
===Ownership===<br />
All artwork will be submitted, including templates and other used items like fonts will be submitted to contribs.org community in order to ensure we can (re)create, enhance and modify badges in the future.<br />
<br />
===Decision===<br />
The decision on the eventual winner will be made by a limited group of people which will be fixed and not open for discussion.<br />
The following people will decide on the winner of the challenge.<br />
<br />
===Price===<br />
Since we are a community that does things for free you will not benefit material or financial when winning the contest. You will however get honor as well as your badges being used on the forums in the contribs.org community.<br />
<br />
===Deadline===<br />
{{Incomplete}}<br />
<br />
==Requirements==<br />
<br />
===Dimensions===<br />
Resolution of the badges should be 72 dpi (dots per inch) and have maximum dimensions of 140 (width) by 80 (height) pixels.<br />
<br />
===What badges?===<br />
We would like badges for the following categories:<br />
* Site Administrator<br />
* Global Moderator<br />
* Forum Moderator<br />
* Bronze Supporter<br />
* Silver Supporter<br />
* Gold Supporter<br />
* Platinum Supporter<br />
* Site Supporter<br />
* QA & Testing Team<br />
* Wiki & Docs Team<br />
* Development Team<br />
* Forum Moderator (DE)<br />
* Forum Moderator (ES)<br />
* Forum Moderator (FR)<br />
* Forum Moderator (IT)<br />
* Forum Moderator (SV)<br />
* Forum Moderator (VoiP)<br />
<br />
===Logo===<br />
The whole Contribs.org logo should be present in the badges as well as the text "SME Server" and the category listed in the paragraph above.<br />
<br />
===Colors===<br />
The colors used for the logo should be the following:<br />
<br />
{| class="wikitable" style="text-align:center"<br />
|+Conribs.org logo colors<br />
|-<br />
! color !! R !! G !! B !! sample<br />
|-<br />
! blue<br />
| 4 || 128 || 182 || {{Colorsample|rgb(4,128,182)}}<br />
|-<br />
! green<br />
| 179 || 220 || 16 || {{Colorsample|rgb(179,220,16)}}<br />
|-<br />
! orange<br />
| 255 || 102 || 0 || {{Colorsample|rgb(255,102,0)}}<br />
|-<br />
! yellow<br />
| 255 || 204 || 0 || {{Colorsample|rgb(255,204,0)}}<br />
|}<br />
<br />
You are free to choose any of the other colors used in the badges, provided that there is a general style.<br />
<br />
==Existing artwork==<br />
The following existing artwork is available that can be used as a base for your badges:<br />
{{Incomplete}}<br />
<br />
==How to submit you artwork?==<br />
{{Incomplete}}</div>
Byte
https://wiki.koozali.org/index.php?title=User:Cactus/Sandbox/Badges&diff=12149
User:Cactus/Sandbox/Badges
2009-01-15T21:56:15Z
<p>Byte: /* Price */</p>
<hr />
<div>=Design Challenge:Contribs.org forum badges=<br />
<br />
You might have noticed that a lot of users in the forums have a badge underneath their user name ranging from tasks they have in the contribs.org community to their donation status. During the years there have been a few flavors made by enthusiast members of the community.<br />
<br />
The current ones look like this to give you a idea on what we are looking for. <br />
{{Image:Forumbadges.}}<br />
As you can see they could at least use some TLC by someone with a little more graphic skills to improve the quality, therefore I suggest a design challenge to see if we have community members with graphic skills who can do better and come up with a set of nice badges we can use in the forums.<br />
<br />
==Regulations==<br />
Since no challenge can be without rules we decided on a small set to not limit creativity to much.<br />
<br />
===Ownership===<br />
All artwork will be submitted, including templates and other used items like fonts will be submitted to contribs.org community in order to ensure we can (re)create, enhance and modify badges in the future.<br />
<br />
===Decision===<br />
The decision on the eventual winner will be made by a limited group of people which will be fixed and not open for discussion.<br />
The following people will decide on the winner of the challenge.<br />
<br />
===Price===<br />
Since we are a community that does things for free you will not benefit material or financial when winning the contest. You will however get honor as well as your badges being used on the forums in the contribs.org community.<br />
<br />
===Deadline===<br />
{{Incomplete}}<br />
<br />
==Requirements==<br />
<br />
===Dimensions===<br />
Resolution of the badges should be 72 dpi (dots per inch) and have maximum dimensions of 140 (width) by 80 (height) pixels.<br />
<br />
===What badges?===<br />
We would like badges for the following categories:<br />
* Site Administrator<br />
* Global Moderator<br />
* Forum Moderator<br />
* Bronze Supporter<br />
* Silver Supporter<br />
* Gold Supporter<br />
* Platinum Supporter<br />
* Site Supporter<br />
* QA & Testing Team<br />
* Wiki & Docs Team<br />
* Development Team<br />
* Forum Moderator (DE)<br />
* Forum Moderator (ES)<br />
* Forum Moderator (FR)<br />
* Forum Moderator (IT)<br />
* Forum Moderator (SV)<br />
* Forum Moderator (VoiP)<br />
<br />
===Logo===<br />
The whole Contribs.org logo should be present in the badges as well as the text "SME Server" and the category listed in the paragraph above.<br />
<br />
===Colors===<br />
The colors used for the logo should be the following:<br />
<br />
{| class="wikitable" style="text-align:center"<br />
|+Conribs.org logo colors<br />
|-<br />
! color !! R !! G !! B !! sample<br />
|-<br />
! blue<br />
| 4 || 128 || 182 || {{Colorsample|rgb(4,128,182)}}<br />
|-<br />
! green<br />
| 179 || 220 || 16 || {{Colorsample|rgb(179,220,16)}}<br />
|-<br />
! orange<br />
| 255 || 102 || 0 || {{Colorsample|rgb(255,102,0)}}<br />
|-<br />
! yellow<br />
| 255 || 204 || 0 || {{Colorsample|rgb(255,204,0)}}<br />
|}<br />
<br />
You are free to choose any of the other colors used in the badges, provided that there is a general style.<br />
<br />
==Existing artwork==<br />
The following existing artwork is available that can be used as a base for your badges:<br />
{{Incomplete}}<br />
<br />
==How to submit you artwork?==<br />
{{Incomplete}}</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server:Documentation:FAQ&diff=11732
SME Server:Documentation:FAQ
2008-12-05T18:00:23Z
<p>Byte: /* Is PHP 4.x on SME Server still save to run? */</p>
<hr />
<div>{{Languages|SME_Server:Documentation:FAQ}}<br />
<br />
==Frequently Asked Questions==<br />
<br />
This Section lists ''Frequently Asked Questions'' (FAQ) for SME 7. Problems many people run into installing SME 7 for the first time or upgrading to later versions are found here.<br />
<br />
If your question isn't listed here, it's possible it's a ''Rarely Asked Question'' (RAQ), in which case you'll be better off searching for answers in [http://bugs.contribs.org Bugzilla]. <br />
<br />
===Installation troubles===<br />
====Installer prompts for installation file location====<br />
Problems have been reported installing SME Server off a PATA CD-ROM drive. The system is able to boot from the CD-ROM drive but after that you get prompted by a message to specify the location where the installation image can be found. This might either mean that the disk is not readable or the CD-ROM drive is not recognized.<br />
If you have validated the disk and are sure that the disk passes you might try to add the all-generic-ide option to the boot prompt before starting the installer like this:<br />
linux all-generic-ide<br />
<br />
===Yum Updates===<br />
==== Which repositories should be enabled====<br />
<br />
You should have the following repositories enabled (blue)<br />
CentOS - os<br />
CentOS - updates<br />
SME Server - addons<br />
SME Server - extras<br />
SME Server - os<br />
SME Server - updates.<br />
<br />
DO NOT enable '''SME Server - updates testing''' which is considered beta, unless<br />
* it is a TEST server NOT a production server or<br />
* you want to be part of a bug-testing group.<br />
<br />
Additionally <br />
* '''SME Server - test''' is considered alpha <br />
* '''SME Server - dev''' contains automatically built rpms. It contains lots of experimental,<br />
incomplete and mutually incompatible packages.<br />
<br />
{{Warning box|msg=If upgrading from a system prior to 7.1 update 1, ie a 7.1 CD install or earlier,<br />
you need to ensure you have the latest versions of the following rpms prior to applying the rest of the updates.<br />
This speeds up install process and avoids updates from centos that may be ahead of the distribution.<br />
<br />
yum update dbus dbus-glib smeserver-support smeserver-yum yum yum-plugin-fastest-mirror python-sqlite <br />
signal-event post-upgrade; signal-event reboot<br />
}}<br />
<br />
{{Note box|A system installed from the SME 7.1 CD will have the 5 repositories above enabled. A system installed from the SME 7.0 iso and updated to 7.1 or later will only have the 3 SME Server repositories enabled. After updating from SME 7.0 to SME 7.1.x you should enable the ''Centos - os'' & ''Centos - updates'' repositories in server-manager.<br />
}}<br />
<br />
*For another way to reset the repositories to the default see [[:Adding_Software#Restoring_Default_Yum_Repositories]]<br />
<br />
====Reconfigure / post-upgrade and reboot====<br />
*When is a post-upgrade and reboot required?<br />
The server manager yum installer has no way of determining whether<br />
any configuration files will change if all are re-expanded or to know which<br />
binaries have changed (or use libraries which have now changed) and therefore<br />
need to be restarted. The only '''safe''' option is to reconfigure and restart<br />
everything.<br />
<br />
After clicking '''Reconfigure''' check the Status message and that the server does actually reboot.<br />
Rarely circumstances arise that prevent the reconfigure from triggering. If so run the following,<br />
<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
====Updating from SME 7.x to SME 7.2====<br />
See [[:Updating_to_SME_7.2#Yum_Update]]<br />
<br />
<br />
<br />
====General====<br />
*Please Wait - Yum Running (prereposetup)<br />
This means Yum is working out what updates are available.<br />
Occasionally such as when large sets of updates are released this could take 10+ minutes to complete<br />
<br />
*Yum doesn't seem to be working correctly. What do I do now?<br />
If for some reason you can't get yum to work correctly, try:<br />
yum clean metadata<br />
or possibly 'yum clean all'<br />
yum update<br />
<br />
*Fix for 'Metadata file does not match checksum'<br />
Typical error message<br />
http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz: <br />
[Errno -1] Metadata file does not match checksum Trying other mirror.<br />
Error: failure: repodata/primary.xml.gz from dag: [Errno 256] No more mirrors to try.<br />
<br />
To flush the up stream proxies, using wget, run:<br />
<br />
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/filelists.xml.gz<br />
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/primary.xml.gz<br />
wget --cache=off http://apt.sw.be/fedora/3/en/i386/dag/repodata/repomd.xml<br />
yum update<br />
<br />
* An unclean shutdown during a system update can put the system into a state where it's difficult to recover.<br />
find all the duplicate rpm's<br />
rpm -qa | sort | less <br />
Then remove all the duplicate rpm's<br />
rpm -e --nodeps rpmname<br />
Install the newest rpms <br />
yum install rpmname<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
* Where can I go to learn more about yum, and about how SME uses it?<br />
[[:Adding_Software ]], man yum, http://linux.duke.edu/projects/yum/<br />
<br />
====Adding, removing or disabling repositories ====<br />
<br />
*What is the recommended way to add other yum repositories<br />
The following code uses the dag repository as an example and sets the status to disabled. <br />
The repository is configured to be used via the command line with the --enablerepo= option <br />
{{Repository|dag}}<br />
<br />
*How do I remove yum repositories<br />
<br />
db yum_repositories delete repositoryname<br />
signal-event yum-modify<br />
<br />
*How do I disable a repository to allow future use via command line with the --enablerepo= option<br />
<br />
db yum_repositories repositoryname setprop status disabled<br />
signal-event yum-modify<br />
<br />
====Other popular repositories====<br />
<br />
http://wiki.contribs.org/Category:Yum_Repository<br />
<br />
Be careful updating software from these repositories. Only update packages by name eg.<br />
yum update --enablerepo=reponame packagename<br />
<br />
Do not do a general update with the 3rd party repository enabled as it could update many packages that will overwrite SME versions.<br />
<br />
===Hardware Compatibility List===<br />
[http://wiki.contribs.org/KnownProblems#Hardware List of Hardware that known have problems with SME Server]<br />
<br />
Maintaining a complete HCL is difficult, <br />
the following links will give a indication of hardware being used by SME Servers and upstream providers<br />
<br />
*https://hardware.redhat.com/index.cgi<br />
*http://smolt.contribs.org<br />
*http://wiki.centos.org/HardwareList<br />
<br />
===Client Computers===<br />
<br />
*Samba trust relationships lost?<br />
This is a possible bug with an upgrade from SME6. After an upgrade, local workstations cannot log in. If you are experiencing this problem, please have a look at this bug for a fix, and provide followup: <br />
[https://sourceforge.net/tracker/index.php?func=detail&amp;aid=1234009&amp;group_id=96750&amp;atid=615772]<br />
<br />
<br />
*Windows XP Clients - Patch to logon to SME domain<br />
This patch can be used when Windows XP clients won't be able to log on to the SME Server domain. The registry patch is located here: <br />
http://servername/server-resources/regedit/winxplogon.reg<br />
Double click on the winxplogon.reg file and the settings will be added to the Windows Registry.<br />
<br />
<br />
*How to disable password caching on Windows 95/98/ME/2000 Clients?<br />
This patch can be used if you don't want Windows clients to remember password for shared folders on SME Server. The registry patch is located here: http://servername/server-resources/regedit/win98pwdcache.reg <br />
Just double click on the win98pwdcache.reg file and the settings will be added to the Windows Registry. <br />
<br />
'''Note'''<br />
Although the filename seems to indicate that this patch will only work for Windows 98, but it also works in Windows 95, Windows ME and Windows 2000.<br />
<br />
<br />
*LDAP Directory Gives MAPI_E_CALL_FAIL Errors on Outlook 2002 or Outlook 2003<br />
In Outlook 2002 or 2003 when someone tries to find a contact using the LDAP server, a message stating that "Unavailable critical extension" and then a second message saying "The search could not be completed. MAPI_E_CALL_FAIL" shows up and nothing shows up from the search. The directory works beautifully in Thunderbird 1.5 as well as Outlook 2000, but not 2002 or 2003. More information can be found here: [http://support.microsoft.com/default.aspx?scid=kb;en-us;555536&amp;sd=rss&amp;spid=2559] [http://bugs.contribs.org/show_bug.cgi?id=1406]<br />
<br />
<br />
*Where is the netlogon directory?<br />
The netlogon directory is located on the SMESERVER at: /home/e-smith/files/samba/netlogon<br />
It can also be found by a client computer at: \\servername\netlogon<br />
<br />
===Web Applications===<br />
*chmod 777<br />
<br />
Using 777 is always wrong (despite the fact that many howtos recommend it). 0770 is sufficient, as long as www is a member of the group owning the directory, and is safer.<br />
<br />
Use chown www /path/to/dir <br /><br />
and preferably put your app in /opt/app not in an ibay <br />
<br />
* Generic Instructions for Installing a Web Application<br />
http://wiki.contribs.org/Generic_WebApp_rpm<br />
<br />
*Wasn't mod_perl installed in previous versions? How do I install it?<br />
It may have been, but it was not used so it is no longer included. If you do want to install it do the following:<br />
<br />
'''Note'''<br />
The commands on a linux shell are case-sensitive, this means that Capital is not the same as capital.<br />
<br />
yum install mod_perl<br />
config setprop modPerl status enabled<br />
signal-event post-upgrade ; signal-event reboot<br />
<br />
*The directory structure is visible. How do I disable indexes in ibays?<br />
SME Server 6.0, 6.0.1, and 6.5 all had the following for the ibays/html directory - "Options Indexes Includes". This would indicate that indexes were allowed for html directories. In SME Server 7.0 this is made a parameter and it defaults to enabled to be compatible with SME Server releases before SME Server 7.0 installations. <br />
<br />
To disable indexes for an ibay in SME Server 7.0 do the following:<br />
<br />
db accounts setprop //ibayname// Indexes disabled <br />
signal-event ibay-modify //ibayname// <br />
<br />
This issue was first reported here: <br />
[[https://sourceforge.net/tracker/?func=detail&amp;atid=615772&amp;aid=1275351&amp;group_id=96750]]<br />
<br />
*I need to create (or install) a PHP application that needs access to the /tmp directory.<br />
db accounts setprop ibayname PHPBaseDir /tmp/:/home/e-smith/files/ibays/ibayname/<br />
signal-event ibay-modify ibayname<br />
<br />
By default if you have PHP code in an IBAY, it can only run in that IBAY. The above commands will allow PHP code in the IBAY to run outside of its installed directory. <br />
<br />
Here is a list of all the [[:DB_Variables_Configuration#Apache_server_ibay_specific_.28httpd-e-smith.29 | IBAY specific settings]]<br />
<br />
===Reset the root and admin password===<br />
<br />
1. Restart your server and at the beginning of the boot-up use the arrow keys to select the kernel you would like to boot into.<br />
<br />
2. Press A , to allow you to append parameters to your grub boot settings.<br />
<br />
3. Be careful not to change anything, only add the following after the A (Be sure to put a space before single):<br />
single<br />
4. Press enter. you will be presented with a prompt.<br />
<br />
5. At this prompt type the following two commands (each followed by a return). You will be asked to provide a new password. <br />
Reset both your root and your admin password and set them to the same value:<br />
passwd root<br />
passwd admin<br />
Reboot your server and everything should be okay now.<br />
<br />
<br />
===File Size Limitations===<br />
*Apache, the web server can only transfer or show files under 2G<br />
<br />
*Backup to USB Disk<br />
FAT32 only supports file size of <4GB. It is recommended that you format your external usb drives to ext3.<br />
<br />
<br />
===Domains===<br />
<br />
*When I create a DOMAIN, I don't see anything listed in the HOSTNAMES AND ADDRESSES panel for that DOMAIN.<br />
<br />
For a domain to be effective (for email or web), it needs to be configured as INTERNET DNS SERVERS (this is the default value). Since the domain resolves via INTERNET DNS SERVERS, no hostnames or addresses are created locally. For more info please visit the Administration Manual section regarding Domains: [[http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter13#Domains]]<br />
<br />
<br />
===Virus Scanning===<br />
*When you elect to nightly scan your server for viruses the current default is to scan /home/e-smith/files<br />
<br />
Note that early SME 7 Servers defaulted to /. <br />
<br />
Also you may want to scan under /opt if have contribs that store user data there<br />
<br />
the db property to change to the default <br />
config setprop clamav FilesystemScanFilesystems /home/e-smith/files<br />
or to scan different areas of the server is<br />
config setprop clamav FilesystemScanFilesystems /home/e-smith/files,/opt<br />
<br />
*How do I exclude some directories from scanning<br />
Set the db value to exclude more directories<br />
<br />
The default<br />
config setprop clamav FilesystemScanExclude /proc,/sys,/usr/share,/var<br />
<br />
Change with<br />
config setprop clamav FilesystemScanExclude /proc,/sys,/usr/share,/var,/home/e-smith/files/ibays<br />
<br />
After any change, run the signal-event for expand and regenerate configuration files, and restart pertinent services<br />
<br />
signal-event clamav-update<br />
<br />
===Proxy Pass===<br />
<br />
*I want to pass some http requests to a server behind my SME Server or external to my site, how can I do this?<br />
<br />
You can set a ProxyPass directive that will pass certain requests to an internal or external server that hosts the domain to be proxypassed<br />
db domains set proxypassdomain.com domain <br />
db domains setprop proxypassdomain.com Nameservers internet<br />
db domains setprop proxypassdomain.com ProxyPassTarget http://xxx.xxx.xxx.xxx/<br />
db domains setprop proxypassdomain.com TemplatePath ProxyPassVirtualHosts <br />
signal-event domain-create proxypassdomain.com<br />
where proxypassdomain.com is the domain name hosted on the internal or external server<br />
and http://xxx.xxx.xxx.xxx/ is the IP address of the internal or external server eg 192.168.1.20 or 122.456.12.171 (it must be the publicly accessible IP if an external server)<br />
{{Note box|If you have added the internal or external server's domain name as a virtual domain on the SME Server, you must remove it prior to issuing these commands. The server-manager domains panel will show the proxy pass entry but you will not be able to edit it, see [[bugzilla:1612]].<br />
}}<br />
<br />
===Shell Access===<br />
*I need to give a user shell access to the SME Server.<br />
<br />
Shell access should only be provided to users who have a *need* for it and can be trusted. <br />
<br />
Before a user can have shell access Admin must enable ssh access at <br />
server-manager -> Security -> Remote Access<br />
<br />
You then enable shell access for a user by:<br />
db accounts setprop username Shell /bin/bash<br />
chsh -s /bin/bash username<br />
<br />
===Upgrading Server===<br />
*What's the best way to upgrade to a new server ?<br />
An article is written for this subject. Please visit: http://wiki.contribs.org/UpgradeDisk<br />
<br />
===Changing maximum Ibay, Account or Group name length===<br />
* How do I change the default maximum (12 characters) name length of an I-Bay, account or group?<br />
Enter following command on the console as root:<br />
/sbin/e-smith/db configuration set maxIbayNameLength xx<br />
/sbin/e-smith/db configuration set maxAcctNameLength xx<br />
/sbin/e-smith/db configuration set maxGroupNameLength xx<br />
where 'xx' is the new size e.g. 15.<br />
<br />
Followed by:<br />
/sbin/e-smith/signal-event console-save<br />
<br />
===Deletion of Users Ibays Groups===<br />
*I can't delete & create a user for some reason. What do I do now?<br />
If for some reason you can't delete & create a user, then first do:<br />
signal-event user-delete <username><br />
db accounts delete <username><br />
<br />
*I can't delete & create a ibay for some reason. What do I do now?<br />
If for some reason you can't delete & create a ibay, then first do:<br />
signal-event ibay-delete <ibayname><br />
db accounts delete <ibayname><br />
<br />
*I can't delete & create a group for some reason. What do I do now?<br />
If for some reason you can't delete & create a group, then first do:<br />
signal-event group-delete <groupname><br />
db accounts delete <groupname><br />
<br />
<br />
*I was looking in the home directory of a user and I see a hidden directory called ".junkmail". Do I need that? Can I delete it?<br />
Don't remove or rename .junkmail folders.<br />
<br />
===Password Strength Checking===<br />
*How can I change password strength & what do the strength settings mean?<br />
<br />
{{Warning box|It is strongly advised not to set the password strength setting to ''none'' as this will lower the security of your server significantly.}}<br />
<br />
{{Note box|PAM module requires passwords to be at least 6 characters long, so setting a password that is shorter than that may cause other problems later. SME server default settings enforce 7 character passwords.}}<br />
<br />
The following settings are available to specify the password strength on SME Server:<br />
<br />
{|<br />
! setting<br />
! explanation<br />
|- <br />
| ''strong'' <br />
| The password is passed through Cracklib for dictionary type word checking as well as requiring upper case, lower case, number, non alpha and a mimimum length of 7 characters.<br />
|- <br />
| ''normal''<br />
| The password requires upper case, lower case, number, non alpha and a minimum length of 7 characters.<br />
|- <br />
| ''none''<br />
| The password can be anything as no checking is done.<br />
Please note that "none" does not mean no password, it just means no password strength checking, so you can enter any (weak) password you want as long as it is at least 7 characters long.<br />
|}<br />
<br />
To set password strength do:<br />
config setprop passwordstrength Admin strengthvalue<br />
config setprop passwordstrength Users strengthvalue<br />
config setprop passwordstrength Ibays strengthvalue<br />
where strengthvalue is one of the entries listed in the table above.<br />
<br />
e.g. <br />
config setprop passwordstrength Users normal<br />
<br />
To review the current settings do:<br />
config show passwordstrength<br />
<br />
which should display something like:<br />
<br />
passwordstrength=configuration<br />
Admin=strong<br />
Ibays=strong<br />
Users=strong<br />
<br />
References:<br />
<ol></li><li>[https://sourceforge.net/tracker/?func=detail&atid=615772&&aid=1228269&group_id=96750 Old Bugtracker on SF.net: Sme7a22 - user passwords]<br />
</li><li>[[Bugzilla:161]]</li><br />
<li>[[Bugzilla:2686]]</li></ol><br />
<br />
<br />
===Hard Drives, RAID's, USB Hard Drives===<br />
*How should I setup my hard-drives?<br />
We never recommend anything other than a '''single disk install''' or '''multiple disks of the same type'''. Anything else and you are following an unrecommended setup and you will need to navigate for yourself. Repeat, we never recommend anything other than a '''single disk install''' or '''multiple disks of the same type'''. If you're thinking of doing anything else (setup your own partitions), read this section again.<br />
<br />
*How should I setup my RAID?<br />
A full article on RAID is found here: [[:Raid]]<br />
<br />
<br />
*I want to use a hardware RAID. What do you suggest?<br />
Please see the notes in the RAID article: [[:Raid#Raid_Notes]]<br />
<br />
<br />
*How do I recover an SME Server with lvm drives<br />
A full article on the recovery method is found here: [[:Recovering_SME_Server_with_lvm_drives]]<br />
<br />
<br />
*I'm installing a RAID 5 but it seems to take a long time. Is there something wrong?<br />
RAID 5 systems (those with 3+ disks) can take a long time during and after the install for everything to sync. Reportedly, it takes almost 2 hours before the disks finally finish syncing on 4 X 80GB disks.<br />
<br />
<br />
*If I boot my SMESERVER with a USB hard drive attached, it recognizes the drive. However, after unplugging the drive, then replugging, it no longer exists. Any ideas why?<br />
Reportedly, some external usb hd's must be completely powered up before connecting the usb cable.<br />
<br />
<br />
*If I boot my SMESERVER with a USB hard drive attached, it doesn't recognize the drive. Any workarounds for this?<br />
Some USB drives need to be plugged twice into the server to be recognized.<br />
<br />
===Backups & Restores===<br />
*AIT-1 Backup: buffer unreliable<br />
An AIT-1 is unreliable if used with variable block size. Set the setting<br />
config setprop flexbackup TapeBlocksize 512<br />
AIT-2, DAT and LTO seem to work well with variable block size.<br />
<br />
<br />
*Slow tape backup performance may be improved by changing Flex backup settings<br />
config setprop flexbackup Blocksize 256<br />
config setprop flexbackup BufferMegs 16<br />
<br />
<br />
*In the ADMIN CONSOLE, there is an option to BACKUP TO USB but there are no restore options.<br />
The RESTORE option is only visible on a new install. If you missed this during install, you can<br />
config set PasswordSet no <br />
signal-event post-upgrade; signal-event reboot <br />
<br />
During reboot reconfiguration process you should see the new restore via USB backup option. <br />
-NOW plug in the usb drive (Do not plug in the usb drive until you reach this point).<br />
-pick YES or RESTORE (or whatever is presented to you)<br />
<br />
<br />
===Supervised Services===<br />
*Many services on SME are supervised, to see which are type<br />
ps ax |grep runsv<br />
To control them read the sv manual<br />
man sv<br />
<br />
*it seems that "sv u http-e-smith" gives no errors, even if the service fails to restart, so you need to use "sv s httpd-e-smith" to check if it fails (example: due to a httpd.conf error)<br />
<br />
This is just the way that runsv (part of the runit package) works. The "sv u http-e-smith"<br />
only sends a message to runsv saying that we want the service to be up. <br />
runsv then will keep trying to get the service running.<br />
<br />
<br />
===Server-Manager===<br />
*I can't access the server-manager. What do I do now?<br />
There are many reasons why you wouldn't be to access the server-manager. First try:<br />
signal-event post-upgrade; signal-event reboot<br />
<br />
If you still can't access, there are reports that a certificates mis-match might have occurred after update. In that case:<br />
rm /home/e-smith/ssl.key/*.key<br />
rm /home/e-smith/ssl.pem/*.pem<br />
rm /home/e-smith/ssl.crt/*.crt<br />
signal-event domain-modify; signal-event reboot<br />
<br />
<br />
*I used to access the SERVER-MANAGER with localhost:980 remotely via SSH tunnel and now I can't. What happened?<br />
This feature has been deprecated a long time and finally removed in V7.2<br />
<br />
If you really want to use this then forward 443 to localhost:443 and then use<br />
https://localhost/server-manager/<br />
<br />
<br />
*Using a ssh client, the /server-manager login screen is difficult to read<br />
The text is white, so you need to adjust your ssh client to use a dark background<br />
<br />
<br />
*I've renamed my server with the ADMIN CONSOLE. The old name appears under the SERVER-MANAGER, HOSTNAMES panel. It cannot be deleted as there are no MODIFY/REMOVE links.<br />
<br />
-login to the shell console<br />
-type: db hosts setprop <local.mycompany.local> static no<br />
-go to the HOSTNAMES & ADDRESSES panel and you should be able to modify/remove the name<br />
<br />
===Booting with SMP kernel after upgrade to version 7.2 from CD===<br />
*I've upgraded and now the SMP kernel isn't available. <br />
This is because when upgrading to 7.2 from CD, kernel modules are <br />
missing for SMP '''IF''' the output of "cat/proc/cpuinfo" <br />
does not show multiple processors. The SMP kernel, if not present, can be installed via yum using:<br />
Do:<br />
yum install kernel-smp kmod-ppp-smp kmod-slip-smp kmod-appletalk-smp<br />
signal-event post-upgrade<br />
signal-event reboot<br />
Details: http://bugs.contribs.org/show_bug.cgi?id=3095<br />
<br />
*I'm getting a kernel panic after upgrade from CD. What do I do now?<br />
When upgrading with a CD, the upgrade will rewrite the grub.conf file. As a result, any additional boot arguments (i.e. acpi=off) will be lost during upgrade. Please edit the grub.conf file.<br />
<br />
<br />
===Special Characters===<br />
*I get strange characters & letters when look at my file names.<br />
If you get filenames that look like: "éèÃ.txt" It's most likely because the SME server isn't understanding special characters you may be using. You can change it to understand special characters in filenames by:<br />
db configuration setprop smb UnixCharSet ISO8859-1<br />
expand-template /etc/smb.conf<br />
/etc/init.d/smb restart<br />
<br />
<br />
===Upstream proxy server configuration===<br />
<br />
*How do I configure a mandatory upstream proxy server, there used to be a panel in earlier versions of sme server, but it's missing in sme7.x<br />
<br />
config set SquidParent a.b.c.d<br />
config set SquidParentPort nnn<br />
signal-event post-upgrade<br />
signal-event reboot<br />
<br />
[The SquidParentPort setting is optional if the upstream proxy is on port 3128.]<br />
<br />
From http://forums.contribs.org/index.php?topic=32998.msg140512#msg140512<br />
<br />
<br />
===Memory usage and limits===<br />
<br />
*How much memory can sme server handle<br />
<br />
SME server currently (v7.3) supports 16GB of RAM, with a maximum of 3GB per process. These limits can easily be increased to 64GB total and 4GB per process by installing and running the "hugemem" variant of the kernel<br />
<br />
*Why does my sme server always seem to be using all the memory, there is no spare memory left<br />
<br />
Utilities such as top or htop always report that all available memory is being used.<br />
The Linux OS is designed to utilise all available memory all of the time. If other processes require more memory then it is made available to those processes. Fully utilising all the available memory is a good thing as it optimises the performanece of your server.<br />
<br />
*How can I tell if my sme server needs more memory<br />
<br />
Watch the availabe swap memory usage eg using top, htop or ps -aux. If swap memory usage regularly exceeds 50% of the available swap memory, then you should add more physical RAM to your system.<br />
Other indications that additional RAM is required are "out of memory" messages in log files, and at times the server becomes inactive for a period, often related to spam & virus scanning & high email loads.<br />
<br />
{{:Booting}}<br />
<br />
{{:Log_Files}}<br />
<br />
{{:Email}}<br />
<br />
{{:Firewall}}<br />
<br />
{{:MySQL}}<br />
<br />
==PHP==<br />
<br />
===Why does SME Server still not have PHP 5? ===<br />
To go short SME Server is based on Centos 4.x which in term is based on RedHat Enterprise Linux 4.x. Since the development team is limited in person and time, all work is done in spare time, we do not have the time to implement such big changes and cope with the maintenance of such work.<br />
<br />
===Is PHP 4.x on SME Server still safe to run? ===<br />
Yes, because security fixes and bug fixes are backported to the 4.x releases and they are propagated to the users as updates, for more information have a look at [http://www.redhat.com/security/updates/backporting/ this page on the RedHat website].<br />
<br />
==Known Problems==<br />
<br />
{{Note box|This section is to be used to document problems that cannot or will not <br><br />
be fixed through development of SME7. <br><br />
Please refer to the [[:KnownProblems]] page}}</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=10786
SME Server 8
2008-10-05T15:31:37Z
<p>Byte: Update SME Server 8 beta status</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta2 is based on CentOS 5.2.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=42103.0 Release Announcement for Beta2].<br />
<br />
A copy of the CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
Here are a list of the Testing Team for this release.<br />
<br />
====Coordinator====<br />
* Gavin Weight<br />
====Members====<br />
* Craig Jensen (~10 hrs a week)<br />
* Brian Read (~2-3 hours per week)<br />
* [[User:Cactus|Cactus]] (~5 hours per week, or as long as the Miss can miss me ;-) )<br />
* Nenonano (~2-3 hours per week)<br />
* Kruhm (~2-3 hours per week)<br />
* Ed Form (~10-12 hours per week)<br />
* TechnologyWise team (8-10 hrs per week)<br />
* VIP-ire (2-3 hours per week)<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section (especially with SME Server 8.0beta1 as this is an early beta release). This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
The repositories for SME 8 have not been enabled. You can't update with yum for now.<br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server:Download&diff=10277
SME Server:Download
2008-07-20T21:36:57Z
<p>Byte: Add new mirror norhex</p>
<hr />
<div>The current stable release is SME Server Release 7.3 (based on CentOS 4.6), see the Main Page for details of incremental updates available with yum. <br />
<br />
Our prior stable release was SME Server Release 7.2<br />
<br />
The SME Server ISO CD image is available to [http://linuxtracker.org/index.php?page=torrent-details&id=020ccb10db6126d6c89f2840efbdef2e1850ebd1 download as a Torrent]<br />
<br />
Alternatively, please download the CD image at your closest mirror site.<br />
<br />
Hosting of SME Server releases and contribs has been generously been provided by the following:<br />
<br />
'''North America:'''<br /> <br />
[http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/7/iso ibiblio.org - USA]<br /><br />
[http://www.gtlib.gatech.edu/pub/linux/distributions/smeserver/releases/7/iso ftp.gtlib.gatech.edu - USA]<br /><br />
[http://smeserver.norhex.com/releases/7/iso norhex.com - USA]<br /><br />
<br />
'''Asia/Pacific:'''<br /> <br />
[http://mirror.pacific.net.au/linux/smeserver/releases/7/iso Pacific.net.au - Australia]<br /> <br />
<br />
'''Europe:'''<br /> <br />
[http://sme-mirror.voxteneo.com/releases/7/iso Voxteneo.com - France ]<br /><br />
[http://ftp.nluug.nl/os/Linux/distr/smeserver/releases/7/iso NLUUG.nl - Netherlands]<br /> <br />
[http://ftp.surfnet.nl/ftp/pub/os/Linux/distr/smeserver/releases/7/iso Surfnet.nl - Netherlands]<br /> <br />
[http://smemirror.fullnet.co.uk/releases/7/iso fullnet.co.uk - United Kingdom]<br />
<br />
<br />
'''Mirrors'''<br /> <br />
Further information on [http://wiki.contribs.org/Mirrors Mirrors]<br />
<br />
'''Zsync'''<br /><br />
Downloads a file over HTTP. zsync uses a control file to determine whether any blocks in the file are already known to the downloader, and only downloads the new blocks. see also '''man zsync''' and the -i option<br />
yum install zsync --enablerepo=dag<br />
zsync http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/smeserver-8.0beta1-i386.iso.zsync<br />
<br />
'''Updates:'''<br /> <br />
Upgrading to 7.x from 6.x - Upgrades from unmodified versions of SME 6.0.1 and 6.5RC1 to SME 7 is supported. If you have modified your server by installing contribs or have used any unsupported 'upgrade' scripts, you may have issues and should consider removing any incompatible contribs before upgrading.<br />
<br />
See http://wiki.contribs.org/Updating_to_SME_7.2<br />
<br />
'''Support:'''<br /> If you have questions about your download or installation, feel free to make use of the contribs.org forums. The forums are available for questions, suggestions, and general comments. You may search and find the answer to your question there.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=10276
SME Server 8
2008-07-20T21:19:30Z
<p>Byte: /* Testing Team */</p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta1 is based on CentOS 5.1.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=39499.0 Release Announcement for Beta1].<br />
<br />
A copy of the CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
Here are a list of the Testing Team for this release.<br />
<br />
Gavin Weight (Coordinator)<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section (especially with SME Server 8.0beta1 as this is an early beta release). This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
expand-template /etc/yum.conf<br />
<br />
=====SME Server 7.3=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.3 your upgrade should run problem free, if not please {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
You can upgrade your clean SME Server 7.3 server by following these steps:<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x or 7.2=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x or 7.2 server upgrading yum will fail with the following error:<br />
<br />
--> Running transaction check<br />
--> Processing Dependency: libstartup-notification-1.so.0 for package: libwnck<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Processing Dependency: startup-notification >= 0.5 for package: libwnck<br />
--> Restarting Dependency Resolution with new changes.<br />
--> Populating transaction set with selected packages. Please wait.<br />
---> Downloading header for startup-notification to pack into transaction set.<br />
startup-notification-0.8- 100% |=========================| 5.0 kB 00:00<br />
---> Package startup-notification.i386 0:0.8-4.1 set to be updated<br />
--> Running transaction check<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
================================================================<br />
No new rpms were installed. No additional commands are required.<br />
================================================================<br />
[root@example ~]#<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7.3 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7.3/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
<br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=10275
SME Server 8
2008-07-20T21:17:19Z
<p>Byte: </p>
<hr />
<div>===Status: Beta===<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good. SME Server 8.0beta1 is based on CentOS 5.1.<br />
<br />
See the [http://forums.contribs.org/index.php?topic=39499.0 Release Announcement for Beta1].<br />
<br />
A copy of the CD image can be downloaded [http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ here].<br />
<br />
===Testing Team===<br />
<br />
===Considerations before installing===<br />
Please, please any issues report to our bug tracker under the SME Server 8 section (especially with SME Server 8.0beta1 as this is an early beta release). This way all problems can be fixed as quickly, early and efficiently as possible by the development team.<br />
{{Note box|Since SME Server 8.0 is still beta no contribs will be released. Once the Release Candidate status is reached contribs will be released for contrib owners to check if their packages need updating.}}<br />
<br />
===Upgrade paths===<br />
<br />
====CD====<br />
Upgrading from CD should work fine. If not {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
====Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
expand-template /etc/yum.conf<br />
<br />
=====SME Server 7.3=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
<br />
If you are running a fresh installation of SME Server 7.3 your upgrade should run problem free, if not please {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}.<br />
<br />
You can upgrade your clean SME Server 7.3 server by following these steps:<br />
<br />
<ol></li><li>Install the necessary packages from the sme8os repository:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade; signal-event reboot<br />
</li></ol><br />
<br />
=====SME Server 7.0, 7.1.x or 7.2=====<br />
{{Note box|You are advised to only upgrade clean machines, e.g. without contribs or other modifications.}}<br />
If you are trying to upgrade from a 7.0, 7.1.x or 7.2 server upgrading yum will fail with the following error:<br />
<br />
--> Running transaction check<br />
--> Processing Dependency: libstartup-notification-1.so.0 for package: libwnck<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Processing Dependency: startup-notification >= 0.5 for package: libwnck<br />
--> Restarting Dependency Resolution with new changes.<br />
--> Populating transaction set with selected packages. Please wait.<br />
---> Downloading header for startup-notification to pack into transaction set.<br />
startup-notification-0.8- 100% |=========================| 5.0 kB 00:00<br />
---> Package startup-notification.i386 0:0.8-4.1 set to be updated<br />
--> Running transaction check<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
================================================================<br />
No new rpms were installed. No additional commands are required.<br />
================================================================<br />
[root@example ~]#<br />
<br />
You can solve this using the following steps:<br />
<ol></li><li>You will need to download the yum-metadata-parser package from the SME Server 7.3 repository:<br />
wget <nowiki>http://mirror.contribs.org/smeserver/releases/7.3/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm</nowiki><br />
</li><li>Manually install the package as below:<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
</li><li>Then type from command line:<br />
<br />
yum clean all<br />
</li><li>After that you should be able to upgrade with the following command:<br />
yum upgrade --disablerepo=* --enablerepo=sme8os<br />
</li><li>Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
</li></ol><br />
<br />
<br />
<br />
===Problems and bugs===<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]. i586 hardware means processors before and including Intel Pentium, Pentium MMX; AMD K5, K6, K6-II, K6-III and Via C3. i686 architecture processors are Intel Pentium Pro, Pentium II, Pentium III; AMD Athlon, Athlon XP and later.</div>
Byte
https://wiki.koozali.org/index.php?title=UpgradeDisk&diff=9857
UpgradeDisk
2008-05-30T08:28:06Z
<p>Byte: /* Upgrade Disk */</p>
<hr />
<div>==Upgrade Disk==<br />
<br />
Hard drive restore requires a complete system. It is meant to take a hard<br />
drive from a system, mount it, and do a restore from it. <br />
<br />
It does not restore contribs or manually added software, except if it's in an Ibay and instructs you to move custom-templates. <br />
<br />
Summarised from http://forums.contribs.org/index.php?topic=30745.0<br />
<br />
# On the old SME server prior to shutting down, at the root command prompt issue the command '''/sbin/e-smith/signal-event pre-backup''' then shutdown & remove the drive<br />
# On the new machine do a fresh install of sme7<br />
# Shut down & install old drive and start machine.<br />
# mkdir /mnt/tmp<br />
# mount /dev/hdb2 /mnt/tmp (adjust "hdb2" according to where the old drive is installed).<br />
# db configuration setprop backup Program CopyFromDisk status enabled<br />
# signal-event pre-restore<br />
# signal-event restore-tape /mnt/tmp (note: this step may take a long time depending on how much data is being restored<br />
# cd /etc/e-smith<br />
# mv templates-custom templates-custom.old<br />
# mkdir templates-custom<br />
# mv templates-user-custom templates-user-custom.old<br />
# mkdir templates-user-custom<br />
# signal-event post-upgrade<br />
# signal-event reboot<br />
# Shutdown and remove old drive<br />
<br />
<br />
Additional tips from http://forums.contribs.org/index.php?topic=39892.0<br />
which refers to http://forums.contribs.org/index.php?topic=37686.0<br />
<br />
The original disk will not mount due to volume group name conflicts with the existing drive(s).<br />
Follow this procedure to rename the volume group on the original disk:<br />
<br />
Boot from SME Server 7.1 (or newer) install CD<br />
<br />
press F5<br />
<br />
type "sme rescue" at the command prompt and hit enter<br />
<br />
Note: don't start the network and skip mounting the filesystem.<br />
<br />
mdadm -AR /dev/md5 /dev/hdx2<br />
lvm vgscan<br />
lvm vgs -v<br />
lvm vgchange -a n<br />
lvm vgrename orig_vg_name new_vg_name<br />
exit<br />
<br />
Now remove the CD and reboot<br />
<br />
mdadm -AR /dev/md5 /dev/hdx2<br />
vgscan<br />
vgchange -a y new_vg_name<br />
mkdir /mnt/tmp<br />
mount /dev/new_vg_name/root /mnt/tmp<br />
{{Note box|In some rare cases your VolumeGroup name listed in the last line might be different, more information can be found in [[bugzilla: 3883]].}}<br />
<br />
You should now be able to view all your old data under /mnt/tmp<br />
<br />
Follow the steps listed above to use CopyFromDisk to restore the data.<br />
----<br />
[[Category:Howto]]</div>
Byte
https://wiki.koozali.org/index.php?title=Package_Modification&diff=8796
Package Modification
2008-03-29T22:27:42Z
<p>Byte: /* Access to build system */</p>
<hr />
<div>===Introduction===<br />
SME Server code is stored in the CVS on http://www.sourceforge.net in two repositories:<br />
* [http://fisheye1.cenqua.com/browse/smeserver/ CVS SME Server] which holds the core packages of the SME Server<br />
* [http://fisheye1.cenqua.com/browse/smecontribs/ CVS SME Contribs] which holds the contribs packages<br />
<br />
This page is to help you make changes to the contribs packages stored on sourceforge. <br />
{{Note box|For now changes to the base are still made using mezzanine.}}<br />
<br />
===Set up===<br />
====Local environment====<br />
* We now use cvs without needing mezzanine, check you have it installed<br />
yum install cvs<br />
<br />
* Setup CVS to use ssh by creating /etc/profile.d/smebuild.sh with the following content<br />
<br />
# Developer environment<br />
# This gets symlinked into /etc/profile.d <br />
<br />
export CVS_RSH=ssh # tell CVS to use ssh<br />
<br />
# DO NOT set CVSROOT<br />
<br />
alias rm='rm -i'<br />
alias cp='cp -i --preserve=timestamps'<br />
alias mv='mv -i'<br />
You have to logout an login again to the console for changes to take effects.<br />
<br />
====Access to build system====<br />
Check updates/status on the build server: http://buildsys.contribs.org<br />
<br />
{{Warning box| For contrib builders using the plaque-client-0.5.0 you will need to downgrade to correct version, to fix this please do:<br />
<br />
rpm -e plague-client plague-common<br />
yum --enable smecontribs install plague-client.}}<br />
<br />
Ask admin@contribs.org for certificates, give the email address to use for notifications.<br />
yum --enable smecontribs install plague-client<br />
<br />
From now, do not use account "root" anymore. Use a dedicated dev account.<br />
Copy certificates and config file to ~/<br />
.plague-client.cfg<br />
.username.pem<br />
.contribs-upload-ca.pem<br />
.contribs-server-ca.pem<br />
<br />
Don't forget to set the proper privileges on the file<br />
chmod 600 .username.pem<br />
<br />
Check it's working<br />
plague-client list_builders<br />
<br />
Builders:<br />
------------------------------------------------------------------------------------------<br />
build64-1.contribs.org x86_64 amd64 ia32e noarch i386 i486 i586 i686 athlon available<br />
build32-1.contribs.org i386 i486 i586 i686 athlon noarch available<br />
<br />
====Sourceforge access====<br />
* SME Server code is stored in the CVS on http://SourceForge.net. To be able to work on your code in the SME Server CVS repository you need an account on SourceForge. With this account the development team can give you access to the CVS repository. More information can be found here:<br />
[http://sourceforge.net/docman/display_doc.php?docid=11123&group_id=1 B04: Registering a User Account]<br />
[http://sourceforge.net/docman/display_doc.php?docid=29894&group_id=1 E04: CVS (Version Control for Source Code)]<br />
[http://sourceforge.net/docs/F02/en/#top F02: SSH Key Generation and Usage]<br />
<br />
* After you have created your SourceForge account you can ask the development team to give you developer access to smecontribs. Create a bug in the Bug Tracker as usual.<br />
<br />
* Copy your local public SSH key to SourceForge https://sourceforge.net/account/editsshkeys.php <br />
<br />
* If local username is different to sf.net username edit ~/.ssh/config:<br />
<br />
Host smeserver.cvs.sourceforge.net<br />
User sfusername ''(without @shell.sf.net)''<br />
Host smecontribs.cvs.sourceforge.net<br />
User sfusername ''(without @shell.sf.net)''<br />
<br />
* Don't forget to set the proper privileges on the file<br />
<br />
chmod 600 ~/.ssh/config<br />
<br />
===Usage===<br />
====Import src.rpm====<br />
Email admin@contribs.org with the location of your rpm, it will be imported into the build system for you.<br />
<br />
====Import cvs====<br />
This is just cvs information, not source code.<br />
<br />
You can use ~/home/smeserver or whatever suits.<br />
<br />
mkdir ~/smeserver<br />
cd ~/smeserver<br />
cvs -z3 -d:ext:smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P rpms <br />
<br />
(for now changes to smeserver are still made with the mezzanine method, and updated manually by devs)<br />
<br />
mkdir ~/smecontribs<br />
cd ~/smecontribs <br />
cvs -z3 -d:ext:smecontribs.cvs.sourceforge.net:/cvsroot/smecontribs co -P rpms <br />
<br />
To refresh run the following from the rpms directory, or any lower directory with a CVS dir<br />
cvs update -dPA<br />
<br />
====Modify a package====<br />
Builders have rights to patch packages, tag, and build. <br />
If you need to upload new source tarballs or versions shad has to do that for now. Email them.<br />
Binary files are stored in a look-aside cache on shads box. CVS isn't great on binary files.<br />
<br />
Mezzanine, (mzsfget, mzclean, mzprep, mzpatch, mzbuild, mzput) have all be replaced with a new method.<br />
<br />
Create a bug at http://bugs.contribs.org against your contrib<br />
<br />
Change to work directory<br />
cd smecontribs/rpms/smeserver-foo/contribs7<br />
<br />
To prepare a tree<br />
cvs update -dPA [optional]<br />
make clean [optional]<br />
make prep<br />
<br />
=====Make a patch=====<br />
Then switch to the tree and make modification.<br />
<br />
In the prepared dir copy a file you want to modify like so:<br />
<br />
cp 28UserManagerProxyPass 28UserManagerProxyPass.{patchname}<br />
<br />
Then modify the original file 28UserManagerProxyPass.<br />
To add new files touch the file.{patchname} so it is empty. (really empty = 0kb, some file manager don't!)<br />
<br />
Once you have all the files you want patched copied and changed then you can build the patch (from the contribs7 dir) with:<br />
make patch SUFFIX={patchname}<br />
It will build and add the patch for you. It should be named "name-version-{patchname}.patch"<br />
(man gendiff. That is what the makefile uses to generate the diff file.)<br />
<br />
=====Apply a patch=====<br />
Or just apply a patch prepared elsewhere, if you don't 'make patch' you need to 'cvs add'<br />
<br />
cp into the contribs7 dir<br />
cvs add smeserver-foo-locale-2008-xx-xx.patch<br />
<br />
=====Edit the spec=====<br />
nano -w smeserver-foo.spec<br />
<br />
#increase the release<br />
%define release 15<br />
<br />
#add the patch<br />
Patch2: smeserver-foo-1.2-widget.patch<br />
<br />
#update the changelog, include the bug number<br />
* Fri Jan 11 2008 John Smith <smith@foo.net> 1.2-15<br />
- fixed foo to create bar [SME 3470]<br />
<br />
#apply the patch in %setup<br />
%patch2 -p1<br />
<br />
=====Commit=====<br />
Build the rpm locally to test, (note, this deletes the working tree!)<br />
make local <br />
<br />
Once you are satisfied and want to submit the package to the build server commit your changes. (Please use descriptive comments so that other developers are aware of what is happening. Comments will appear on the subject line of the commit email that get send to the other developers.)<br />
<br />
cvs commit -m 'your descriptive commit message here'<br />
<br />
You can automate the addition of the comments in the spec file with the command 'clog'. {{Note box|You will need to be in the sme7, sme8, or contribs7 directory for this to work}}<br />
<br />
rm -f clog<br />
cvs commit -m "$(make clog)"<br />
<br />
Then tag all files as belonging to a particular build version<br />
make tag<br />
<br />
Then submit the request to the build server which will checkout the recently tagged version and build it in a chroot (mock) env.<br />
make build<br />
<br />
Key things are to always do "make tag" before "make build" <br />
<br />
Always ensure you are working with the latest version (cvs update -dPA)<br />
<br />
You and updatesteam will get an email on successfull build. <br />
Only you will get an email on failed build.<br />
<br />
CVS cheat sheet [[:Package_Modification/More cvs commands]]<br />
<br />
====Releasing a package====<br />
After the make build command the build system will try and build your package. After a successful build it will be put in the smetest repository. You should be notified of the result of the build by e-mail.<br />
<br />
Once a package is build succesfully you should verify your changes, ideally you would have a bug to verify for each modification. After verification of all relevant changes and bugs you can release the package like this:<br />
<ol></li><li>Login to shell.contribs.org like this:<br />
<br />
ssh username@shell.contribs.org<br />
</li><li>Navigate to the teams directory:<br />
<br />
cd /teams<br />
</li><li>The teams directory contains a few directories of which two are relevant, the first is called updates which will hold the SME Server packages, the other is called contribs and will hold build contribs.<br />
Suppose we would like to release our contrib we would proceed like this:<br />
<br />
cd contribs/7<br />
</li><li>Now copy the relevant package from smetest to smecontribs, old versions are removed automatically<br />
<br />
cp smetest/package-name-version.rpm smecontribs/<br />
</li></ol><br />
<br />
{{Note box|Within a period of two hours the package should be moved to the smecontribs repository and be available as soon as the mirrors synchronize.}}<br />
<br />
===Workflow===<br />
Once the server successfully builds it will automatically be pulled on the next repo update run <br />
(40 past the even hours MDT). The package will either be put into the smedev (new package) or smetest (exist in higher repo) After verification the package is manually moved from smedev/smetest to smecontribs (for contribs) or smeupdates-testing (for packages in base)<br />
<br />
===Mailing Lists===<br />
Subscribe yourself to the [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist]. This is the place to discuss the development of the server and contribs. If you have other questions, not regarding development please use the [http://forums.contribs.org forums].<br />
<br />
Other lists exist to monitor bugs and the build system, UpdatesTeam + ...</div>
Byte
https://wiki.koozali.org/index.php?title=Category:Contrib&diff=8788
Category:Contrib
2008-03-28T23:11:40Z
<p>Byte: /* SME Server Contribs */</p>
<hr />
<div>{{Languages|:Category:Contrib}}<br />
===SME Server Contribs===<br />
SME Server contribs are software packages that are designed to add extra functionality to SME Server.<br />
<br />
To be listed on this page, the contrib should comply with these rules:<br />
* Be available in the smecontrib repository<br />
* Have a wiki page with install and usage instructions, following the template listed on the [[Category_talk:Contrib|talk page]].<br />
* Have a Bugzilla Contribs Component<br />
<br />
{{Note box|Please note that with the next major update set (expected early next week) any additional contribs you may have installed will give translation warnings/errors, this is because we have made major translation changes to incorporate many NEW languages (and more in the future we hope)<br />
<br />
If your contrib is in the smecontribs repository then we (and the community) will assist in translations and patches will be made available to bring their contribs to latest translation.<br />
<br />
But if your contrib is NOT in the smecontribs repository then we strongly advise you email:<br />
<br />
admin [at] contribs [dot] org<br />
<br />
and look in to with a view to getting your contrib in the smecontribs repository.<br />
}}<br />
<br />
For more information on releasing a contrib refer to the [[Releasing Contribs]] and [[:Package Modification]] pages.<br />
{{Note box|This is not a page where every contrib is listed extensively, just the best one or two of each type, the rest are linked at the bottom or listed in the appropriate category.}}<br />
<br />
A lot off contribs are available in the SME Contribs repository, to list the actual list of packages in the SME Contribs repository issue the following command:<br />
<br />
yum --disablerepo=* --enablerepo=smecontribs list available<br />
<br />
To install a contrib:<br />
<br />
yum --enablerepo=smecontribs install packagename<br />
<br />
===[[:Category:Administration|Administration]]===<br />
<br />
====[[:OCS Inventory Tools]]====<br />
<br />
Open Computer and Software Inventory Next Generation is an application designed to help a network or system administrator keep track of the computers configuration and software that are installed on the network.<br />
<br />
It is also able to detect all active devices on your network, such as switch, router, network printer and unattended devices. For each one, it stores MAC and IP addresses and allows you to classify them.<br />
<br />
Last, but not least, OCS Inventory NG includes package deployment feature on client computers. From the central management server, you can upload packages (software setup, commands or only files to store on client computers) which will be downloaded through HTTP/HTTPS and launched by agent on client computer. <br />
<br />
===[[:Category:Backup|Backup]]===<br />
====[[:Affa]]====<br />
<br />
The main purpose of this affa package is to make a SME 7 Server a dedicated backup box in a few minutes. Affa backs up as many SME servers as you like or any other servers which have sshd running and rsync installed. Once it is configured, Affa runs reliably unattended and sends warning messages in case of any errors.<br />
<br />
Affa is a command line tool for system administrators and is intentionally designed without a GUI. Therefore it can be efficiently managed on the console and over slow internet connections. <br />
<br />
===[[:Category:CMS|Content Management Systems]]===<br />
====[[:Moodle]]====<br />
<br />
Moodle is a course management system (CMS) A free, Open Source software package designed using sound pedagogical principles, to help educators create effective online learning communities.<br />
<br />
===[[:Category:Development Tools|Development Tools]]===<br />
<br />
<br />
===[[:Category:Groupware|Groupware]]===<br />
====[[:Egroupware|eGroupware]]====<br />
<br />
eGroupWare is a free enterprise ready groupware software for your network. It enables you to manage contacts, appointments, todos and many more for your whole business.<br />
<br />
eGroupWare is a groupware server. It comes with a native web-interface which allowes to access your data from any platform all over the planet. Moreover you also have the choice to access the eGroupWare server with your favorite groupware client (Kontact, Evolution, Outlook) and also with your mobile or PDA via SyncML. <br />
<br />
===[[:Category:Mail|Email Applications]]===<br />
====[http://dungog.net/wiki/Smeserver-vacation Vacation]====<br />
<br />
Setup an automatic 'out of office' email reply.<br />
<br />
===[[:Category:Webapps|Web Applications]]===<br />
====[[:SMF]]====<br />
<br />
Simple Machines Forum — SMF in short — is a free, professional grade software package that allows you to set up your own online community within minutes.<br />
<br />
Its powerful custom made template engine puts you in full control of the lay-out of your message board and with our unique SSI - or Server Side Includes - function you can let your forum and your website interact with each other.</div>
Byte
https://wiki.koozali.org/index.php?title=Package_Modification&diff=7866
Package Modification
2008-02-12T16:05:56Z
<p>Byte: /* Import cvs */</p>
<hr />
<div>===Introduction===<br />
SME Server code is stored in the CVS on http://www.sourceforge.net in two repositories:<br />
* [http://fisheye1.cenqua.com/browse/smeserver/ CVS SME Server] which holds the core packages of the SME Server<br />
* [http://fisheye1.cenqua.com/browse/smecontribs/ CVS SME Contribs] which holds the contribs packages<br />
<br />
This page is to help you make changes to the contribs packages stored on sourceforge. <br />
{{Note box|For now changes to the base are still made using mezzanine.}}<br />
<br />
===Set up===<br />
====Local environment====<br />
* We now use cvs without needing mezzanine, check you have it installed<br />
yum install cvs<br />
<br />
* Setup CVS to use ssh by creating /etc/profile.d/smebuild.sh with the following content<br />
<br />
# Developer environment<br />
# This gets symlinked into /etc/profile.d <br />
<br />
export CVS_RSH=ssh # tell CVS to use ssh<br />
<br />
# DO NOT set CVSROOT<br />
<br />
alias rm='rm -i'<br />
alias cp='cp -i --preserve=timestamps'<br />
alias mv='mv -i'<br />
You have to logout an login again to the console for changes to take effects.<br />
<br />
====Access to build system====<br />
Check updates/status on the build server: http://buildsys.contribs.org<br />
<br />
Ask admin@contribs.org for certificates, give the email address to use for notifications.<br />
yum install --enablerepo=smedev plague-client <br />
<br />
From now, do not use account "root" anymore. Use a dedicated dev account.<br />
Copy certificates and config file to ~/<br />
.plague-client.cfg<br />
.username.pem<br />
.contribs-upload-ca.pem<br />
.contribs-server-ca.pem<br />
<br />
Don't forget to set the proper privileges on the file<br />
chmod 600 .username.pem<br />
<br />
Check it's working<br />
plague-client list_builders<br />
<br />
Builders:<br />
------------------------------------------------------------------------------------------<br />
build64-1.contribs.org x86_64 amd64 ia32e noarch i386 i486 i586 i686 athlon available<br />
build32-1.contribs.org i386 i486 i586 i686 athlon noarch available<br />
<br />
====Sourceforge access====<br />
* SME Server code is stored in the CVS on http://SourceForge.net. To be able to work on your code in the SME Server CVS repository you need an account on SourceForge. With this account the development team can give you access to the CVS repository. More information can be found here:<br />
[http://sourceforge.net/docman/display_doc.php?docid=11123&group_id=1 B04: Registering a User Account]<br />
[http://sourceforge.net/docman/display_doc.php?docid=29894&group_id=1 E04: CVS (Version Control for Source Code)]<br />
[http://sourceforge.net/docs/F02/en/#top F02: SSH Key Generation and Usage]<br />
<br />
* After you have created your SourceForge account you can ask the development team to give you developer access to smecontribs. Create a bug in the Bug Tracker as usual.<br />
<br />
* Copy your local public SSH key to SourceForge https://sourceforge.net/account/editsshkeys.php <br />
<br />
* If local username is different to sf.net username edit ~/.ssh/config:<br />
<br />
Host smeserver.cvs.sourceforge.net<br />
User sfusername ''(without @shell.sf.net)''<br />
Host smecontribs.cvs.sourceforge.net<br />
User sfusername ''(without @shell.sf.net)''<br />
<br />
* Don't forget to set the proper privileges on the file<br />
<br />
chmod 600 ~/.ssh/config<br />
<br />
===Usage===<br />
====Import src.rpm====<br />
Email admin@contribs.org with the location of your rpm, it will be imported into the build system for you.<br />
<br />
====Import cvs====<br />
This is just cvs information, not source code.<br />
<br />
You can use ~/home/smeserver or whatever suits.<br />
<br />
mkdir ~/smeserver<br />
cd ~/smeserver<br />
cvs -z3 -d:ext:smeserver.cvs.sourceforge.net:/cvsroot/smeserver co -P rpms <br />
<br />
(for now changes to smeserver are still made with the mezzanine method, and updated manually by devs)<br />
<br />
mkdir ~/smecontribs<br />
cd ~/smecontribs <br />
cvs -z3 -d:ext:smecontribs.cvs.sourceforge.net:/cvsroot/smecontribs co -P rpms <br />
<br />
To refresh run the following from the rpms directory, or any lower directory with a CVS dir<br />
cvs update -dPA<br />
<br />
====Modify a package====<br />
Builders have rights to patch packages, tag, and build. <br />
If you need to upload new source tarballs or versions shad has to do that for now. Email them.<br />
Binary files are stored in a look-aside cache on shads box. CVS isn't great on binary files.<br />
<br />
Mezzanine, (mzsfget, mzclean, mzprep, mzpatch, mzbuild, mzput) have all be replaced with a new method.<br />
<br />
Create a bug at http://bugs.contribs.org against your contrib<br />
<br />
Change to work directory<br />
cd smecontribs/rpms/smeserver-foo/contribs7<br />
<br />
To prepare a tree<br />
cvs update -dPA [optional]<br />
make clean [optional]<br />
make prep<br />
<br />
Then switch to the tree and make modification.<br />
<br />
In the prepared dir copy a file you want to modify like so:<br />
<br />
cp 28UserManagerProxyPass 28UserManagerProxyPass.{patchname}<br />
<br />
Then modify the original file 28UserManagerProxyPass.<br />
To add new files touch the file.{patchname} so it is empty. (really empty = 0kb, some file manager don't!)<br />
<br />
Once you have all the files you want patched copied and changed then you can build the patch (from the contribs7 dir) with:<br />
make patch SUFFIX={patchname}<br />
It will build and add the patch for you. It should be named "name-version-{patchname}.patch"<br />
(man gendiff. That is what the makefile uses to generate the diff file.)<br />
<br />
Edit the spec<br />
nano -w smeserver-foo.spec<br />
<br />
#increase the release<br />
%define release 15<br />
<br />
#add the patch<br />
Patch2: smeserver-foo-1.2-widget.patch<br />
<br />
#update the changelog, include the bug number<br />
* Fri Jan 11 2008 John Smith <smith@foo.net> 1.2-15<br />
- fixed foo to create bar [SME 3470]<br />
<br />
#apply the patch in %setup<br />
%patch2 -p1<br />
<br />
Build the rpm locally to test, (note, this deletes the working tree!)<br />
make local <br />
<br />
Once you are satisfied and want to submit the package to the build server commit your changes. (Please use descriptive comments so that other developers are aware of what is happening. Comments will appear on the subject line of the commit email that get send to the other developers.)<br />
<br />
cvs commit -m 'msg'<br />
<br />
You can automate the addition of the comments in the spec file with the command 'clog'. {{Note box|You will need to be in the sme7, sme8, or contribs7 directory for this to work}}<br />
<br />
rm -f clog<br />
cvs commit -m "$(make clog)"<br />
<br />
Then tag all files as belonging to a particular build version<br />
make tag<br />
<br />
Then submit the request to the build server which will checkout the recently tagged version and build it in a chroot (mock) env.<br />
make build<br />
<br />
Key things are to always do "make tag" before "make build" <br />
<br />
Always ensure you are working with the latest version (cvs update -dPA)<br />
<br />
You and updatesteam will get an email on successfull build. <br />
Only you will get an email on failed build.<br />
<br />
CVS cheat sheet [[:Package_Modification/More cvs commands]]<br />
<br />
===Workflow===<br />
Once the server successfully builds it will automatically be pulled on the next repo update run <br />
(40 past the even hours MDT). The package will either be put into the smedev (new package) or smetest (exist in higher repo) After verification the package is manually moved from smedev/smetest to smecontribs (for contribs) or smeupdates-testing (for packages in base)<br />
<br />
===Mailing Lists===<br />
Subscribe yourself to the [http://lists.contribs.org/mailman/listinfo/devinfo devinfo mailinglist]. This is the place to discuss the development of the server and contribs. If you have other questions, not regarding development please use the [http://forums.contribs.org forums].<br />
<br />
Other lists exist to monitor bugs and the build system, UpdatesTeam + ...</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=7529
SME Server 8
2008-01-20T22:21:42Z
<p>Byte: </p>
<hr />
<div>==Status: Beta==<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good.<br />
<br />
See the Release Announcement for Beta1 http://forums.contribs.org/index.php?topic=39499.0<br />
<br />
http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ - 8.0 beta1 (based on CentOS 5.1)<br />
<br />
Please, please any issues report to our bug tracker under the SME Server 8 section.<br />
(especially with SME Server 8.0beta1 as this is an early beta release) <br />
<br />
Notes:<br />
- Also no contribs will be released for 8.0 until we get to the RC status.<br />
<br />
===New Install===<br />
Install with the CD, should work fine. If not report a bug.<br />
<br />
===Upgrade paths===<br />
<br />
====With CD====<br />
Should work fine. If not report a bug.<br />
<br />
[[bugzilla:3726]]<br />
<br />
====With Yum====<br />
<br />
=====Setting up your SME Server 8 repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://mirror.contribs.org/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
expand-template /etc/yum.conf<br />
<br />
Then run yum command <br />
yum upgrade --disable '*' --enable sme8os<br />
<br />
Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
<br />
=====If your running SME Server 7.x (clean install & excluding 7.3)=====<br />
<br />
Upgrading via yum if you have SME Server 7.x clean (Excluding 7.3) install can now be done, you will first encounter this error:<br />
<br />
--> Running transaction check<br />
--> Processing Dependency: libstartup-notification-1.so.0 for package: libwnck<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Processing Dependency: startup-notification >= 0.5 for package: libwnck<br />
--> Restarting Dependency Resolution with new changes.<br />
--> Populating transaction set with selected packages. Please wait.<br />
---> Downloading header for startup-notification to pack into transaction set.<br />
startup-notification-0.8- 100% |=========================| 5.0 kB 00:00<br />
---> Package startup-notification.i386 0:0.8-4.1 set to be updated<br />
--> Running transaction check<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
================================================================<br />
No new rpms were installed. No additional commands are required.<br />
================================================================<br />
[root@example ~]#<br />
<br />
You will need to download from the [http://mirror.contribs.org/smeserver/releases/7.3/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm yum-metadata-parser] and manually install the package as below:<br />
<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
<br />
Then type from command line:<br />
<br />
yum clean all<br />
<br />
followed by:<br />
<br />
yum upgrade --disable "*" --enable smeos<br />
<br />
Now you should be on your way to upgrading to SME Server 8beta :)<br />
<br />
=====If your running SME Server 7.3 (clean install)=====<br />
<br />
<br />
If you have SME Server 7.3 clean install you will be able to upgrade to SME Server 8beta without any issues.<br />
<br />
You should only do this if you are interested in helping with development/testing and of course if you find a bug remember to report to our bug tracker.<br />
<br />
<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=7528
SME Server 8
2008-01-20T22:17:31Z
<p>Byte: /* With Yum */</p>
<hr />
<div>==Status: Beta==<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good.<br />
<br />
See the Release Announcement for Beta1 http://forums.contribs.org/index.php?topic=39499.0<br />
<br />
http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ - 8.0 beta1 (based on CentOS 5.1)<br />
<br />
Please, please any issues report to our bug tracker under the SME Server 8 section.<br />
(especially with SME Server 8.0beta1 as this is an early beta release) <br />
<br />
Notes:<br />
- Also no contribs will be released for 8.0 until we get to the RC status.<br />
<br />
===New Install===<br />
Install with the CD, should work fine. If not report a bug.<br />
<br />
===Upgrade paths===<br />
<br />
====With CD====<br />
Should work fine. If not report a bug.<br />
<br />
[[bugzilla:3726]]<br />
<br />
====With Yum====<br />
=====If your running SME Server 7.x (clean install & excluding 7.3)=====<br />
<br />
Upgrading via yum if you have SME Server 7.x clean (Excluding 7.3) install can now be done, you will first encounter this error:<br />
<br />
--> Running transaction check<br />
--> Processing Dependency: libstartup-notification-1.so.0 for package: libwnck<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Processing Dependency: startup-notification >= 0.5 for package: libwnck<br />
--> Restarting Dependency Resolution with new changes.<br />
--> Populating transaction set with selected packages. Please wait.<br />
---> Downloading header for startup-notification to pack into transaction set.<br />
startup-notification-0.8- 100% |=========================| 5.0 kB 00:00<br />
---> Package startup-notification.i386 0:0.8-4.1 set to be updated<br />
--> Running transaction check<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
================================================================<br />
No new rpms were installed. No additional commands are required.<br />
================================================================<br />
[root@example ~]#<br />
<br />
You will need to download from the [http://mirror.contribs.org/smeserver/releases/7.3/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm yum-metadata-parser] and manually install the package as below:<br />
<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
<br />
Then type from command line:<br />
<br />
yum clean all<br />
<br />
followed by:<br />
<br />
yum upgrade --disable "*" --enable smeos<br />
<br />
Now you should be on your way to upgrading to SME Server 8beta :)<br />
<br />
=====If your running SME Server 7.3 (clean install)=====<br />
<br />
<br />
If you have SME Server 7.3 clean install you will be able to upgrade to SME Server 8beta without any issues.<br />
<br />
You should only do this if you are interested in helping with development/testing and of course if you find a bug remember to report to our bug tracker.<br />
<br />
=====sme8os repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://mirror.contribs.org/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
expand-template /etc/yum.conf<br />
<br />
Then run yum command <br />
yum upgrade --disable '*' --enable sme8os<br />
<br />
Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=7525
SME Server 8
2008-01-20T17:18:39Z
<p>Byte: /* Status: Beta */</p>
<hr />
<div>==Status: Beta==<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good.<br />
<br />
See the Release Announcement for Beta1 http://forums.contribs.org/index.php?topic=39499.0<br />
<br />
http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ - 8.0 beta1 (based on CentOS 5.1)<br />
<br />
Please, please any issues report to our bug tracker under the SME Server 8 section.<br />
(especially with SME Server 8.0beta1 as this is an early beta release) <br />
<br />
Notes:<br />
- Also no contribs will be released for 8.0 until we get to the RC status.<br />
<br />
===New Install===<br />
Install with the CD, should work fine. If not report a bug.<br />
<br />
===Upgrade paths===<br />
<br />
====With CD====<br />
Should work fine. If not report a bug.<br />
<br />
[[bugzilla:3726]]<br />
<br />
====With Yum====<br />
Upgrading via yum if you have SME Server 7.x clean (Excluding 7.3) install can now be done, you will first encounter this error:<br />
<br />
--> Running transaction check<br />
--> Processing Dependency: libstartup-notification-1.so.0 for package: libwnck<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Processing Dependency: startup-notification >= 0.5 for package: libwnck<br />
--> Restarting Dependency Resolution with new changes.<br />
--> Populating transaction set with selected packages. Please wait.<br />
---> Downloading header for startup-notification to pack into transaction set.<br />
startup-notification-0.8- 100% |=========================| 5.0 kB 00:00<br />
---> Package startup-notification.i386 0:0.8-4.1 set to be updated<br />
--> Running transaction check<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
================================================================<br />
No new rpms were installed. No additional commands are required.<br />
================================================================<br />
[root@example ~]#<br />
<br />
You will need to download from the [http://mirror.contribs.org/smeserver/releases/7.3/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm yum-metadata-parser] and manually install the package as below:<br />
<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
<br />
Then type from command line:<br />
<br />
yum clean all<br />
<br />
followed by:<br />
<br />
yum upgrade --disable "*" --enable smeos<br />
<br />
Now you should be on your way to upgrading to SME Server 8betax :)<br />
<br />
If you have SME Server 7.3 clean install you will be able to upgrade to SME Server 8betax without any issues.<br />
<br />
You should only do this if you are interested in helping with development/testing and of course if you find a bug remember to report to our bug tracker.<br />
<br />
=====sme8os repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://mirror.contribs.org/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
expand-template /etc/yum.conf<br />
<br />
Then run yum command <br />
yum upgrade --disable '*' --enable sme8os<br />
<br />
Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=7524
SME Server 8
2008-01-20T17:16:18Z
<p>Byte: /* With Yum */</p>
<hr />
<div>==Status: Beta==<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good.<br />
<br />
See the Release Announcement for Beta1 http://forums.contribs.org/index.php?topic=39499.0<br />
<br />
http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ - 8.0 beta1 (based on CentOS 5.1)<br />
<br />
Please, please any issues report to our bug tracker under the SME Server 8 section.<br />
(especially with SME Server 8.0beta1 as this is an early beta release) <br />
<br />
Notes:<br />
- Upgrades from 7 to 8 are still being worked on and might not work correctly yet.<br />
- Also no contribs will be released for 8.0 until we get to the RC status.<br />
<br />
===New Install===<br />
Install with the CD, should work fine. If not report a bug.<br />
<br />
===Upgrade paths===<br />
<br />
====With CD====<br />
Should work fine. If not report a bug.<br />
<br />
[[bugzilla:3726]]<br />
<br />
====With Yum====<br />
Upgrading via yum if you have SME Server 7.x clean (Excluding 7.3) install can now be done, you will first encounter this error:<br />
<br />
--> Running transaction check<br />
--> Processing Dependency: libstartup-notification-1.so.0 for package: libwnck<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Processing Dependency: startup-notification >= 0.5 for package: libwnck<br />
--> Restarting Dependency Resolution with new changes.<br />
--> Populating transaction set with selected packages. Please wait.<br />
---> Downloading header for startup-notification to pack into transaction set.<br />
startup-notification-0.8- 100% |=========================| 5.0 kB 00:00<br />
---> Package startup-notification.i386 0:0.8-4.1 set to be updated<br />
--> Running transaction check<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
================================================================<br />
No new rpms were installed. No additional commands are required.<br />
================================================================<br />
[root@example ~]#<br />
<br />
You will need to download from the [http://mirror.contribs.org/smeserver/releases/7.3/smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm yum-metadata-parser] and manually install the package as below:<br />
<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
<br />
Then type from command line:<br />
<br />
yum clean all<br />
<br />
followed by:<br />
<br />
yum upgrade --disable "*" --enable smeos<br />
<br />
Now you should be on your way to upgrading to SME Server 8betax :)<br />
<br />
If you have SME Server 7.3 clean install you will be able to upgrade to SME Server 8betax without any issues.<br />
<br />
You should only do this if you are interested in helping with development/testing and of course if you find a bug remember to report to our bug tracker.<br />
<br />
=====sme8os repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://mirror.contribs.org/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
expand-template /etc/yum.conf<br />
<br />
Then run yum command <br />
yum upgrade --disable '*' --enable sme8os<br />
<br />
Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server_8&diff=7523
SME Server 8
2008-01-20T17:15:23Z
<p>Byte: /* With Yum */</p>
<hr />
<div>==Status: Beta==<br />
<br />
SME Server Version 8 will be the next major version of SME Server, and will involve upgrading the base to CentOS 5. We are just in the early stages of development, but so far things look good.<br />
<br />
See the Release Announcement for Beta1 http://forums.contribs.org/index.php?topic=39499.0<br />
<br />
http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/ - 8.0 beta1 (based on CentOS 5.1)<br />
<br />
Please, please any issues report to our bug tracker under the SME Server 8 section.<br />
(especially with SME Server 8.0beta1 as this is an early beta release) <br />
<br />
Notes:<br />
- Upgrades from 7 to 8 are still being worked on and might not work correctly yet.<br />
- Also no contribs will be released for 8.0 until we get to the RC status.<br />
<br />
===New Install===<br />
Install with the CD, should work fine. If not report a bug.<br />
<br />
===Upgrade paths===<br />
<br />
====With CD====<br />
Should work fine. If not report a bug.<br />
<br />
[[bugzilla:3726]]<br />
<br />
====With Yum====<br />
Upgrading via yum if you have SME Server 7.x clean (Excluding 7.3) install can now be done, you will first encounter this error:<br />
<br />
--> Running transaction check<br />
--> Processing Dependency: libstartup-notification-1.so.0 for package: libwnck<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Processing Dependency: startup-notification >= 0.5 for package: libwnck<br />
--> Restarting Dependency Resolution with new changes.<br />
--> Populating transaction set with selected packages. Please wait.<br />
---> Downloading header for startup-notification to pack into transaction set.<br />
startup-notification-0.8- 100% |=========================| 5.0 kB 00:00<br />
---> Package startup-notification.i386 0:0.8-4.1 set to be updated<br />
--> Running transaction check<br />
--> Processing Dependency: yum-metadata-parser for package: yum<br />
--> Finished Dependency Resolution<br />
Error: Missing Dependency: yum-metadata-parser is needed by package yum<br />
================================================================<br />
No new rpms were installed. No additional commands are required.<br />
================================================================<br />
[root@example ~]#<br />
<br />
You will need to download from the [smeos/i386/SME/RPMS/yum-metadata-parser-1.0-8.el4.centos.i386.rpm yum-metadata-parser] and manually install the package as below:<br />
<br />
rpm -Uvh --oldpackage yum-metadata-parser-1.0-8.el4.centos.i386.rpm<br />
<br />
Then type from command line:<br />
<br />
yum clean all<br />
<br />
followed by:<br />
<br />
yum upgrade --disable "*" --enable smeos<br />
<br />
Now you should be on your way to upgrading to SME Server 8betax :)<br />
<br />
If you have SME Server 7.3 clean install you will be able to upgrade to SME Server 8betax without any issues.<br />
<br />
You should only do this if you are interested in helping with development/testing and of course if you find a bug remember to report to our bug tracker.<br />
<br />
=====sme8os repository=====<br />
Setup with the following yum repositories...<br />
<br />
/sbin/e-smith/db yum_repositories set sme8os repository \<br />
Name 'SME Server 8 - smeos' \<br />
BaseURL 'http://mirror.contribs.org/smeserver/releases/testing/8/smeos/i386/' \<br />
EnableGroups yes \<br />
GPGCheck no \<br />
Visible yes \<br />
status enabled<br />
<br />
Expand your yum.conf...<br />
expand-template /etc/yum.conf<br />
<br />
Then run yum command <br />
yum upgrade --disable '*' --enable sme8os<br />
<br />
Once completed issue<br />
signal-event post-upgrade;signal-event reboot<br />
<br />
If you have any bug issues with upgrading please open a new SME Server 8.x {{BugzillaFileBug|product=SME%20Server%20Release%208.X|component=|comment=|summary=|title=file a bug here}}<br />
<br />
===Major Changes===<br />
<br />
* CentOS 5 has dropped support for i586 and therefore SME Server 8 will not work on i586 hardware. See [[bugzilla:2845]]</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server:7.3&diff=7206
SME Server:7.3
2008-01-01T22:28:32Z
<p>Byte: /* SME Server 7.3 Release Notes */</p>
<hr />
<div>==Status: Gold==<br />
<br />
==SME Server 7.3 Release Notes==<br />
<br />
<br />
January 1 2008<br />
<br />
The SME Server development team is pleased to announce the release of<br />
SME Server 7.3. This release is based on CentOS 4.6 and all packages<br />
have been updated to the latest releases.<br />
<br />
<br />
The release should be obtained from your closest mirror, see http://wiki.contribs.org/SME_Server:Download<br />
<br />
<br />
All SME Server users should upgrade to this release.<br />
<br />
<br />
<br />
Bug reports and reports of potential bugs should be raised<br />
in the bug tracker (and only there, please);<br />
<br />
http://bugs.contribs.org/<br />
<br />
<br />
===Please Note===<br />
-----------<br />
It may take up to 48 hours for mirrors to finish syncing,<br />
during this time you may experience problems.<br />
<br />
<br />
===About SME Server===<br />
<br />
<br />
SME Server is the leading Linux distribution for small and medium<br />
enterprises. SME Server is brought to you by SME Server, Inc.<br />
( http://www.smeserver.org/ ), a non-profit corporation that exists to<br />
provide marketing and legal support for SME Server.<br />
<br />
SME Server is freely available under the GNU General Public License<br />
and is only possible through the efforts of the SME Server community.<br />
However, the availability and quality of SME Server is dependent on<br />
meeting our expenses, such as hosting costs, server hardware, etc.<br />
<br />
As such, we ask for a small donation to offset costs and fund further<br />
development.<br />
<br />
Please visit '''http://www.smeserver.org/donate/''' to donate.<br />
<br />
===Thanks===<br />
------<br />
The development team would like to thank all of those involved in<br />
this release. However, this distribution cannot continue with the<br />
current level of support. More people are required to help with<br />
bug triage and verification testing.<br />
<br />
<br />
This release contains many new features, all released updates for<br />
SME Server 7.2 and fixes for many reported problems. Upgrades<br />
will be available by CD, the Software Installer and command line.<br />
<br />
==Upgrades==<br />
<br />
<br />
* Always perform a backup prior to major system upgrades<br />
<br />
* An upgrade will preserve the existing data<br />
<br />
<br />
==Changes in this release==<br />
<br />
<br />
<br />
===Installer Options===<br />
-----------------<br />
* Using "sme multipart" boot parameter now enables quotas on all LVM's see bug 3651 on how to create your quota files<br />
<br />
<br />
===Other mail system changes===<br />
-------------------------<br />
* Support for disconnect option in rhsbl plugin<br />
<br />
* Support for disconnect immediately if dnsbl plugin rejects recipient addresses<br />
<br />
* Newer version of ipsvd to resolve a few Thunderbird issues<br />
<br />
* Support for configurable timeouts which by default is set to two minutes<br />
<br />
<br />
===Console===<br />
-------<br />
* Now able to remove Corporate DNS setting<br />
* Raid reconstruction now finishes after using "sme nolvm" passed at install time<br />
<br />
<br />
===Backups===<br />
-------<br />
* Ability to use console restore with CD or DVD recordable media<br />
<br />
* Remove smbpasswd file prior to restore<br />
<br />
<br />
===Localisation===<br />
------------<br />
* The fr-fr browser language is now supported<br />
<br />
* Italian translation minor update<br />
<br />
<br />
===Software Installer===<br />
------------------<br />
* The voxteneo.com and fullnet.co.uk mirrors has been added as a mirror location. Many thanks to all of our mirrors<br />
<br />
* Removed planetmirror mirror due to being unstable for a number of months<br />
<br />
* Added smecontribs repository to smeserver<br />
<br />
<br />
===Webmail===<br />
-------<br />
* Horde, imp, turbo and ingo have been updated to the latest versions<br />
<br />
<br />
===Server manager===<br />
--------------<br />
* Updated wording in Server manager > proxy to be correct when running in serveronly mode<br />
<br />
* Now able to remove settings in the Corporate DNS panel<br />
<br />
* Make qpsmtpd/state visible in the view log files<br />
<br />
* Convert squid timestamp in view log files<br />
<br />
* Since we moved to session-based login changing admin password does no longer invalidate access to server manager<br />
<br />
* Added support if you use port-forwarding with an external dynamic ip address<br />
<br />
<br />
===Other fixes and updates===<br />
-----------------------<br />
* More changes have been made in preparation for migration to CentOS5<br />
<br />
* Various samba issues fixed with new samba 3.0.25b package<br />
<br />
* Smartd is disabled by default but has built in templates to enable<br />
<br />
* Import of spamassassin keys are now processed correctly<br />
<br />
* Fixed various log noise issues<br />
<br />
* Allow root to be key based login only<br />
<br />
* Increased dnscache forwarder cache size<br />
<br />
* Freshclam permissions now corrected<br />
<br />
* Unwanted symlinks in httpd log directory no longer appear<br />
<br />
* Added WPAD feature in DHCP<br />
<br />
* Fixed various perl issues<br />
<br />
* Using long email address now stops regeneration email every day<br />
<br /><br />
<br />
==General features==<br />
<br />
* Based on CentOS 4.6 and all available updates<br />
<br /><br />
<br />
==There are a few differences from previous releases <=7.2==<br />
<br /><br />
<br />
===After installing for the very first time:===<br />
-----------------------------------------<br />
* First night you should receive an email from cron about sa_updates.<br />
<br />
* First night you should receive a large email saying a bunch of groups/users were removed/added (rkhunter email notification).<br />
<br />
* Any time you change users/groups you will receive an email the next day about those changes (rkhunter email notification).<br />
<br />
<br />
===Taking the upgrade path from a 7.x to 7.3===<br />
-----------------------------------------<br />
* First night you may receive an email from cron about sa_updates<br />
<br />
* First night you may receive a email saying missing passwd/group files (rkhunter email notification).<br />
<br />
<br />
$Id: README.txt,v 1.20 2008/01/01 17:18:13 slords Exp $</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server:Download&diff=7204
SME Server:Download
2008-01-01T22:24:31Z
<p>Byte: </p>
<hr />
<div>This release, 7.3 is based on CentOS 4.6 Our last stable release was SME Server Release 7.2, see the Main Page for details of incremental updates available with yum. <br />
<br />
The SME Server ISO CD image is available to [http://www.tuxdistro.com/browse.php?cat=318 download as a Torrent]<br />
<br />
Alternatively, please download the CD image at your closest mirror site.<br />
<br />
Hosting of SME Server releases and contribs has been generously been provided by the following:<br />
<br />
'''North America:'''<br /> <br />
[http://distro.ibiblio.org/pub/linux/distributions/smeserver/releases/7/iso ibiblio.org - USA]<br /><br />
[http://www.gtlib.gatech.edu/pub/linux/distributions/smeserver/releases/7/iso ftp.gtlib.gatech.edu - USA]<br /><br />
<br />
'''Asia/Pacific:'''<br /> <br />
[http://mirror.pacific.net.au/linux/smeserver/releases/7/iso Pacific.net.au - Australia]<br /> <br />
<br />
'''Europe:'''<br /> <br />
[http://sme-mirror.voxteneo.com/releases/7/iso Voxteneo.com - France ]<br /><br />
[http://ftp.nluug.nl/os/Linux/distr/smeserver/releases/7/iso NLUUG.nl - Netherlands]<br /> <br />
[http://ftp.surfnet.nl/ftp/pub/os/Linux/distr/smeserver/releases/7/iso Surfnet.nl - Netherlands]<br /> <br />
[http://smemirror.fullnet.co.uk/releases/7/iso fullnet.co.uk - United Kingdom]<br />
<br />
<br />
'''Mirrors'''<br /> <br />
Further information on [http://wiki.contribs.org/Mirrors Mirrors]<br />
<br />
'''Zsync'''<br /><br />
Downloads a file over HTTP. zsync uses a control file to determine whether any blocks in the file are already known to the downloader, and only downloads the new blocks. see also '''man zsync''' and the -i option<br />
yum install zsync --enablerepo=dag<br />
zsync http://mirror.contribs.org/smeserver/releases/testing/8.0/iso/i386/smeserver-8.0beta1-i386.iso.zsync<br />
<br />
'''Updates:'''<br /> <br />
Upgrading to 7.x from 6.x - Upgrades from unmodified versions of SME 6.0.1 and 6.5RC1 to SME 7 is supported. If you have modified your server by installing contribs or have used any unsupported 'upgrade' scripts, you may have issues and should consider removing any incompatible contribs before upgrading.<br />
<br />
See http://wiki.contribs.org/Updating_to_SME_7.2<br />
<br />
'''Support:'''<br /> If you have questions about your download or installation, feel free to make use of the contribs.org forums. The forums are available for questions, suggestions, and general comments. You may search and find the answer to your question there.</div>
Byte
https://wiki.koozali.org/index.php?title=Main_Page&diff=7203
Main Page
2008-01-01T22:23:30Z
<p>Byte: </p>
<hr />
<div>__NOTOC__<br />
{{Languages}}<br />
<br />
{| style="border: solid 1px; border-color:lightgray; margin: oem; background-color: #ffff99;" width=100% cellpadding=5 cellspacing=5<br />
| width=50% align=left valign=top | <B>SME Server Current Release:</B><br />
SME Server 7.3 released on 1st January 2008. <br />
<br>See [http://forums.contribs.org/index.php?topic=39541.0 this forum thread] by the development team and [[Bugzilla:3639]] for details<br />
| align=left valign=top | <B>Development Status:</B><br>SME Server 8.0 - [[:SME_Server_8| Wiki]] - [[bugzilla:3640]]<br />
|}<br />
<br />
{| cellpadding=5 cellspacing=5<br />
|-<br />
| valign=top | '''Welcome to the information and documentation wiki for SME Server'''<br />
<br />
We're here to provide collaborative documentation of the SME Server project. SME Server is a leading distribution for small and medium enterprises. It stands apart from the competition by shipping with most common functionality preconfigured and features a number of popular additional enhancements in the form of downloadable 'contributions'. It is published under the GPL license and while freely available, a small [http://www.smeserver.org/donate donation] is requested.<br />
<br />
<B>Quick Links</B><br />
{|<br />
|-<br />
|{{Click || image=Help.png | link=Help:Contents | width=22px | height=22px }}<br />
|Find '''[[Help:Contents|help]]''' with reading and editing the Wiki<br />
|}<br />
| <br />
|}<br />
<br />
:...and don't forget all the navigation links in the sidebar to the left.<br />
<br />
== Documentation==<br />
{| width=100%<br />
|<br />
{| cellspacing=5 cellpadding=5 border=0 width=100%<br />
<br />
|width=48|{{Click || image=Man.png | link=SME_Server:Documentation | width=48px | height=48px }}<br />
|'''[[SME_Server:Documentation|SME Server Manuals]]'''<br />
[[:SME_Server:Documentation:Administration_Manual|Administration]] <br /><br />
[[:SME_Server:Documentation:User_Manual|User]] <br /><br />
[[:SME_Server:Documentation:Developers_Manual|Developer]]<br />
<br />
|<br />
|width=48|{{Click || image=Kdict.png | link=:SME_Server:Documentation | width=48px | height=48px }}<br />
|'''[[:SME_Server:Documentation|Additional Documentation]]'''<br />
[[:SME_Server:Documentation:FAQ|FAQ's]] <br /><br />
[[:Category:Howto|HowTo's]]<br />
<br />
|-<br />
|width=48|{{Click || image=Blockdevice.png | link=:Category:Contrib | width=48px | height=48px }}<br />
|'''[[:Category:Contrib|Contribs]]'''<br><small>Individual SME Server Contribs<br />
|width=48|<br />
<br />
|}<br />
| width=220 valign=top | {{Template:Featured_Articles}}<br />
|}<br />
<br />
== Support ==<br />
<br />
* [[:SME_Server:Documentation |Documentation]]:<br />
The Wiki documentation is the primary source of information for SME Server.<br />
<br />
* [http://forums.contribs.org Forums]:<br />
Use the forums if you want advice how to do something not covered in the wiki <br><br />
Post to the forums if you found or did something, and you think other people might find it interesting<br />
<br />
* [http://bugs.contribs.org Bugzilla]:<br />
Raise a bug if you tried to do something covered in the wiki and it didn't work. <br><br />
For more information on Bugzilla see the [[:Bugzilla Help]] page.<br />
<br />
== News ==<br />
<br />
{{News}}</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server:7.3&diff=7200
SME Server:7.3
2008-01-01T19:28:20Z
<p>Byte: /* SME Server 7.3 Release Notes */</p>
<hr />
<div>==Status: Gold==<br />
<br />
==SME Server 7.3 Release Notes==<br />
<br />
<br />
January 1 2008<br />
<br />
The SME Server development team is pleased to announce the release of<br />
SME Server 7.3. This release is based on CentOS 4.6 and all packages<br />
have been updated to the latest releases.<br />
<br />
<br />
The release should be obtained from your closest mirror, see http://wiki.contribs.org/SME_Server:Download<br />
<br />
<br />
All SME Server users should upgrade to this release.<br />
<br />
<br />
<br />
Bug reports and reports of potential bugs should be raised<br />
in the bug tracker (and only there, please);<br />
<br />
http://bugs.contribs.org/<br />
<br />
<br />
===About SME Server===<br />
<br />
<br />
SME Server is the leading Linux distribution for small and medium<br />
enterprises. SME Server is brought to you by SME Server, Inc.<br />
( http://www.smeserver.org/ ), a non-profit corporation that exists to<br />
provide marketing and legal support for SME Server.<br />
<br />
SME Server is freely available under the GNU General Public License<br />
and is only possible through the efforts of the SME Server community.<br />
However, the availability and quality of SME Server is dependent on<br />
meeting our expenses, such as hosting costs, server hardware, etc.<br />
<br />
As such, we ask for a small donation to offset costs and fund further<br />
development.<br />
<br />
Please visit '''http://www.smeserver.org/donate/''' to donate.<br />
<br />
===Thanks===<br />
------<br />
The development team would like to thank all of those involved in<br />
this release. However, this distribution cannot continue with the<br />
current level of support. More people are required to help with<br />
bug triage and verification testing.<br />
<br />
<br />
This release contains many new features, all released updates for<br />
SME Server 7.2 and fixes for many reported problems. Upgrades<br />
will be available by CD, the Software Installer and command line.<br />
<br />
==Upgrades==<br />
<br />
<br />
* Always perform a backup prior to major system upgrades<br />
<br />
* An upgrade will preserve the existing data<br />
<br />
<br />
==Changes in this release==<br />
<br />
<br />
<br />
===Installer Options===<br />
-----------------<br />
* Using "sme multipart" boot parameter now enables quotas on all LVM's see bug 3651 on how to create your quota files<br />
<br />
<br />
===Other mail system changes===<br />
-------------------------<br />
* Support for disconnect option in rhsbl plugin<br />
<br />
* Support for disconnect immediately if dnsbl plugin rejects recipient addresses<br />
<br />
* Newer version of ipsvd to resolve a few Thunderbird issues<br />
<br />
* Support for configurable timeouts which by default is set to two minutes<br />
<br />
<br />
===Console===<br />
-------<br />
* Now able to remove Corporate DNS setting<br />
* Raid reconstruction now finishes after using "sme nolvm" passed at install time<br />
<br />
<br />
===Backups===<br />
-------<br />
* Ability to use console restore with CD or DVD recordable media<br />
<br />
* Remove smbpasswd file prior to restore<br />
<br />
<br />
===Localisation===<br />
------------<br />
* The fr-fr browser language is now supported<br />
<br />
* Italian translation minor update<br />
<br />
<br />
===Software Installer===<br />
------------------<br />
* The voxteneo.com and fullnet.co.uk mirrors has been added as a mirror location. Many thanks to all of our mirrors<br />
<br />
* Removed planetmirror mirror due to being unstable for a number of months<br />
<br />
* Added smecontribs repository to smeserver<br />
<br />
<br />
===Webmail===<br />
-------<br />
* Horde, imp, turbo and ingo have been updated to the latest versions<br />
<br />
<br />
===Server manager===<br />
--------------<br />
* Updated wording in Server manager > proxy to be correct when running in serveronly mode<br />
<br />
* Now able to remove settings in the Corporate DNS panel<br />
<br />
* Make qpsmtpd/state visible in the view log files<br />
<br />
* Convert squid timestamp in view log files<br />
<br />
* Since we moved to session-based login changing admin password does no longer invalidate access to server manager<br />
<br />
* Added support if you use port-forwarding with an external dynamic ip address<br />
<br />
<br />
===Other fixes and updates===<br />
-----------------------<br />
* More changes have been made in preparation for migration to CentOS5<br />
<br />
* Various samba issues fixed with new samba 3.0.25b package<br />
<br />
* Smartd is disabled by default but has built in templates to enable<br />
<br />
* Import of spamassassin keys are now processed correctly<br />
<br />
* Fixed various log noise issues<br />
<br />
* Allow root to be key based login only<br />
<br />
* Increased dnscache forwarder cache size<br />
<br />
* Freshclam permissions now corrected<br />
<br />
* Unwanted symlinks in httpd log directory no longer appear<br />
<br />
* Added WPAD feature in DHCP<br />
<br />
* Fixed various perl issues<br />
<br />
* Using long email address now stops regeneration email every day<br />
<br /><br />
<br />
==General features==<br />
<br />
* Based on CentOS 4.6 and all available updates<br />
<br /><br />
<br />
==There are a few differnces from previous releases <=7.2==<br />
<br /><br />
<br />
===After installing for the very first time:===<br />
-----------------------------------------<br />
* First night you should receive an email from cron about sa_updates.<br />
<br />
* First night you should receive a large email saying a bunch of groups/users were removed/added (rkhunter email notification).<br />
<br />
* Any time you change users/groups you will receive an email the next day about those changes (rkhunter email notification).<br />
<br />
<br />
===Taking the upgrade path from a 7.x to 7.3===<br />
-----------------------------------------<br />
* First night you may receive an email from cron about sa_updates<br />
<br />
* First night you may receive a email saying missing passwd/group files (rkhunter email notification).<br />
<br />
<br />
$Id: README.txt,v 1.20 2008/01/01 17:18:13 slords Exp $</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server:7.3&diff=7199
SME Server:7.3
2008-01-01T19:12:39Z
<p>Byte: /* About SME Server */</p>
<hr />
<div>==Status: Gold==<br />
<br />
==SME Server 7.3 Release Notes==<br />
<br />
<br />
January 1 2008<br />
<br />
The SME Server development team is pleased to announce the release of<br />
SME Server 7.3. This release is based on CentOS 4.6 and all packages<br />
have been updated to the latest releases.<br />
<br />
<br />
All SME Server users should upgrade to this release.<br />
<br />
<br />
Bug reports and reports of potential bugs should be raised<br />
in the bug tracker (and only there, please);<br />
<br />
http://bugs.contribs.org/<br />
<br />
<br />
===About SME Server===<br />
<br />
<br />
SME Server is the leading Linux distribution for small and medium<br />
enterprises. SME Server is brought to you by SME Server, Inc.<br />
( http://www.smeserver.org/ ), a non-profit corporation that exists to<br />
provide marketing and legal support for SME Server.<br />
<br />
SME Server is freely available under the GNU General Public License<br />
and is only possible through the efforts of the SME Server community.<br />
However, the availability and quality of SME Server is dependent on<br />
meeting our expenses, such as hosting costs, server hardware, etc.<br />
<br />
As such, we ask for a small donation to offset costs and fund further<br />
development.<br />
<br />
Please visit '''http://www.smeserver.org/donate/''' to donate.<br />
<br />
===Thanks===<br />
------<br />
The development team would like to thank all of those involved in<br />
this release. However, this distribution cannot continue with the<br />
current level of support. More people are required to help with<br />
bug triage and verification testing.<br />
<br />
<br />
This release contains many new features, all released updates for<br />
SME Server 7.2 and fixes for many reported problems. Upgrades<br />
will be available by CD, the Software Installer and command line.<br />
<br />
<br />
==Upgrades==<br />
<br />
<br />
* Always perform a backup prior to major system upgrades<br />
<br />
* An upgrade will preserve the existing data<br />
<br />
<br />
==Changes in this release==<br />
<br />
<br />
<br />
===Installer Options===<br />
-----------------<br />
* Using "sme multipart" boot parameter now enables quotas on all LVM's see bug 3651 on how to create your quota files<br />
<br />
<br />
===Other mail system changes===<br />
-------------------------<br />
* Support for disconnect option in rhsbl plugin<br />
<br />
* Support for disconnect immediately if dnsbl plugin rejects recipient addresses<br />
<br />
* Newer version of ipsvd to resolve a few Thunderbird issues<br />
<br />
* Support for configurable timeouts which by default is set to two minutes<br />
<br />
<br />
===Console===<br />
-------<br />
* Now able to remove Corporate DNS setting<br />
* Raid reconstruction now finishes after using "sme nolvm" passed at install time<br />
<br />
<br />
===Backups===<br />
-------<br />
* Ability to use console restore with CD or DVD recordable media<br />
<br />
* Remove smbpasswd file prior to restore<br />
<br />
<br />
===Localisation===<br />
------------<br />
* The fr-fr browser language is now supported<br />
<br />
* Italian translation minor update<br />
<br />
<br />
===Software Installer===<br />
------------------<br />
* The voxteneo.com and fullnet.co.uk mirrors has been added as a mirror location. Many thanks to all of our mirrors<br />
<br />
* Removed planetmirror mirror due to being unstable for a number of months<br />
<br />
* Added smecontribs repository to smeserver<br />
<br />
<br />
===Webmail===<br />
-------<br />
* Horde, imp, turbo and ingo have been updated to the latest versions<br />
<br />
<br />
===Server manager===<br />
--------------<br />
* Updated wording in Server manager > proxy to be correct when running in serveronly mode<br />
<br />
* Now able to remove settings in the Corporate DNS panel<br />
<br />
* Make qpsmtpd/state visible in the view log files<br />
<br />
* Convert squid timestamp in view log files<br />
<br />
* Since we moved to session-based login changing admin password does no longer invalidate access to server manager<br />
<br />
* Added support if you use port-forwarding with an external dynamic ip address<br />
<br />
<br />
===Other fixes and updates===<br />
-----------------------<br />
* More changes have been made in preparation for migration to CentOS5<br />
<br />
* Various samba issues fixed with new samba 3.0.25b package<br />
<br />
* Smartd is disabled by default but has built in templates to enable<br />
<br />
* Import of spamassassin keys are now processed correctly<br />
<br />
* Fixed various log noise issues<br />
<br />
* Allow root to be key based login only<br />
<br />
* Increased dnscache forwarder cache size<br />
<br />
* Freshclam permissions now corrected<br />
<br />
* Unwanted symlinks in httpd log directory no longer appear<br />
<br />
* Added WPAD feature in DHCP<br />
<br />
* Fixed various perl issues<br />
<br />
* Using long email address now stops regeneration email every day<br />
<br /><br />
<br />
==General features==<br />
<br />
* Based on CentOS 4.6 and all available updates<br />
<br /><br />
<br />
==There are a few differnces from previous releases <=7.2==<br />
<br /><br />
<br />
===After installing for the very first time:===<br />
-----------------------------------------<br />
* First night you should receive an email from cron about sa_updates.<br />
<br />
* First night you should receive a large email saying a bunch of groups/users were removed/added (rkhunter email notification).<br />
<br />
* Any time you change users/groups you will receive an email the next day about those changes (rkhunter email notification).<br />
<br />
<br />
===Taking the upgrade path from a 7.x to 7.3===<br />
-----------------------------------------<br />
* First night you may receive an email from cron about sa_updates<br />
<br />
* First night you may receive a email saying missing passwd/group files (rkhunter email notification).<br />
<br />
<br />
$Id: README.txt,v 1.20 2008/01/01 17:18:13 slords Exp $</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server:7.3&diff=7198
SME Server:7.3
2008-01-01T19:11:49Z
<p>Byte: /* There are a few differnces from previous releases <=7.2 */</p>
<hr />
<div>==Status: Gold==<br />
<br />
==SME Server 7.3 Release Notes==<br />
<br />
<br />
January 1 2008<br />
<br />
The SME Server development team is pleased to announce the release of<br />
SME Server 7.3. This release is based on CentOS 4.6 and all packages<br />
have been updated to the latest releases.<br />
<br />
<br />
All SME Server users should upgrade to this release.<br />
<br />
<br />
Bug reports and reports of potential bugs should be raised<br />
in the bug tracker (and only there, please);<br />
<br />
http://bugs.contribs.org/<br />
<br />
<br />
===About SME Server===<br />
<br />
<br />
SME Server is the leading Linux distribution for small and medium<br />
enterprises. SME Server is brought to you by SME Server, Inc.<br />
( http://www.smeserver.org/ ), a non-profit corporation that exists to<br />
provide marketing and legal support for SME Server.<br />
<br />
SME Server is freely available under the GNU General Public License<br />
and is only possible through the efforts of the SME Server community.<br />
However, the availability and quality of SME Server is dependent on<br />
meeting our expenses, such as hosting costs, server hardware, etc.<br />
<br />
As such, we ask for a small donation to offset costs and fund further<br />
development.<br />
<br />
Please visit http://www.smeserver.org/donate/ to donate.<br />
<br />
<br />
===Thanks===<br />
------<br />
The development team would like to thank all of those involved in<br />
this release. However, this distribution cannot continue with the<br />
current level of support. More people are required to help with<br />
bug triage and verification testing.<br />
<br />
<br />
This release contains many new features, all released updates for<br />
SME Server 7.2 and fixes for many reported problems. Upgrades<br />
will be available by CD, the Software Installer and command line.<br />
<br />
<br />
==Upgrades==<br />
<br />
<br />
* Always perform a backup prior to major system upgrades<br />
<br />
* An upgrade will preserve the existing data<br />
<br />
<br />
==Changes in this release==<br />
<br />
<br />
<br />
===Installer Options===<br />
-----------------<br />
* Using "sme multipart" boot parameter now enables quotas on all LVM's see bug 3651 on how to create your quota files<br />
<br />
<br />
===Other mail system changes===<br />
-------------------------<br />
* Support for disconnect option in rhsbl plugin<br />
<br />
* Support for disconnect immediately if dnsbl plugin rejects recipient addresses<br />
<br />
* Newer version of ipsvd to resolve a few Thunderbird issues<br />
<br />
* Support for configurable timeouts which by default is set to two minutes<br />
<br />
<br />
===Console===<br />
-------<br />
* Now able to remove Corporate DNS setting<br />
* Raid reconstruction now finishes after using "sme nolvm" passed at install time<br />
<br />
<br />
===Backups===<br />
-------<br />
* Ability to use console restore with CD or DVD recordable media<br />
<br />
* Remove smbpasswd file prior to restore<br />
<br />
<br />
===Localisation===<br />
------------<br />
* The fr-fr browser language is now supported<br />
<br />
* Italian translation minor update<br />
<br />
<br />
===Software Installer===<br />
------------------<br />
* The voxteneo.com and fullnet.co.uk mirrors has been added as a mirror location. Many thanks to all of our mirrors<br />
<br />
* Removed planetmirror mirror due to being unstable for a number of months<br />
<br />
* Added smecontribs repository to smeserver<br />
<br />
<br />
===Webmail===<br />
-------<br />
* Horde, imp, turbo and ingo have been updated to the latest versions<br />
<br />
<br />
===Server manager===<br />
--------------<br />
* Updated wording in Server manager > proxy to be correct when running in serveronly mode<br />
<br />
* Now able to remove settings in the Corporate DNS panel<br />
<br />
* Make qpsmtpd/state visible in the view log files<br />
<br />
* Convert squid timestamp in view log files<br />
<br />
* Since we moved to session-based login changing admin password does no longer invalidate access to server manager<br />
<br />
* Added support if you use port-forwarding with an external dynamic ip address<br />
<br />
<br />
===Other fixes and updates===<br />
-----------------------<br />
* More changes have been made in preparation for migration to CentOS5<br />
<br />
* Various samba issues fixed with new samba 3.0.25b package<br />
<br />
* Smartd is disabled by default but has built in templates to enable<br />
<br />
* Import of spamassassin keys are now processed correctly<br />
<br />
* Fixed various log noise issues<br />
<br />
* Allow root to be key based login only<br />
<br />
* Increased dnscache forwarder cache size<br />
<br />
* Freshclam permissions now corrected<br />
<br />
* Unwanted symlinks in httpd log directory no longer appear<br />
<br />
* Added WPAD feature in DHCP<br />
<br />
* Fixed various perl issues<br />
<br />
* Using long email address now stops regeneration email every day<br />
<br /><br />
<br />
==General features==<br />
<br />
* Based on CentOS 4.6 and all available updates<br />
<br /><br />
<br />
==There are a few differnces from previous releases <=7.2==<br />
<br /><br />
<br />
===After installing for the very first time:===<br />
-----------------------------------------<br />
* First night you should receive an email from cron about sa_updates.<br />
<br />
* First night you should receive a large email saying a bunch of groups/users were removed/added (rkhunter email notification).<br />
<br />
* Any time you change users/groups you will receive an email the next day about those changes (rkhunter email notification).<br />
<br />
<br />
===Taking the upgrade path from a 7.x to 7.3===<br />
-----------------------------------------<br />
* First night you may receive an email from cron about sa_updates<br />
<br />
* First night you may receive a email saying missing passwd/group files (rkhunter email notification).<br />
<br />
<br />
$Id: README.txt,v 1.20 2008/01/01 17:18:13 slords Exp $</div>
Byte
https://wiki.koozali.org/index.php?title=SME_Server:7.3&diff=7197
SME Server:7.3
2008-01-01T19:11:28Z
<p>Byte: /* There are a few differnces from previous releases <=7.2 */</p>
<hr />
<div>==Status: Gold==<br />
<br />
==SME Server 7.3 Release Notes==<br />
<br />
<br />
January 1 2008<br />
<br />
The SME Server development team is pleased to announce the release of<br />
SME Server 7.3. This release is based on CentOS 4.6 and all packages<br />
have been updated to the latest releases.<br />
<br />
<br />
All SME Server users should upgrade to this release.<br />
<br />
<br />
Bug reports and reports of potential bugs should be raised<br />
in the bug tracker (and only there, please);<br />
<br />
http://bugs.contribs.org/<br />
<br />
<br />
===About SME Server===<br />
<br />
<br />
SME Server is the leading Linux distribution for small and medium<br />
enterprises. SME Server is brought to you by SME Server, Inc.<br />
( http://www.smeserver.org/ ), a non-profit corporation that exists to<br />
provide marketing and legal support for SME Server.<br />
<br />
SME Server is freely available under the GNU General Public License<br />
and is only possible through the efforts of the SME Server community.<br />
However, the availability and quality of SME Server is dependent on<br />
meeting our expenses, such as hosting costs, server hardware, etc.<br />
<br />
As such, we ask for a small donation to offset costs and fund further<br />
development.<br />
<br />
Please visit http://www.smeserver.org/donate/ to donate.<br />
<br />
<br />
===Thanks===<br />
------<br />
The development team would like to thank all of those involved in<br />
this release. However, this distribution cannot continue with the<br />
current level of support. More people are required to help with<br />
bug triage and verification testing.<br />
<br />
<br />
This release contains many new features, all released updates for<br />
SME Server 7.2 and fixes for many reported problems. Upgrades<br />
will be available by CD, the Software Installer and command line.<br />
<br />
<br />
==Upgrades==<br />
<br />
<br />
* Always perform a backup prior to major system upgrades<br />
<br />
* An upgrade will preserve the existing data<br />
<br />
<br />
==Changes in this release==<br />
<br />
<br />
<br />
===Installer Options===<br />
-----------------<br />
* Using "sme multipart" boot parameter now enables quotas on all LVM's see bug 3651 on how to create your quota files<br />
<br />
<br />
===Other mail system changes===<br />
-------------------------<br />
* Support for disconnect option in rhsbl plugin<br />
<br />
* Support for disconnect immediately if dnsbl plugin rejects recipient addresses<br />
<br />
* Newer version of ipsvd to resolve a few Thunderbird issues<br />
<br />
* Support for configurable timeouts which by default is set to two minutes<br />
<br />
<br />
===Console===<br />
-------<br />
* Now able to remove Corporate DNS setting<br />
* Raid reconstruction now finishes after using "sme nolvm" passed at install time<br />
<br />
<br />
===Backups===<br />
-------<br />
* Ability to use console restore with CD or DVD recordable media<br />
<br />
* Remove smbpasswd file prior to restore<br />
<br />
<br />
===Localisation===<br />
------------<br />
* The fr-fr browser language is now supported<br />
<br />
* Italian translation minor update<br />
<br />
<br />
===Software Installer===<br />
------------------<br />
* The voxteneo.com and fullnet.co.uk mirrors has been added as a mirror location. Many thanks to all of our mirrors<br />
<br />
* Removed planetmirror mirror due to being unstable for a number of months<br />
<br />
* Added smecontribs repository to smeserver<br />
<br />
<br />
===Webmail===<br />
-------<br />
* Horde, imp, turbo and ingo have been updated to the latest versions<br />
<br />
<br />
===Server manager===<br />
--------------<br />
* Updated wording in Server manager > proxy to be correct when running in serveronly mode<br />
<br />
* Now able to remove settings in the Corporate DNS panel<br />
<br />
* Make qpsmtpd/state visible in the view log files<br />
<br />
* Convert squid timestamp in view log files<br />
<br />
* Since we moved to session-based login changing admin password does no longer invalidate access to server manager<br />
<br />
* Added support if you use port-forwarding with an external dynamic ip address<br />
<br />
<br />
===Other fixes and updates===<br />
-----------------------<br />
* More changes have been made in preparation for migration to CentOS5<br />
<br />
* Various samba issues fixed with new samba 3.0.25b package<br />
<br />
* Smartd is disabled by default but has built in templates to enable<br />
<br />
* Import of spamassassin keys are now processed correctly<br />
<br />
* Fixed various log noise issues<br />
<br />
* Allow root to be key based login only<br />
<br />
* Increased dnscache forwarder cache size<br />
<br />
* Freshclam permissions now corrected<br />
<br />
* Unwanted symlinks in httpd log directory no longer appear<br />
<br />
* Added WPAD feature in DHCP<br />
<br />
* Fixed various perl issues<br />
<br />
* Using long email address now stops regeneration email every day<br />
<br /><br />
<br />
==General features==<br />
<br />
* Based on CentOS 4.6 and all available updates<br />
<br /><br />
<br />
==There are a few differnces from previous releases <=7.2==<br />
<br /><br />
<br />
<br />
===After installing for the very first time:===<br />
-----------------------------------------<br />
* First night you should receive an email from cron about sa_updates.<br />
<br />
* First night you should receive a large email saying a bunch of groups/users were removed/added (rkhunter email notification).<br />
<br />
* Any time you change users/groups you will receive an email the next day about those changes (rkhunter email notification).<br />
<br />
<br />
===Taking the upgrade path from a 7.x to 7.3===<br />
-----------------------------------------<br />
* First night you may receive an email from cron about sa_updates<br />
<br />
* First night you may receive a email saying missing passwd/group files (rkhunter email notification).<br />
<br />
<br />
$Id: README.txt,v 1.20 2008/01/01 17:18:13 slords Exp $</div>
Byte