<?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>Admon Home &#187; debian</title>
	<atom:link href="http://www.admon.org/tag/debian/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.admon.org</link>
	<description>Linux System Administration</description>
	<lastBuildDate>Sat, 19 May 2012 03:36:55 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Update Debian Lenny to Squeeze</title>
		<link>http://www.admon.org/update-debian-lenny-to-squeeze/</link>
		<comments>http://www.admon.org/update-debian-lenny-to-squeeze/#comments</comments>
		<pubDate>Thu, 01 Dec 2011 01:58:12 +0000</pubDate>
		<dc:creator>joseph</dc:creator>
				<category><![CDATA[Reviews]]></category>
		<category><![CDATA[apt-get]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[lenny]]></category>
		<category><![CDATA[squeeze]]></category>

		<guid isPermaLink="false">http://www.admon.org/?p=1065</guid>
		<description><![CDATA[The upgrade between major releases for Debian system is quite easy compared to RHEL / CentOS. How can I upgrade to Debian GNU/Linux 6.0 (Squeeze) from the previous Debian 5.0 (Lenny) remotely? The upgrades can be handled well by the command apt-get. Anyway before running the upgrade, it&#8217;s highly suggested to make a backup &#8211; [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-medium wp-image-736" title="debian" src="http://www.admon.org/wp-content/uploads/2010/06/debian-300x261.png" alt="Debian Linux" width="300" height="261" />The upgrade between major releases for Debian system is quite easy compared to RHEL / CentOS.</p>
<p>How can I upgrade to Debian GNU/Linux 6.0 (Squeeze) from the previous Debian 5.0 (Lenny) remotely?<span id="more-1065"></span></p>
<p>The upgrades can be handled well by <a title="Debian apt Howto Guide" href="http://www.debian.org/doc/manuals/apt-howto/" target="_blank">the command apt-get</a>. Anyway before running the upgrade, it&#8217;s highly suggested to make a backup &#8211; at least the most important part of your system should be backup-ped. The <a title="Debian Upgrade Guide" href="http://www.debian.org/releases/stable/powerpc/release-notes/ch-upgrading.en.html" target="_blank">official Debian document</a> recommends:</p>
<blockquote><p>The main things you&#8217;ll want to back up are the contents of /etc, /var/lib/dpkg, /var/lib/apt/extended_states and the output of dpkg &#8211;get-selections &#8220;*&#8221; (the quotes are important). If you use aptitude to manage packages on your system, you will also want to back up /var/lib/aptitude/pkgstates.</p></blockquote>
<p>Let&#8217;s start the Debian Squeeze upgrade now. Firstly edit the file called /etc/apt/sources.list, enter:</p>
<pre># vi /etc/apt/sources.list</pre>
<p>Replace the word &#8220;<em>lenny</em>&#8221; with &#8220;<em>squeeze</em>&#8220;, the it should look as follows:</p>
<pre>deb http://ftp.us.debian.org/debian/ squeeze main
deb http://security.debian.org/ squeeze/updates main</pre>
<p>These two lines are important for our upgrade, and you may have other lines inside, they don&#8217;t make much sense. Save and close the file. Type the following commands:</p>
<pre># apt-get update
# apt-get install apt dpkg aptitude
# apt-get dist-upgrade</pre>
<p>When they all finish smoothly, it&#8217;s time to reboot the server. After a reboot make sure all services are running:</p>
<pre># lsb_release -a
# tail -f /var/log/messages</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.admon.org/update-debian-lenny-to-squeeze/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Manage Debian auto startup scripts</title>
		<link>http://www.admon.org/manage-debian-auto-startup-scripts/</link>
		<comments>http://www.admon.org/manage-debian-auto-startup-scripts/#comments</comments>
		<pubDate>Fri, 11 Jun 2010 15:24:31 +0000</pubDate>
		<dc:creator>joseph</dc:creator>
				<category><![CDATA[Applications]]></category>
		<category><![CDATA[System Tuning]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[init scripts]]></category>
		<category><![CDATA[update-rc.d]]></category>

		<guid isPermaLink="false">http://planet.admon.org/?p=689</guid>
		<description><![CDATA[Debian uses a Sys-V like init system for executing commands when the system runlevel changes &#8211; for example at bootup and shutdown time. Its startup files are stored in /etc/init.d/ and symbolic linked within the /etc/rcX.d/ directories. Debian Linux comes with different utilities to manage these startup file, here we&#8217;ll show two examples on managing [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://planet.admon.org/wp-content/uploads/2010/06/debian.png"><img class="size-thumbnail wp-image-736 alignleft" title="debian" src="http://planet.admon.org/wp-content/uploads/2010/06/debian-150x150.png" alt="Debian Linux" width="150" height="150" /></a>Debian uses a <a href="http://en.wikipedia.org/wiki/UNIX_System_V">Sys-V like</a> init system for executing commands when the system runlevel changes &#8211; for example at bootup and shutdown time. Its startup files are stored in <em>/etc/init.d/</em> and symbolic linked within the <em>/etc/rcX.d/</em> directories. Debian Linux comes with different utilities to manage these startup file<span id="more-689"></span>, here we&#8217;ll show two examples on managing these system init scripts.</p>
<p><strong>1, rcconf </strong>- <a href="http://packages.debian.org/lenny/rcconf">http://packages.debian.org/lenny/rcconf</a></p>
<p>This tool configures system services in connection with system runlevels. It turns on/off services using the scripts in <em>/etc/init.d/</em>. Rcconf works with System-V style runlevel configuration. It is a Text User Interface (TUI) frontend to the update-rc.d command.</p>
<p>To start <strong>rcconf</strong>, login as root and type the command &#8220;<em>rcconf</em>&#8220;, then select the service that you would like to enable or disable, and press Tab to apply a change.</p>
<p>A similar command is <a href="http://packages.debian.org/lenny/sysv-rc-conf">sysv-rc-conf</a>, you can make more specified choices in this TUI based configuration tool.</p>
<p><strong>2, sysv-rc</strong> &#8211; <a href="http://packages.debian.org/lenny/sysv-rc">http://packages.debian.org/lenny/sysv-rc</a></p>
<p>Sysv-rc provides a terminal interface for managing &#8220;<em>/etc/rcX.d/</em>&#8221; symlinks. With the help of update-rc.d, you can allow turning services on or off simply. Actually it&#8217;s much what <a href="http://www.linuxjournal.com/article/4445">chkconfig</a> does in Redhat/CentOS, which means you can edit startup scripts for any runlevel.</p>
<p>By default <strong>sysv-rc</strong> is installed even in a minimal installation. Otherwise you need to run &#8220;apt-get install sysv-rc&#8221; to install it. Here&#8217;re some common usage examples for update-rc.d:</p>
<p>To remove the service SERVICE-NAME:</p>
<pre>update-rc.d -f SERVICE-NAME remove</pre>
<p>To add the service SERVICE-NAME:</p>
<pre>update-rc.d SERVICE-NAME defaults</pre>
<pre>update-rc.d SERVICE-NAME defaults 29</pre>
<p>The argument 29 is optional, which ensures that SERVICE-NAME is called after all scripts whose number is less than 29 have completed, and before all scripts whose number is 30 or greater.</p>
<p>To start the script SERVICE-NAME in runlevels 2345 and stop in 456, run (as root):</p>
<pre>update-rc.d SERVICE-NAME start 2 3 4 5 . stop 0 1 6 .</pre>
<pre>update-rc.d SERVICE-NAME start 30 2 3 4 5 . stop 70 0 1 6 .</pre>
<p>You can find more details of this command by running &#8220;man 8 update-rc.d&#8221;.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.admon.org/manage-debian-auto-startup-scripts/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>Batch rename files in Linux</title>
		<link>http://www.admon.org/batch-rename-files-in-linux/</link>
		<comments>http://www.admon.org/batch-rename-files-in-linux/#comments</comments>
		<pubDate>Fri, 23 Apr 2010 07:55:35 +0000</pubDate>
		<dc:creator>joseph</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[rename]]></category>

		<guid isPermaLink="false">http://planet.admon.org/?p=595</guid>
		<description><![CDATA[Is there any easy ways to batch rename files in Linux? A common requirement is that the web developers may ask you to help rename all *.html files to *.htm, how can we do that? Someone probably will say that they can make a simple script in some minutes to do this kind of things. [...]]]></description>
			<content:encoded><![CDATA[<p>Is there any easy ways to batch rename files in Linux? A common requirement is that the web developers may ask you to help rename all <em>*.html</em> files to<em> *.htm</em>, how can we do that?<span id="more-595"></span></p>
<p>Someone probably will say that they can make a simple script in some minutes to do this kind of things. Actually you don&#8217;t need to recreate the wheel, the operating system have supplied such an utility already, the command is rename, it&#8217;s part of the <a href="http://www.kernel.org/pub/linux/utils/util-linux/">util-linux package</a>.</p>
<p>With the help of this command, it&#8217;s a very easy work to bulk rename files.<br />
But, note that this command is a little different by systems.<br />
Here we&#8217;ll show the usage examples for <strong>rename</strong> in both Redhat / CentOS and Debian / Ubuntu.</p>
<p><strong>1, Batch rename files in Redhat / CentOS</strong><br />
For the scenario we mentioned above, it can be done like this:</p>
<pre>$ rename .html .htm *</pre>
<p>It renames all files in current working directory that match <em>*.html*</em> to <em>*.htm*</em>.<br />
Note that only the first matched occurrence will be modified. If there&#8217;s a file called <em>abc.html.abc.html</em>, after renamed once, the new name is abc.htm.abc.html, not abc.html.abc.htm.</p>
<p><strong>2, Bulk rename files in Debian / Ubuntu</strong><br />
The command here in Debian are quite different which makes it more powerful and professional.<br />
I&#8217;ll show two examples with explaination:</p>
<pre>$ rename -n 's/.html$/htm/' *</pre>
<p><em>-n</em> means no action will be applied, it will shows detailed information on what files would have been renamed:</p>
<pre>$ rename -n 's/.html$/.htm/' abc.html.abc.html
abc.html.abc.html renamed as abc.html.abc.htm</pre>
<p>The expression regunation here is in Perl style, which means you can apply multiple actions at one time, like this:</p>
<pre>$ rename 's/.html$/htm/, s/css/css.backup/, s/jscript/js/' *</pre>
<p>For more details you can raise a forum thread <a href="http://forum.admon.org/linux-scripting/">here at our support forum</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.admon.org/batch-rename-files-in-linux/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
		<item>
		<title>Rename a Vserver step by step</title>
		<link>http://www.admon.org/rename-a-vserver-step-by-step/</link>
		<comments>http://www.admon.org/rename-a-vserver-step-by-step/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 03:39:09 +0000</pubDate>
		<dc:creator>joseph</dc:creator>
				<category><![CDATA[System Tuning]]></category>
		<category><![CDATA[Virtualization]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[hostname]]></category>
		<category><![CDATA[rename]]></category>
		<category><![CDATA[vserver]]></category>

		<guid isPermaLink="false">http://planet.admon.org/?p=522</guid>
		<description><![CDATA[Suppose you made a mistake on the Vserver name when creating it. After finished the installation, you might want to rename your Vserver. This can be accomplished by renaming the config directory and the root for the vserver in question, then modifying some symlinks to match. The general steps are: Stop the vserver in question [...]]]></description>
			<content:encoded><![CDATA[<p>Suppose you made a mistake on the <a href="http://www.linux-vserver.org/Welcome_to_Linux-VServer.org">Vserver</a> name when creating it. After finished the installation, you might want to <strong>rename your Vserver</strong>. This can be accomplished by renaming the config directory and the root for the vserver in question, then modifying some symlinks to match. <span id="more-522"></span></p>
<p>The general steps are:</p>
<ul>
<li> Stop the vserver in question</li>
<p>It can be done by this command: &#8220;<em>vserver  &lt;server name&gt; </em><em>stop</em>&#8221;</p>
<li>Rename the <em>/vservers/&lt;server name&gt;</em> directory</li>
<p>By default it&#8217;s in /vservers, and on some self-crafted versions, it might be re-defined to other path like /var/lib/vservers. Simply you just need to use mv command to rename the issued vserver.</p>
<li>Rename the <em>/etc/vservers/&lt;server name&gt;</em> directory</li>
<p><a href="http://www.nongnu.org/util-vserver/doc/conf/configuration.html">The directory /etc/vservers</a> is much like a system wide configuration directory for vservers, you can use mv to rename specified directory as well.</p>
<li>Update some softlink in <em>/etc/vservers/&lt;server name&gt;</em></li>
<p>update link: /etc/vservers/&lt;server name&gt;/run -&gt; /var/run/vservers/&lt;server name&gt;<br />
update link: /etc/vservers/&lt;server name&gt;/vdir -&gt; /etc/vservers/.defaults/vdirbase/&lt;server name&gt;<br />
update link: /etc/vservers/&lt;server name&gt;/cache -&gt; /etc/vservers/.defaults/cachebase/&lt;server name&gt;<br />
Pay some attention to relative path issue, otherwise these links might get broken, there&#8217;s an example, the current working directory is <em>/etc/vservers/mars</em>:</p>
<pre>joseph@galaxy:/etc/vservers/mars$ ln -s -f /etc/vservers/.defaults/vdirbase/mars vdir</pre>
<li>Update link: /var/run/vservers.rev/&lt;server XID&gt; -&gt; /etc/vservers/&lt;server name&gt;</li>
<p>Please note that this just an update by fixing the dead link, and there&#8217;s no need to create a new XID.</p>
<li>Reset hostname for vserver in question</li>
<p>Basically you just need to modify <em>/etc/vservers/&lt;server name&gt;/uts/nodename</em> before starting the issued vserver, and get other host name related settings modified when system booted.</p>
<pre>joseph@galaxy:/etc/vservers$ grep mars -R mars/ 2&gt;/dev/null -l
mars/uts/nodename
mars/vdir/etc/hosts
mars/vdir/etc/pam_ldap.conf
mars/vdir/etc/mailname
mars/vdir/etc/hostname</pre>
</ul>
<p>Now, It should start properly. If any issue encountered, please don&#8217;t hesitate to <a href="http://forum.admon.org/virtualization/" target="_blank">raise a forum thread</a> at our community forum.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.admon.org/rename-a-vserver-step-by-step/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Set system variables in Debian and CentOS</title>
		<link>http://www.admon.org/set-syste-variables-in-debian-and-centos/</link>
		<comments>http://www.admon.org/set-syste-variables-in-debian-and-centos/#comments</comments>
		<pubDate>Fri, 30 Oct 2009 16:19:38 +0000</pubDate>
		<dc:creator>joseph</dc:creator>
				<category><![CDATA[Programming]]></category>
		<category><![CDATA[System Tuning]]></category>
		<category><![CDATA[bash]]></category>
		<category><![CDATA[centos]]></category>
		<category><![CDATA[debian]]></category>
		<category><![CDATA[global variable]]></category>
		<category><![CDATA[system variable]]></category>

		<guid isPermaLink="false">http://planet.admon.org/?p=388</guid>
		<description><![CDATA[As indicated in title, this request is probably very common for sysadmins. For example, when a Java environment is ready, we need to make sure that JAVA_HOME is globally available for some system accounts, so that they can restart java instance smoothly. The following section would show an example on how to set the variable [...]]]></description>
			<content:encoded><![CDATA[<p>As indicated in title, this request is probably very common for sysadmins.</p>
<p>For example, when a Java environment is ready, we need to make sure that JAVA_HOME is globally available for some system accounts, so that they can restart java instance smoothly.<span id="more-388"></span></p>
<p>The following section would show an example on how to set the variable ORACLE_HOME to be a global one on both Debian and CentOS. Before we start, it&#8217;s suggested to have a glance on our former post &#8220;<a href="http://planet.admon.org/howto/difference-between-login-shell-and-non-login-shell/">difference between login shell and non-login shell</a>&#8220;.</p>
<p><strong>Set system variables in Debian / Ubuntu</strong></p>
<p>What is considered the best way to set globally exported environment variables in debian?  There are two ways:</p>
<p>For global settings, you can simply add a new line in <strong>/etc/environment</strong> like this:</p>
<pre>ORACLE_HOME=/opt/oracle</pre>
<p>After this modification, re-login is needed, then it would take effect for both login shell and non-login shells.</p>
<p>For a single user, you can apply this line in <strong>~/.bashrc</strong></p>
<pre>export ORACLE_HOME=/opt/oracle</pre>
<p>The above setting would take effect on both shells.<br />
Normally, we just need to support login shells, so you can append the new line in <strong>/etc/profile</strong>. It would do the same work, BUT will not take effect on non-login shells.</p>
<p><strong>Set global variables in CentOS / RHEL</strong></p>
<p>There&#8217;s a standard way to set global environment variables on Redhat based systems, including Redhat 9.0, Fedora series, Red Hat Enterprise series, CentOS 4/5.<br />
You can create a new file in <strong>/etc/profile.d/</strong>, and put the variables in it. This directory is used to store new variables:</p>
<pre>example# ls /etc/profile.d/
colorls.csh  glib2.sh               krb5-devel.sh         lang.sh
colorls.sh   gnome-ssh-askpass.csh  krb5-workstation.csh  less.csh
cvs.sh       gnome-ssh-askpass.sh   krb5-workstation.sh   less.sh
glib2.csh    krb5-devel.csh         lang.csh              which-2.sh</pre>
<p>The file you created should have a suffix &#8220;.sh&#8221;, so that it would be recognized as variable files by bash. No executable permission is needed for this new file. An example file is listed below:</p>
<pre>example# cat oralce.sh
ORACLE_HOME=/opt/oracle</pre>
<p>Note: All the above examples are assumed that you&#8217;re using <a href="http://www.gnu.org/software/bash/">BASH</a>. If you use <a href="http://en.wikipedia.org/wiki/C_shell">CSH </a>as default shell, you should name this new file as &#8220;oracle.csh&#8221;, means the suffix should be &#8220;.csh&#8221;.</p>
<p>If you have any issue on this post, please leave a comment or raise a thread at <a href="http://forum.admon.org/linux-scripting/">our support forum</a>, thanks!</p>
]]></content:encoded>
			<wfw:commentRss>http://www.admon.org/set-syste-variables-in-debian-and-centos/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Use cpulimit to limit CPU time for process</title>
		<link>http://www.admon.org/use-cpulimit-to-limit-cpu-time-for-process/</link>
		<comments>http://www.admon.org/use-cpulimit-to-limit-cpu-time-for-process/#comments</comments>
		<pubDate>Sun, 25 Oct 2009 06:51:38 +0000</pubDate>
		<dc:creator>joseph</dc:creator>
				<category><![CDATA[Applications]]></category>
		<category><![CDATA[System Tuning]]></category>
		<category><![CDATA[apache]]></category>
		<category><![CDATA[CPU]]></category>
		<category><![CDATA[cpulimit]]></category>
		<category><![CDATA[debian]]></category>

		<guid isPermaLink="false">http://planet.admon.org/?p=371</guid>
		<description><![CDATA[How we can limit the CPU usage of a sepcified process with the CPUlimit utility? Cpulimit is a simple program that attempts to limit the CPU usage of a process. It&#8217;s expressed in percentage, not in cpu time. This is useful to control batch jobs, when you don&#8217;t want them to eat too much CPU [...]]]></description>
			<content:encoded><![CDATA[<p><strong>How we can limit the CPU usage of a sepcified process with the <a href="http://cpulimit.sourceforge.net/">CPUlimit</a></strong> <strong>utility?</strong></p>
<p>Cpulimit is a simple program that attempts to <strong>limit the CPU usage of a process</strong>. It&#8217;s expressed in percentage, not in cpu time.</p>
<p>This is useful to control batch jobs, when you don&#8217;t want them to eat too much CPU resource. It does not act on the nice value or other scheduling priority stuff, but on the real CPU usage. Also, it is able to adapt itself to the overall system load, dynamically and quickly.<span id="more-371"></span></p>
<p>If your machine has one processor you can limit the percentage from 0% to 100%, which means that if you set for example 50%, your process cannot use more than 500 ms of cpu time for each second. But if your machine has four processors, percentage may vary from 0% to 400%, so setting the limit to 200% means to use no more than half of the available power. In any case, the percentage is the same of what you see when you run top.</p>
<p>Cpulimit should run at least with the same user running the controlled process. It&#8217;s much better if you run cpulimit as root, in order to have a higher priority and a more precise control.</p>
<p><strong>Installation of CPUlimit</strong></p>
<p>CPUlimit is available for Debian and Ubuntu, so it can be installed by &#8220;<em>aptitude install cpulimit</em>&#8220;. If you&#8217;re running CentOS or other system, you might need to compile it from source code by yourself.</p>
<p>After the installation, let&#8217;s take a look at the cpulimit man page to learn how to use it:</p>
<pre>cpulimit TARGET [OPTIONS...]

TARGET must be exactly one of these:

-p, --pid=N              pid of the process
-e, --exe=FILE           name of the executable program file
-P, --path=PATH          absolute path name of the executable program file

OPTIONS
-l, --limit=N            percentage of CPU allowed from 0 to 100 (mandatory)
-v, --verbose            show control statistics
-z, --lazy               exit if there is no suitable target process, or if it dies
-h, --help               display this help and exit</pre>
<p><strong>Usage of CPUlimit</strong></p>
<p>These examples are from CPUlimit man page as well:</p>
<pre>Assuming  you  have  started "foo --bar" and you find out with top(1) or ps(1) that this process uses all your CPU time you can either

# cpulimit -e foo -l 50
limits the CPU usage of the process by acting on the executable program file. Note: the argument "--bar" is omitted.

# cpulimit -p 1234 -l 50
limits the CPU usage of the process by acting on its PID, as shown by ps(1)

# cpulimit -P /usr/bin/foo -l 50
same as -e but uses the absolute path name</pre>
<p>Now let&#8217;s assume that we want to limit the process httpd to 45%. This is how we do it:</p>
<p>cpulimit -e httpd -l 45</p>
<p>The <em>-e</em> switch takes the name of the executable program file. You can take that name from the output of the top command.</p>
<p>Instead of using the name of the executable program file, we can use the process ID with the -p switch. You can find out the process ID of the httpd process as follows:</p>
<pre>ps aux | grep httpd</pre>
<p>Let&#8217;s assume the httpd process ID is 13500; we can then limit that process to 45% CPU usage as follows:</p>
<pre>cpulimit -p 13500 -l 45</pre>
<p>Instead of using the name of the executable file (-e) of the process ID (-p), we can also pass the absolute path name of the executable program file to cpulimit with the -P switch.</p>
<p>The absolute path name of the httpd executable is /usr/sbin/httpd so we&#8217;d use the following command:</p>
<pre>cpulimit -P /usr/sbin/httpd -l 45</pre>
<p>Please note that cpulimit will run in the foreground of your terminal until you terminate it with CTRL+C &#8211; terminating it will also remove any CPU limits.</p>
<p><strong>Further Readings</strong></p>
<p>CPUlimit Homepage:  <a href="http://cpulimit.sourceforge.net/">http://cpulimit.sourceforge.net/</a></p>
<p>AND Homepage:  <a href="http://and.sourceforge.net/">http://and.sourceforge.net/</a></p>
]]></content:encoded>
			<wfw:commentRss>http://www.admon.org/use-cpulimit-to-limit-cpu-time-for-process/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

