Your Drupal cron might be currently failing simply because your server time is ahead or behind

Per instructions on http://drupal.org/cron I've added the the following line to server's cron job:

# crontab -e

44 * * * * /usr/bin/lynx -source http://akyl.net/cron.php

The time on the upper right corner of my MacPro's display was showing exactly 1.43 pm. After one minute passed I checked the status of cron on http://akyl.net/admin/reports/status and, alas, cron didn't yet run. Googling gave lot's of long discussions like one on http://drupal.org/node/143519 just quickly glancing on which gets you confused with lot's of possible reasons for the failure.

Tinyurl is not tiny anymore

I've just setup http://akyl.net, a Drupal 6 website, with nodes configured to automatically be announced on Twitter, and posted my first entry: http://akyl.net/easy-way-extending-linux-logical-volumes. Everything looks great, but one thing.

An easy way of extending Linux logical volumes

Some vendors like 1and1 deliver Linux servers with pre-configured partitioning scheme with reduced logical volumes. A Logical Volume Manager (LVM) manager is here to help us.

First we need to see if we have an extra space at all by running pvs command on Ubuntu and pvs -av on CentOS (http://www.centos.org/docs/5/html/Cluster_Logical_Volume_Manager/move_ne... recommends runing pvs -o+pv_used, however it did not work on CentOS 5.8)

root@host:~# pvs

Pages

Subscribe to Front page feed