04-16-2019
The 12-core mega beast is now in the hands of Apple iCare waiting for their phone call.
They could not find an entry for a 12-core MacPro in their system so they had to register it into the system as an 8-core machine.
Let's see what news Apple brings..... they said they would contact me in two or three days.
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
can it be used?
how to config it?
thanks (4 Replies)
Discussion started by: cloudsmell
4 Replies
2. OS X (Apple)
I installed 10.5 (Leopard) on my G4 733 Mhz (after minor tampering with the install package, just switched a boolean FALSE to TRUE).
Everything works fine after startup, but once I sleep the computer and wake it back up, kernel_task starts using at as much CPU runtime as it can, as in past 90%.... (0 Replies)
Discussion started by: peter.story
0 Replies
3. Solaris
Hi bros,
CPU speed of Sun Sparc Enterprise T5140 in data sheet is 1200 Mhz. Why it shows in "prtdiag -v" command each thread just has speed at 1165 Mhz.
Thank you,
tien86 (4 Replies)
Discussion started by: tien86
4 Replies
4. Hardware
Hey MacPro users.
I just bought a refurbished 13-Core MacPro with 64GB of RAM for a cybersecurity gaming project I'm working on. Could not wait for the new MacPro in 2019, so this will have to do:
2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1
Now, I'm... (0 Replies)
Discussion started by: Neo
0 Replies
5. OS X (Apple)
Before Upgrade:
https://www.unix.com/members/1-albums177-picture1220.png
After Upgrade:
https://www.unix.com/members/1-albums177-picture1221.png (0 Replies)
Discussion started by: Neo
0 Replies
6. OS X (Apple)
WARNING!
Just upgraded my MacPro (2013) from Catalina 10.15.2 to 10.15.3.
After the routine download and restart for upgrade installation, the Mac would not boot. Totally crashed.
Now, I'm in the process of a 15 hour restore from my last time machine backup.
I'm not very happy with... (3 Replies)
Discussion started by: Neo
3 Replies
GCORE(1) General Commands Manual GCORE(1)
NAME
gcore - get core image of running process
SYNOPSIS
gcore [-s][-c core] pid
DESCRIPTION
gcore creates a core image of each specified process, suitable for use with adb(1). By default the core image is written to the file
<pid>.core.
The options are:
-c Write the core file to the specified file instead of <pid>.core.
-s Stop the process while creating the core image and resume it when done. This makes sure that the core dump will be in a consistent
state. The process is resumed even if it was already stopped. Of course, you can obtain the same result by manually stopping the
process with kill(1).
The core image name was changed from core.<pid> to <pid>.core to prevent matching names like core.h and core.c when using programs such as
find(1).
FILES
<process-id>.core The core image.
BUGS
If gcore encounters an error while creating the core image and the -s option was used the process will remain stopped.
Swapped out processes and system processes (the swapper) may not be gcore'd.
4.2 Berkeley Distribution April 15, 1994 GCORE(1)