How to clear Drupal’s cache

The easiest and fastest way to clear Drupal’s cache if you have access to its database is to execute the following SQL query on its database:

DELETE FROM {cache};

Another way to clear the cache in Drupal is to create a PHP file to clear caches and rebuild the routing tables. Be careful not to leave this on the server as anyone can clear caches if they know the file name. Create a file named clear.php with the following code. Place the file in drupal base directory and run it by browsing to http://example.com/clear.php.

include_once './includes/bootstrap.inc';
drupal_bootstrap(DRUPAL_BOOTSTRAP_FULL);
drupal_flush_all_caches();
?>

The third and the lamest way is through the Drupal’s admin area. Simply go to Administer > Site configuration > Performance. Near the bottom of the page, you’ll see a big fat button that says “Clear cached data.” I think you can take it from there.

What is RGP – Redemption Grace Period explained

RGP stands for Redemption Grace Period. The Redemption Grace Period is a thirty (30) day period that begins after a registrar requests that the registry delete a domain name. The Internet Corporation for Assigned Names and Numbers (ICANN) has required that registries implement this facility to allow the original registrants (domain name holders) to redeem a deleted name.

The reason for the introduction of the RGP process is to provide additional time to catch erroneous deletions before the name is made available for re-registration.

When a name enters RGP, it is removed from the zone file (if it was originally in the zone file). As a result, any Internet services served by the domain name will be disabled (e.g. e-mail or a Web site). The registrant must act IMMEDIATELY if he or she wants to keep the name.

What is DNS propagation and why does it take so long?

You’ve registered your domain name, and paid for hosting with a hosting provider, and uploaded your website to the web server. If this is all done, why can’t you see the results of your hard work right away? What is this DNS propagation people keep telling you about?

In order to understand DNS propagation, you must first understand a little about how DNS works. When you set up your website with your hosting provider, they create a Master DNS record in their Domain Name Servers. Your domain registrar (the company you paid for the honor of owning your domain name) points to your web host’s DNS server as being the master authority of your domain.

When any outside source wants to know how to find your website, they first go to the registration database to find out who the DNS authority is for your website. Then they visit your hosting provider’s DNS servers to find out what the IP Address is for your domain name, and from there your audience can now view your website.

The problem with this whole scheme is that in order to speed up the rate at which their customers can view the internet, each Internet Server Provider caches their DNS records. This means that they make their own copy of the master records, and read from them locally instead of looking them up on the Internet each time someone wants view a website. This actually speeds up web surfing quite a bit, by (1) speeding up the return time it takes for a web browser to request a domain lookup and get an answer, and (2) actually reducing the amount of traffic on the web therefore giving it the ability to work faster.

The downside to this caching scenario and what makes it take so long for your website to be visible to everyone, is that each company or ISP that caches DNS records only updates them every few days. This is not any kind of standard, and they can set this time anywhere from a few hours to several days. The slow updating of the servers cache is called propagation, since your websites DNS information is now being propagated across all DNS servers on the web. When this is finally complete, everyone can now visit your new website. Being that the cache time is different for all servers, as mentioned above, it can take anywhere from 36 to 72 hours for DNS changes to be totally in effect.

Как да разберем текущата версия на WordPress с SQL заявка

За да разберете текущата версия на WordPress без да имате директен достъп до админ частта, но имате достъп до базата данни, изпълнете следната SQL заявка:

SELECT option_value FROM `wp_options` WHERE `option_name` LIKE ‘%transient_update_core%’;

Заявката ще върне доста дълъг стринг подобен на този в който се съдържат текущата версия на инсталирания WordPress и последната версия налична на официалния сайт:

O:8:”stdClass”:3:{s:7:”updates”;a:2:{i:0;O:8:”stdClass”:5:{s:8:”response”;s:6:”latest”;s:3:”url”;s:24:”http://bg.wordpress.org/”;s:7:”package”;s:49:”http://bg.wordpress.org/wordpress-2.9.2-bg_BG.zip”;s:7:”current”;s:5:”2.9.2″;s:6:”locale”;s:5:”bg_BG”;}i:1;O:8:”stdClass”:5:{s:8:”response”;s:6:”latest”;s:3:”url”;s:30:”http://wordpress.org/download/”;s:7:”package”;s:40:”http://wordpress.org/wordpress-2.9.2.zip”;s:7:”current”;s:5:”2.9.2″;s:6:”locale”;s:5:”en_US”;}}s:12:”last_checked”;i:1268677761;s:15:”version_checked”;s:5:”2.9.2″;}

Какво е EV SSL (extended validation SSL)

SSL сертификат с extended validation е пак ssl серификат, който се издава срещу доста по щателна и задълбочена проверка. За сравнение за обикновен ssl сертификат се иска само проверка за собственост на домейна с потвърдителен меил. Предполага се, че тези сертификати са по сигурни и надеждни и по лесно печелят доверието на клиента. Имат лесно забележима цветната лента в адрес бара, докато обикновения ssl има само катинарче в долната част и много фишинг сайтове имат такъв обикновен ssl. Докато EV SSL-а ясно показва на посетителите, че организацията притежаваща сайта е била подложена на много сериозна проверка и е сертифицирана по най-строгите стандарти в индустрията. И заради всички тези екстри струва по скъпо и се издава по трудно и бавно. За такъв сертификат е необходимо да има официално регистрирана организация, която е собственик на домейна, както и потвърждаване на присъствието на адресите на организацията. Сертификати от това поколение поддържат почти всички браузъри, но не всеки ssl провайдър може да ги издава.

Как да разберем текущата версия на Joomla 1.5

Единият от начините да установим версията на вече инсталирана Joomla 1.5 е да се логнем в админ панела и да погледнем горе в дясно.

Другият е да отворим файла version.php който се намира в libraries/joomla. Редовете които ще ви кажат версията са следните:

.

/** @var int Main Release Level */
var $RELEASE = ‘1.5’;
/** @var int Sub Release Level */
var $DEV_LEVEL = ’10’;

.

Първият ред ни дава клона на Joomla, те биват 1.0 и 1.5. Вторият е версията на съответния клон. В този случай версията е 1.5.10.

Обработка на опашката в exim

За да листнете опашката:
exim -bp

За да изброите броя на съобщенията в опашката:
exim -bpc

За да изтриете съобщение от опашката:
exim -Mrm

За да изтриете всички съобщения в опашката:

exim -bp | awk ‘/^ *[0-9]+[mhd]/{print “exim -Mrm ” $3}’ | bash

exim -bp | exiqgrep -i | xargs exim -Mrm

Примери за употреба на find

find . -type f -size +10000 -exec ls -al {} \;
find . -atime +1 -type f -exec mv {} TMP \; # mv files older then 1 day to dir TMP
find . -name “-F” -exec rm {} \; # a script error created a file called -F
find . -exec grep -i “vds admin” {} \;
find . \! -name “*.Z” -exec compress -f {} \;
find . -type f \! -name “*.Z” \! -name “.comment” -print | tee -a /tmp/list
find . -name *.ini
find . -exec chmod 775 {} \;
find . -user xuser1 -exec chown -R user2 {} \;
find . -name ebtcom*
find . -name mkbook
find . -exec grep PW0 {} \;
find . -exec grep -i “pw0” {} \;
find . -atime +6
find . -atime +6 -exec ll | more
find . -atime +6 -exec ll | more \;
find . -atime +6 -exec ll \;
find . -atime +6 -exec ls \;
find . -atime +30 -exec ls \;
find . -atime +30 -exec ls \; | wc -l
find . -name auth*
find . -exec grep -i plotme10 {};
find . -exec grep -i plotme10 {} \;
find . -ls -exec grep ‘PLOT_FORMAT 22’ {} \;
find . -print -exec grep ‘PLOT_FORMAT 22’ {} \;
find . -print -exec grep ‘PLOT_FORMAT’ {} \;
find . -print -exec grep ‘PLOT_FORMAT’ {} \;
find ./machbook -exec chown 184 {} \;
find . \! -name ‘*.Z’ -exec compress {} \;
find . \! -name “*.Z” -exec compress -f {} \;
find /raid/03c/ecn -xdev -type f -print
find /raid/03c/ecn -xdev -path -type f -print
find / -name .ssh* -print | tee -a ssh-stuff
find . -name “*font*”
find . -name hpmcad*
find . -name *fnt*
find . -name hp_mcad* -print
find . -grep Pld {} \;
find . -exec grep Pld {} \;
find . -exec grep Pld {} \;
find . -exec grep PENWIDTH {} \; | more
find . -name config.pro
find . -name config.pro
find /raid -type d “.local_sd_customize” -print
find /raid -type d -name “.local_sd_customize” -print
find /raid -type d -name “.local_sd_customize” -ok cp /raid/04d/MCAD-apps/I_Custom/SD_custom/site_sd_customize/user_filer_project_dirs {} \;
find /raid -type d -name “.local_sd_customize” -exec cp /raid/04d/MCAD-apps/I_Custom/SD_custom/site_sd_customize/user_filer_project_dirs {} \;
find . -name xeroxrelease
find . -exec grep xeroxrelease {} \;
find . -name xeroxrelease
find . -name xeroxrelease* -print 2>/dev/null
find . -name “*release*” 2>/dev/null
find / -name “*xerox*” 2>/dev/null
find . -exec grep -i xeroxrelease {} \;
find . -print -exec grep -i xeroxrelease {} \;
find . -print -exec grep -i xeroxrelease {} \; > xeroxrel.lis
find . -exec grep -i xeroxrel {} \;
find . -print -exec grep -i xeroxrel {} \;
find . -print -exec grep -i xeroxrel {} \; | more
find /raid/03c/inwork -xdev -type f -print >> /raid/04d/user_scripts/prt_list.tmp
find . -exec grep ‘31.53’ {} \;
find . -ls -exec grep “31/.53” {} \; > this.lis
find . -print -exec grep “31/.53” {} \; > this.lis
find . -print -exec grep 31.53 {} \; > this.lis
find . -exec grep -i pen {} /;
find . -exec grep -i pen {} \;
find . -print -exec grep -i pen {} \; | more
find . -exec grep -i pen {} \;
find . -atime +6 -exec ll | more \;
find . -atime +6 -exec ll \;
find . -atime +6 -exec ls \;
find . -atime +30 -exec ls \;
find . -atime +30 -exec ls \; | wc -l
find . \! -name ‘*.Z’ -exec compress -f {} \;
find . -name ‘cache*’ -depth -exec rm {} \;
find . -name ‘cache*’ -depth -print | tee -a /tmp/cachefiles
find . -name ‘cache[0-9][0-9]*’ -depth -print | tee -a /tmp/cachefiles
find . -name ‘hp_catfile’ ‘hp_catlock’ -depth -print | tee -a /tmp/hp.cats
find . -name ‘hp_catfile’ -name ‘hp_catlock’ -depth -print | tee -a /tmp/hp.cats
find . -name ‘hp_cat*’ -depth -print | tee -a /tmp/hp.cats
find . -name ‘hp_cat[fl]*’ -depth -print | tee -a /tmp/hp.cats
find /raid -name ‘hp_cat[fl]*’ -depth -print
find . \! -name ‘*.Z’ -exec compress -f {} \;
find . -name ‘*’ -exec compress -f {} \;
find . -xdev -name “wshp1*” -print
find . -xdev -name “wagoneer*” -print
find . -name “xcmd” -depth -print
find /usr/contrib/src -name “xcmd” -depth -print
find /raid -type d -name “.local_sd_customize” -exec ls {} \;
find /raid -type d -name “.local_sd_customize” \
-exec cp /raid/04d/MCAD-apps/I_Custom/SD_custom/site_sd_customize/user_filer_project_dirs {} \;