Search results for query: *

The only other thing you can do to improve BadBigBen code is to add '| wc -l' at the end which will count the number of rows grep returns. --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

I had a similar issue with users using an Access DB, but I'm sure this would apply to all file based databases. Try disabling all oplocks. I also read about tweaking the "lock spin" parameters, but havent tried them as the disabling oplocks did it for me. As a matter of fact, you may want to...

At any time you suspect your HDD if flaky, get the HDD manufacturer's DFT (Drive Fitness Test) CD & wipe/zero the whole disk (after making a backup of course). This should relocate any bad or suspected to be bad sectors. --== Anything can go wrong. It's just a matter of how far wrong it will go...

You may want to read up on this post http://www.tek-tips.com/viewthread.cfm?qid=1318503&page=1 --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

You can also try using implode() to convert your array into a string in the sending page then explode() it back into an array in the receiving page. --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

If your accessories information (d1line, d2line, hpd2line, etc) were stored in an array. eg. $accessories = null; $accessoriesList = array($d1line, $d2line, $d1eline, $d2eline, $d3line, $d5line, $d7line, $w1line, $hpd1line, $hpd2line); foreach($accessoriesList as $value) {...

Overlooked it earlier, but can you change the double back tic ``admin`` to just `admin`? --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

If you id column is an int, shouldn't WHERE id=%s be WHERE id=%d? --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

I'd be confused too if I can't see the "how" & "what". Start by showing us the section of your problematic PHP code and a sample of your data. --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

As the message says, your SQL syntax is wrong. Print/echo out the full statement. --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

The tar format is just a sequential concatenation of files and as such has no 'limit' per se. The only thing limiting the size of a tar archive would be the file system it is created on. I've done backups of my file server with more than 200GB onto DLTs & some 50GB to 100GB of temporary backups...

The %s is a string placeholder or variable that gets "filled in" with the string value passed in after the comma. Example 1: print sprintf("My name is %s", 'Dave'); %s in this case will be filled in with the word - Dave. Example 2: print sprintf("I am %d years old", 35); %d is an integer...

If your eventids are sorted, then use a temp variable to store the last eventid and compare it to the one you currently have. If its the same, new <td>, else new <tr>. --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

The permission of /var/spool/cups is 710, meaning people in the sys group can change into, but can't see anything in it. --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

32-bits --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

You can either try uname -a to check the version of the running kernel or rpm -q kernel. With both command, take note of the string if it contains i386/i586/i686(32bit) or x86_64(64bit). --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

I see use of divide & section. Then is see the example where there are 2 distinct "Head" words in all the gibberish. This leads me to think that the OP might want to break the line before the Head word THEN replace all the spaces with commas. We might try this: $new_string = null...

I followed the link but it doesn't look like a repository. --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

This may sound stupid but have checked your RHN account to see if your server is allowed to do updates? --== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--

You have to be specific about the package name. Try searching for it first with yum search package to see if it returns any hits. The package name in a search can be a partial but not for install. Once you know the package name, yum will grab it off the internet and install it along with all...