Sponsored Content
Operating Systems OS X (Apple) 12-Core MacPro (2013) kernel_task over 1200% Post 303033967 by Neo on Monday 15th of April 2019 11:26:10 AM
Old 04-15-2019
Yes, I tried for many hours, a few times, sometimes for 20 minutes, etc, but I will try overnight again before lugging the beast to Apple.

Thanks for reminding me to try an "overnight unplugged" test before throwing in the towel.
This User Gave Thanks to Neo For This Post:
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Can I use a general printer(HP LaserJet 1200) on solaris?

can it be used? how to config it? thanks (4 Replies)
Discussion started by: cloudsmell
4 Replies

2. OS X (Apple)

kernel_task help

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

T5140 CPU Speed is 1200 Mhz or 1165 Mhz?

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

2013 Apple Mac Pro 2.7GHz 12 Core/64GB/256GB Flash/Dual AMD FirePro D700 6GB 6,1

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)

DiskSpeedTest 256GB OEM v. 960GB Transcend 855 SSD MacPro 2013, 12-Core, 64GB RAM

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! Upgrade to Catalina 10.15.3 Crashes MacPro (2013) - Will Not Boot !

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
lib::core::only(3)					User Contributed Perl Documentation					lib::core::only(3)

NAME
lib::core::only - Remove all non-core paths from @INC to avoid site/vendor dirs SYNOPSIS
use lib::core::only; # now @INC contains only the two core directories To get only the core directories plus the ones for the local::lib in scope: $ perl -Mlib::core::only -Mlocal::lib=~/perl5 myscript.pl To attempt to do a self-contained build (but note this will not reliably propagate into subprocesses, see the CAVEATS below): $ PERL5OPT='-Mlib::core::only -Mlocal::lib=~/perl5' cpan DESCRIPTION
lib::core::only is simply a shortcut to say "please reduce my @INC to only the core lib and archlib (architecture-specific lib) directories of this perl". You might want to do this to ensure a local::lib contains only the code you need, or to test an App::FatPacker tree, or to avoid known bad vendor packages. You might want to use this to try and install a self-contained tree of perl modules. Be warned that that probably won't work (see "CAVEATS"). This module was extracted from local::lib's --self-contained feature, and contains the only part that ever worked. I apologise to anybody who thought anything else did. CAVEATS
This does not propagate properly across perl invocations like local::lib's stuff does. It can't. It's only a module import, so it only affects the specific perl VM instance in which you load and import() it. If you want to cascade it across invocations, you can set the PERL5OPT environment variable to '-Mlib::core::only' and it'll sort of work. But be aware that taint mode ignores this, so some modules' build and test code probably will as well. You also need to be aware that perl's command line options are not processed in order - -I options take effect before -M options, so perl -Mlib::core::only -Ilib is unlike to do what you want - it's exactly equivalent to: perl -Mlib::core::only If you want to combine a core-only @INC with additional paths, you need to add the additional paths using -M options and the lib module: perl -Mlib::core::only -Mlib=lib # or if you're trying to test compiled code: perl -Mlib::core::only -Mblib For more information on the impossibility of sanely propagating this across module builds without help from the build program, see <http://www.shadowcat.co.uk/blog/matt-s-trout/tainted-love> - and for ways to achieve the old --self-contained feature's results, look at App::FatPacker's tree function, and at App::cpanminus's --local-lib-contained feature. AUTHOR
Matt S. Trout <mst@shadowcat.co.uk> LICENSE
This library is free software under the same terms as perl itself. COPYRIGHT
(c) 2010 the lib::core::only "AUTHOR" as specified above. perl v5.16.3 2013-02-12 lib::core::only(3)
All times are GMT -4. The time now is 10:03 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy