The year 2038 problem : Unix Millennium Bug, Y2K38 or Y2.038K

The year 2038 problem : Unix Millennium Bug, Y2K38 or Y2.038K

Hey friends,
some systems which are using unix timestamp at various step may cause error after 2038.
The problem affects all software and systems that stores both system time as a signed 32-bit integer.

For such sytems time beyond 19 Jan 2038  will "wrap around" and be stored internally as a negative number, which will counted as a date in 1901 rather than 2038.

Affect of this in PHP:
php's strtotime function fails to create timestamp if date is above then year 2038 and the server stores timestamp with 32 bit signed integer.
(my local packages fails to create timestamp )
Solution :
There is no particular system solution have been arrived yet for this.
First solution from some people is to use unsigner 32 bit integer for time stamp so it will increase the availibility of time stamp till 2106 but still after that it will not useful and may create other problems in system.
same way using 64 bit signed variable for timestamp can increase the available time stamp range upto minimum 300000 years.
System that may affect due to this:

• file systems (like many inode file systems still in use)
• databases (that have 32 bit time fields)