is there any way to find when the server was built i mean when the os was loaded on the machine..both linux and solaaris servers

is there any way to find when the server was built i mean when the os was loaded on the machine..both linux and solaaris servers..need exact date when the server was built
sants_ppAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Smart_ManCommented:
is this helpful for you ?

http://linux.die.net/man/1/uptime

waiting for your reply
0
TintinCommented:
Assuming your hostname hasn't changed, then on Solaris looking at the timestamp of

/etc/hostname.*

will give you the timestamp when the server was installed.

0
sants_ppAuthor Commented:
hi smart man,
   uptime tells how long system has been running..but if we rebooted the server after os installtion ..asuume 10 days before..it gives output as 10 days 15 mins like that..we cannot able to determine exact date and time
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

arrkerr1024Commented:
I think you'd have to figure out a good list of files that are probably stamped with the load time, and just take the oldest.  The /etc/hostname is a good idea, but obviously could easily have changed as well.  Config files for things that are set once and not changed would be a good bet...

On redhat you could check for /root/anaconda-ks.cfg which is a log left by the installer, but could have been deleted by a prior admin.  I don't know if solaris writes an installation log to the filesystem?
0
Smart_ManCommented:
sorry for confusing the uptime with the installation date.

i hope this one help , could not try it myself

http://www.unix.com/showthread.php?t=20030

waiting for your eply
0
casemanagerCommented:
Hello Smart man,

I don't think that checking the last logs or the /var/adm/messages files can help us in this case. These files are regularly rotated/truncated ( at least on a production system) -  so the information cannot be trusted.

Checking time stamp on /etc/hostname.* is a much better idea as it is not often that the hostname chnange is made on the prod server.

regards,
Casemanager
0
omarfaridCommented:
if you look at the binaries dates in /usr/bin then you will see a common date and time between them which is the installation date.
0
Brian UtterbackPrinciple Software EngineerCommented:
Actually, looking at the binaries on /usr/bin is a almost the right way. The key is not to look at the modification time,
which is when the file was written, unless the file is being installed, or restored from archive,  in which case the mod
time is the time the file was modified before it was archived. So, that means that the mod time doesn't tell you when the
files were installed, it tells you the time they were created, at least for the system files, which is not what you want.

What you are looking for is the "ctime", which was the time the inode for the file was last modified. SO, what you want to
do is cd into /usr/bin and then run "ls -ltc". The earliest date on the list is the latest time that the system could have been
installed, and almost certainly is the time it actually was installed.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Smart_ManCommented:
it is really a should-considered point for the OS makers. since nothing is so accurate. i have seen a workaround solution more accuret for the MS OS. ofcourse that is assuming the machine date was right at the installation time.

maybe a better approach is to try searching for operating duration , as a new concept, rather than the machine date/time stamp at the installation or the up time or any other logs/file timestamps.

0
arrkerr1024Commented:
Good point about the machine clock being right at installation.  Oddly enough more times than not when I've been given a machine to load I get it loaded up and when I sync the time for the first time it can literally be years off.  Especially on a machine that may have been sitting around waiting for a reload and the battery died and it went back to 1969.
0
Smart_ManCommented:
I dunno if such a concept already exist or not . but i am glad to invent it here in the EE if it is not.I think it might be called . accumulated up-time. or operating time as the most accurate measure for such issue. which can be calculated to estimate the real time of installation.

all other work around measurements wont give the accurate timestamp.


waiting for your reply.
0
sants_ppAuthor Commented:
cannot able to find exact date.bur aswers are very useful
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Unix OS

From novice to tech pro — start learning today.