05-24-2011
Several have pointed out that we seem to be ignoring the matter of cost. In fact, TCO is one of our main motivations.
We have been a strictly Linux shop. Over the years, we have gathered the impression from colleagues using commercial Unixen that we were spending much more time on maintenance and recovery than they were.
Since workstation use has fallen dramatically over the past decade, you can find some really good deals on second-hand IA64/POWER workstations. As for licenses, Solaris is free for noncommercial use, and HP-UX and AIX licenses are tied to the machine.
8 More Discussions You Might Find Interesting
1. Programming
I'm kinda fed up with all the theoretical side of the programming. now i'd love to participate in some project dealing with C network programming under Unix. My question is: is there any online programs or projects where i can really participate? Any other suggestions how to build up practical... (1 Reply)
Discussion started by: solvman
1 Replies
2. UNIX for Advanced & Expert Users
Hi everybody,
I'm kinda fed up with all the theoritical part of programming. I wonder if there is any online project or something where i can participate to practice my skills? Any other suggestions how to build up practical side of Unix C programming?
Thank you all. (1 Reply)
Discussion started by: solvman
1 Replies
3. UNIX for Dummies Questions & Answers
Is Solaris still very hardware dependent? As in it is used mostly on SUN workstations and servers?
What about IBM's AIX? Does it only work on IBM machines?
Which is more popular and are there performance or usage differences? (1 Reply)
Discussion started by: CapsuleCorpJX
1 Replies
4. Solaris
hello
has anyone built a script that compares 2 Solaris servers? CPU, memory, swap, memory variables in /etc/system, Solaris version
Could you please advise on how to make such a comparaison?
thanks (9 Replies)
Discussion started by: melanie_pfefer
9 Replies
5. AIX
I have been in IT for around 7 years now and have benefited greatly from Open Source as well as free commercial offerings like Vmware Server that allow me to setup virtual environments and get some hands on time with different OS's and software.
I am starting a new job in a few weeks which has... (5 Replies)
Discussion started by: supercrazy1
5 Replies
6. AIX
Hello,
I have a directory which suddenly got filled up 100% from 70% ; (this is an oracle directory which has application and database in it ORACLE EBS)
I do make cold backups, last month when I made cold backup of the directory /oratec the tar zip file was 31GB and this month when i made the... (5 Replies)
Discussion started by: filosophizer
5 Replies
7. Solaris
I'd like to share some experiences and what I found for NIS migration from Solaris 8 NIS to Linux platform.
I'm not an expert for both platforms, it's just when I tested both systems and found something really tricky. That might takes a lot of time for you to find the root cause. So, I think I can... (11 Replies)
Discussion started by: bestard
11 Replies
8. UNIX for Beginners Questions & Answers
Good day to all.
I'm relatively new in using the Sun Solaris OS. I would like to request your expertise in helping to solve a problem that I have at work. Not sure if this has been asked before but I have tried searching through the internet to no avail.
Basically I have 2 sun solaris... (8 Replies)
Discussion started by: Fossil_84
8 Replies
TIME(2) Linux Programmer's Manual TIME(2)
NAME
time - get time in seconds
SYNOPSIS
#include <time.h>
time_t time(time_t *t);
DESCRIPTION
time() returns the time as the number of seconds since the Epoch, 1970-01-01 00:00:00 +0000 (UTC).
If t is non-NULL, the return value is also stored in the memory pointed to by t.
RETURN VALUE
On success, the value of time in seconds since the Epoch is returned. On error, ((time_t) -1) is returned, and errno is set appropriately.
ERRORS
EFAULT t points outside your accessible address space.
CONFORMING TO
SVr4, 4.3BSD, C89, C99, POSIX.1-2001. POSIX does not specify any error conditions.
NOTES
POSIX.1 defines seconds since the Epoch using a formula that approximates the number of seconds between a specified time and the Epoch.
This formula takes account of the facts that all years that are evenly divisible by 4 are leap years, but years that are evenly divisible
by 100 are not leap years unless they are also evenly divisible by 400, in which case they are leap years. This value is not the same as
the actual number of seconds between the time and the Epoch, because of leap seconds and because system clocks are not required to be syn-
chronized to a standard reference. The intention is that the interpretation of seconds since the Epoch values be consistent; see
POSIX.1-2008 Rationale A.4.15 for further rationale.
SEE ALSO
date(1), gettimeofday(2), ctime(3), ftime(3), time(7)
COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
Linux 2011-09-09 TIME(2)