GRANT ALL ON testdb.* TO 'testuser'@'localhost' IDENTIFIED BY 'pass1';

You can also limit user’s privileges to specific ip addresses or domains in case you need to access your databases from a different host.

GRANT ALL ON *.* TO 'testuser'@'remote.farmsoftstudios.com' IDENTIFIED BY 'pass1';

[root@localhost ~]# cat /etc/redhat-release
CentOS release 5 (Final)

Create a directory on the root:
mkdir /sharename

Then mount the share:

mount -t cifs //<servername>/<sharename> /sharename

if you type df -h you should see that your share is now mounted on the mountpoint that you created earlier.

<table>
 <tr class=”title”>
  <td></td>
 </tr>
<?php
$i=0;
foreach($row as $r){
   if($i&0){$alt=‘ class=”even”‘;}else{$alt=”;}
   echo “<tr”.$alt.“>”;
   //other table stuff in here
   $i++;
   echo “</tr>”;
}
?>
</table>


These days, I consider the failure to use version control a professional malpractice. I’m also a zealot when it comes to deleting dead code. In fact, I derive quite a bit of enjoyment out of deleting existing code. Unused code, old code, mockups, things that were started and never finished, things that someone thought they needed and never did—I’m delighted to delete them all.

Quoting from the latest PHP|Architect (August 2008) article, I found Jeff Moore’s writing insightful as well as helpful.  A strong contender for clean code, he suggests deleting stranded, dead, or depreciated codeblocks.  As far as his suggestion for version control, I would completely agree.  I maintained/wrote an entire project without version control (along with two other developers), and I sincerely hope that I never have to do that again.  It was a total disaster.  FTP overwrites, deleted code that had dependancies, and no way to roll back equalled extreme project management headaches.

My Advice: Use Version Control. Period.

If you just need to block a certain port (i.e. port 22 for SSH), you would do it like so:

iptables -A INPUT -s 222.124.24.131 -p tcp --destination-port 22 -j DROP