10-05-2015
Quote:
Originally Posted by
gandolf989
I find this statement really odd. The reason why people liked RISC chips is because, at one point, they had faster clock speeds that CISC chips. However, since then CISC chips have become significantly faster, run at a higher clock frequency and can do more with each clock cycle. Hence anything RISC is in the past.
Which is why the average North American now carries one or more RISC processors at all times, has several more in their home, and is increasingly using them for all computing.
9 More Discussions You Might Find Interesting
1. Solaris
Hello Guys, im new to this forum. Im from UK and ive recently completed my SCSA I & II and also got trained in Veritas Suite (Veritas Volume Manager and Veritas Clusters, Veritas NetBackup), SAN Configuration. I was trying to get a break as a junior sun solaris admin. I am applying for the jobs... (1 Reply)
Discussion started by: megadeth
1 Replies
2. UNIX for Dummies Questions & Answers
the root shell has been changed in the file /etc/passwd, basically pointing to an incorrect directory. So now every time we login as 'su' I get the message
'su: no shell' so we can't login as superuser.
Is there an easy way to rectify this? please use step by step instructions/commands -
I... (4 Replies)
Discussion started by: homechoice
4 Replies
3. AIX
Hello:
NOOB here. I attempted to use smit mkcd. Failed on first attempt, not enough space. 2nd attempt tried to place iso on /usr, not enough space there. Cleanup ran for about 5 minutes after aborting. Now AIX won't boot. LCD display on 7029-6E3 says: 0517 MOUNT /USR. Attempted to boot from CD... (11 Replies)
Discussion started by: bbird
11 Replies
4. Solaris
Hi all - I have an issue with our (way old) single processor SunFire 280R, running Solaris 9.0.4.
It won't boot even after multiple power cycles. There was a power outage last week end in the computer room, so this might have to do.
In normal boot mode, the screen shows a single line :
... (5 Replies)
Discussion started by: bostella
5 Replies
5. UNIX for Dummies Questions & Answers
I've screwed something up in my sshd_config apparently, because I can't ssh with root anymore.
I had disabled root login for security reasons, but then my ssh credentials with full administrative privelges stopped working. So then I reenabled root login (and reset ssh), but root now isn't... (3 Replies)
Discussion started by: cquarry
3 Replies
6. UNIX for Advanced & Expert Users
Can someone tell me why pkill won't work on firefox anymore? (11 Replies)
Discussion started by: cokedude
11 Replies
7. Slackware
We used to use Slackware, but then moved all our servers to Ubuntu Linux.
Does anyone use Slackware anymore? (8 Replies)
Discussion started by: Neo
8 Replies
8. Programming
(Apologies for any typos.)
OSX 10.12.3 AND Windows 10.
This is for the serious Python experts on at least 3.5.x and above...
In script format sys.stdout.write() AND sys.stderr.write() seems to work correctly.
Have I found a serious bug in the interactive sys.stdout.write() AND... (2 Replies)
Discussion started by: wisecracker
2 Replies
9. UNIX for Beginners Questions & Answers
Can anyone offer any advice on how to modify the script below to work on a new system we have, that has no graphics capability? We admin the system through a serial RAS device. I've tried running the below script through the RAS and through an ssh -X session. It failed with something like "GTK... (3 Replies)
Discussion started by: yelirt5
3 Replies
clock(3C) Standard C Library Functions clock(3C)
NAME
clock - report CPU time used
SYNOPSIS
#include <time.h>
clock_t clock(void);
DESCRIPTION
The clock() function returns the amount of CPU time (in microseconds) used since the first call to clock() in the calling process. The time
reported is the sum of the user and system times of the calling process and its terminated child processes for which it has executed the
wait(3C) function, the pclose(3C) function, or the system(3C) function.
RETURN VALUES
Dividing the value returned by clock() by the constant CLOCKS_PER_SEC, defined in the <time.h> header, will give the time in seconds. If
the process time used is not available or cannot be represented, clock returns the value (clock_t) -1.
USAGE
The value returned by clock() is defined in microseconds for compatibility with systems that have CPU clocks with much higher resolution.
Because of this, the value returned will wrap around after accumulating only 2147 seconds of CPU time (about 36 minutes).
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Interface Stability |Standard |
+-----------------------------+-----------------------------+
|MT-Level |MT-Safe |
+-----------------------------+-----------------------------+
SEE ALSO
times(2), popen(3C), system(3C), wait(3C), attributes(5), standards(5)
SunOS 5.10 24 Jul 2002 clock(3C)