<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>studiosacchetti.com &#187; centos</title>
	<atom:link href="http://www.studiosacchetti.com/tag/centos/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.studiosacchetti.com</link>
	<description>Soluzioni informatiche per piccole e medie aziende</description>
	<lastBuildDate>Fri, 13 Jan 2012 14:14:50 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Building an rpm to install script filesBuilding an rpm to install script files</title>
		<link>http://www.studiosacchetti.com/2010/building-an-rpm-to-install-script-filesbuilding-an-rpm-to-install-script-files/</link>
		<comments>http://www.studiosacchetti.com/2010/building-an-rpm-to-install-script-filesbuilding-an-rpm-to-install-script-files/#comments</comments>
		<pubDate>Mon, 31 May 2010 18:56:33 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Tecnici]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[rpm]]></category>

		<guid isPermaLink="false">http://www.studiosacchetti.com/?p=357</guid>
		<description><![CDATA[On an rpm based system, say CentOS, first make sure that the rpm-build package is installed. In your user account, not as root (bad form and all) make the following directories: mkdir -p ~/rpm mkdir -p ~/rpm/BUILD mkdir -p ~/rpm/RPMS mkdir -p ~/rpm/SOURCES mkdir -p ~/rpm/SPECS mkdir -p ~/rpm/SRPMS mkdir -p ~/rpm/tmp And create an [...]]]></description>
			<content:encoded><![CDATA[<p>On an rpm based system, say CentOS, first make sure that the  rpm-build package is installed.</p>
<p>In your user account, not as root (bad form and all) make the  following directories:</p>
<p><code><span id="more-357"></span><br />
mkdir -p ~/rpm<br />
mkdir -p ~/rpm/BUILD<br />
mkdir -p ~/rpm/RPMS<br />
mkdir -p ~/rpm/SOURCES<br />
mkdir -p ~/rpm/SPECS<br />
mkdir -p ~/rpm/SRPMS<br />
mkdir -p ~/rpm/tmp<br />
</code></p>
<p>And create an ~/.rpmmacros file with the following in it:</p>
<p><code><br />
%packager       Your Name<br />
%_topdir        /home/YOUR HOME DIR/rpm<br />
%_tmppath       /home/YOUR HOME DIR/rpm/tmp<br />
</code></p>
<p>And now comes the fun part.  Go to the ~/rpm/SOURCES directory and  create a working package directory under that with the package name and a  dash and the major revision number.  For example, ~/rpm/SOURCES/linc-1.   Now in that directory you will copy all the scripts/files that you  wish to have in your package.  For example, I might have a script in  that directory called myscript.sh that I want to be installed as part of  the linc package.</p>
<p>Once that is done, make a tarball of that directory in the  ~/rpm/SOURCES directory named programname-revision.tar.gz.  Using my  previous example it would be:<br />
<code><br />
tar czvf linc-1.tar.gz linc-1/<br />
</code></p>
<p>Now for the glue that makes this all stick together.  Go to your  ~/rpm/SPECS directory and create a spec file for your package.  We’ll  call mine linc.spec and it’ll look like this:</p>
<p><code><br />
Summary: My first rpm script package<br />
Name: linc<br />
Version: 1<br />
Release: 1<br />
Source0: linc-1.tar.gz<br />
License: GPL<br />
Group: MyJunk<br />
BuildArch: noarch<br />
BuildRoot: %{_tmppath}/%{name}-buildroot<br />
%description<br />
Make some relevant package description here<br />
%prep<br />
%setup -q<br />
%build<br />
%install<br />
install -m 0755 -d $RPM_BUILD_ROOT/opt/linc<br />
install -m 0755 myscript.sh $RPM_BUILD_ROOT/opt/linc/myscript.sh<br />
%clean<br />
rm -rf $RPM_BUILD_ROOT<br />
%post<br />
echo " "<br />
echo "This will display after rpm installs the package!"<br />
%files<br />
%dir /opt/linc<br />
/opt/linc/myscript.sh<br />
</code></p>
<p>A lot of that file is pretty self explanatory except then install  lines and the lines after %file.  The install lines tell rpm what to  install where and with what permissions.  You also have to do any  directory creation there as well (the one with the -d in the line).  The  things after %file are similar in that this tells rpm’s database which  files are attached to this package.  The %dir signifies a new directory,  otherwise the files are listed with their complete paths.</p>
<p>Now that you have all that together.  The last thing you need do is  create the package.  Just  go to ~/rpm and do an “rpmbuild -ba  SPECS/linc.spec”.  You will end up with an  ~/rpm/RPMS/noarch/linc-1-1.noarch.rpm if all goes well.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.studiosacchetti.com/2010/building-an-rpm-to-install-script-filesbuilding-an-rpm-to-install-script-files/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>how to install a plesk web server on CentOS 5.3</title>
		<link>http://www.studiosacchetti.com/2009/how-to-install-a-plesk-web-server-on-centos-5-3/</link>
		<comments>http://www.studiosacchetti.com/2009/how-to-install-a-plesk-web-server-on-centos-5-3/#comments</comments>
		<pubDate>Wed, 29 Jul 2009 13:16:32 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Tecnici]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[linux]]></category>
		<category><![CDATA[plesk]]></category>

		<guid isPermaLink="false">http://www.studiosacchetti.com/?p=301</guid>
		<description><![CDATA[Start the CentOS installer by booting from cd/dvd. For partitioning advice, I followed parallels suggestions We cannot give any exact numbers, however, you should take into account the following.Plesk for Linux OSes stores all users&#8217; data in /var partition by default, so the partitioning should be like: SWAP → twice RAM size /boot → 128 [...]]]></description>
			<content:encoded><![CDATA[<ol>
<li>Start the CentOS installer by booting from cd/dvd.</li>
<li>For partitioning advice, I followed parallels suggestions<br />
We cannot give any exact numbers, however, you should take into account the following.Plesk for Linux OSes stores all users&#8217; data in /var partition by default, so the partitioning should be like:<code><br />
SWAP 	→	twice RAM size</code><br />
<code>/boot 	→	128 MB</code><br />
<code>/ 	→	System + Plesk, updates. 5-10 GB should be enough.</code><br />
<code>/tmp	→	1GB.</code><br />
<code>/var	→	the rest of the space (domains, mail, backups, databases are stored there)</code><span id="more-301"></span></p>
<p>Directories that usually take much disk space:<code>/var/www/vhosts (/srv/vhosts on SuSE) - domains.</code><br />
<code>/var/qmail - mail.</code><br />
<code>/var/lib/mysql - Mysql databases.</code><br />
<code>/var/lib/psa/dumps - Plesk clients'/domains' backups.</code><br />
<code>/var/lib/pgsql/data - Postgres databases.</code><br />
<code>/var/tomcat* - Tomcat applications.</code><br />
<code>/var/lib/mailman - Mailman lists.</code></p>
<p>Please check file /etc/psa/psa.conf for all other directories used by Plesk control panel.<br />
Plesk Control Panel under FreeBSD uses the /usr/local partition for storing large quantity of data and /var/db partition for databases.<br />
So the /usr and /var partitions have to be larger in this case.</li>
<li>When prompted by the installer, I deselected all installation types.</li>
<li>I 	entered my appropriate network config when prompted. In my case I specifified a static public IP and corresponding gateway and also a couple of know public dns server addresses, although depending on 	your needs/set-up, you might want/need to be using DHCP.</li>
<li>After the installation has completed and you re-boot, upon first log-in you are presented with a network configuration utility; as I&#8217;d set 	my network up previously I didn&#8217;t need to do anything with this although there is also a security option which I did alter &#8211; by 	default there is a firewall configured to block most services 	including HTTP. I chose to switch this off totally at this point as I would be using Plesk to manage the firewall later on.</li>
<li>Now I wanted to perform some system updates via Yum, however because CentOS uses bind in a chrooted set-up which doesn&#8217;t work well with 	Plesk, I did the following (after a previous attempt without this knowledge caused me big problems with Bind):
<ul>
<li>Edit /etc/yum.conf and, under the [main] section, add the line<br />
<code>exclude=bind-chroot</code></li>
<li>Next, get rid of the currently installled bind-chroot package<br />
<code># rpm -e bind-chroot</code></li>
<li>Now we can use Yum to provide system updates [Please note, if you plan on using ARTs yum packages, which is a really good idea because you 	get updated Plesk compatible versions of both PHP and MySQL, do not 	add this channel to yum just yet, otherwise the Plesk installer won't run until they've been removed!!].<br />
<code>#yum check-update</code><br />
<code>#yum update</code></li>
</ul>
</li>
<li>Now you&#8217;re system is up to date, you can go off and get and then 	run the Plesk auto-installer. To install Parallels Plesk Panel software on a server:
<ol>
<li> Download 	the latest version of Parallels Products Installer that suits your 	operating system from <a href="http://www.parallels.com/en/download/plesk9/">http://www.parallels.com/en/download/plesk9/</a> and save it on your server&#8217;s hard drive.</li>
<li>Change 	your working directory to the directory where the downloaded 	Parallels Products Installer is located.</li>
<li>Set the execution 	permission for Parallels Products Installer:<code><br />
# chmod +x parallels_products_installer_file_name<br />
</code></li>
<li>Run the following command in console:<br />
<code>#export LANG=C<br />
<code>#export LANG_ALL=C<br />
</code></code></li>
<li>Run 	Parallels Products Installer:
<ul>
<li>To install 		Parallels Plesk Panel through the web interface of Parallels 		Products Installer, run the following command:<code><br />
# ./parallels_products_installer_file_name --web-interface</code><br />
Open your browser and 		enter https://hostname:8447/ or https://IP-address:8447/ in the address bar. The Parallels Product Installer web interface 		will open. Log in as root.</li>
<li>To install 		Parallels Plesk Panel through the command line interface of 		Parallels Products Installer, run the following command:<br />
# ./parallels_products_installer_file_name</li>
</ul>
</li>
<li>Follow 	the instructions presented on the screen to complete the 	installation. Refer to Parallels Plesk Panel Installation Guide 	available at 	<a href="http://download1.parallels.com/Plesk/Plesk9.2/Doc/en-US/plesk-9.2-unix-installation-guide/index.htm">http://download1.parallels.com/Plesk/Plesk9.2/Doc/en-US/plesk-9.2-unix-installation-guide/index.htm</a> if you need detailed installation instructions.</li>
<li>When the 	installation is finished, Parallels Plesk Panel will start 	automatically.</li>
</ol>
</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.studiosacchetti.com/2009/how-to-install-a-plesk-web-server-on-centos-5-3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

