How to run cron jobs on even/odd days, minutes etc..

Ever wondered how to start a cron job on even/odd minute/day/hour ?

Here are some examples:

Example1: You want to run job on even/odd minute:

0-59/2 * * * * /path/to/evenjob.sh
1-59/2 * * * * /path/to/oddjob.sh

Example2: You want to run job in 10th minutie of every even/odd hour:

10 0-23/2 * * * /path/to/evenjob.sh
10 1-23/2 * * * /path/to/oddjob.sh

Example3: You want to run job at 5pm every even/odd date

0 17 2-31/2 * * /path/to/evenjob.sh
0 17 1-31/2 * * /path/to/oddjob.sh

If you dont clearly remember the positions of the minutes/hours/days you can find them in this man page:

man 5 crontab

here is a snippet from it:


field allowed values
minute 0-59
hour 0-23
day of month 1-31
month 1-12 (or names, see below)
day of week 0-7 (0 or 7 is Sun, or use names)

How to access IPv6 IP address from web browser

These days I am playing with IPv6 and tried to access few sites directly by IP address.

It looks like the browsers are trying to interpret the IPv6 address as name:port and the connection of course fail.

If you type directly in the browser, for example:

http://2a02:2e0:3fe:100::8

you will get error message.

If you want this to be interpreted as IPv6 address you will have to type the address like this:

http://[2a02:2e0:3fe:100::8]

I tested this on Linux with the following browsers:

Firefox
Opera
Google Chrome

CentOS 5 / RedHat Enterprise Linux (RHEL) 5 not IPv6 ready

These days I am trying to start using IPv6 on CentOS 5, but unfortunately I found that this distro is not exactly ready to run IPv6. What is the main problem for me: The kernel version coming with the distro is not, I repeat it is NOT, capable of doing connection tracking, which is very very bad.
We are being brought back in the days of kernel 2.2 and ipchains.
Probably some of you remember how crippled it was, compared to 2.4 and 2.6 + iptables.

Well it looks like the users of RHEL 5 are screwed (at least for now) even though they are paying.
In this bug report,

https://bugzilla.redhat.com/show_bug.cgi?id=243739

the RH developers basically say that backporting of xtables to kernel 2.6.18 is not possible, which sounds very bad for me. They can at least try to release a newer kernel version even though this is against the versioning policy accepted by RedHat, but you have to agree that this is too expensive distro and to not support IPv6.
They recommend building kernel from source with enabled IPv6 connection tracking features.
Come on guys what I am paying for, for building my custom kernels ?