Sponsored Content
Special Forums Hardware How to remove fan from cpu fan chassis? Post 302809259 by lchunleo on Sunday 19th of May 2013 02:34:34 AM
Old 05-19-2013
thanks, i just unable to see the screw or any sort, no matter which orientation i am looking at....but nevertheless thanks alot..
 

7 More Discussions You Might Find Interesting

1. BSD

Fan control

Hi all, Is there any way that I can get some control over th fan in my Evo N400C laptop running OpenBSD 4.0? Right now the fan is running constantly and it woulf be nice if it could be quiet sometime. (1 Reply)
Discussion started by: Timmy66
1 Replies

2. Hardware

Fan Tray for Sunfire T2000

Recently the rear fan assembly of one of our T2000 servers went faulty. I could replace it immediately with the one from a currently powered off standby machine. But now this one has to be replaced. So I got a quote from our supplier who charges EUR 776 for a new spare part or EUR 405 (all... (0 Replies)
Discussion started by: hergp
0 Replies

3. What is on Your Mind?

I just ordered a Mini-Box with no fan!

I just ordered a Mini-Box M350 with a Mini-ITX Intel DM510MO motherboard. NO FAN! I've come to hate the wine of spinning mechanisms in PCs in my quiet home. This one is for surfing the web in my living room (instead of using this laptop), so it doesn't really need much power. If I do... (1 Reply)
Discussion started by: KenJackson
1 Replies

4. Solaris

Fan failure

would Solaris 10 shutdown automatically if both CPU fans fail? (7 Replies)
Discussion started by: orange47
7 Replies

5. Hardware

How to replace the fan in the HP J6000?

Hi all, it is me again..now my HP J6000 fan is spoilt. Based on the error, i suspected it is Fan 1 in the power supply, however there is 3 fans in the power supply, how do i know which is Fan 1? Thanks for your response regards (2 Replies)
Discussion started by: lchunleo
2 Replies

6. Solaris

Sun Fire V210 CPU Fan Temp too high?

Hey, I have a V210 with a failed CPU fan. The temperature is currently at 84C and I've been asked to wait a few weeks before replacing as its a production system and it cant be shut down yet. Is it too hot? Do I risk killing the CPU at this temp? Its been like this for a few weeks now... (5 Replies)
Discussion started by: magarvo
5 Replies

7. Solaris

Sun v215 Fan Speed

Hi all, I made some calculations and it seems that fans are working more than they supposed to keep the internals at the specified values. Is there a way to adjust this ? I have 2 approaches ; -from ALOM sc|ok prompt -from Solaris 10 or -from a HW Switch I am pretty sure that... (5 Replies)
Discussion started by: y33t
5 Replies
sort(3perl)						 Perl Programmers Reference Guide					       sort(3perl)

NAME
sort - perl pragma to control sort() behaviour SYNOPSIS
use sort 'stable'; # guarantee stability use sort '_quicksort'; # use a quicksort algorithm use sort '_mergesort'; # use a mergesort algorithm use sort 'defaults'; # revert to default behavior no sort 'stable'; # stability not important use sort '_qsort'; # alias for quicksort my $current; BEGIN { $current = sort::current(); # identify prevailing algorithm } DESCRIPTION
With the "sort" pragma you can control the behaviour of the builtin "sort()" function. In Perl versions 5.6 and earlier the quicksort algorithm was used to implement "sort()", but in Perl 5.8 a mergesort algorithm was also made available, mainly to guarantee worst case O(N log N) behaviour: the worst case of quicksort is O(N**2). In Perl 5.8 and later, quicksort defends against quadratic behaviour by shuffling large arrays before sorting. A stable sort means that for records that compare equal, the original input ordering is preserved. Mergesort is stable, quicksort is not. Stability will matter only if elements that compare equal can be distinguished in some other way. That means that simple numerical and lexical sorts do not profit from stability, since equal elements are indistinguishable. However, with a comparison such as { substr($a, 0, 3) cmp substr($b, 0, 3) } stability might matter because elements that compare equal on the first 3 characters may be distinguished based on subsequent characters. In Perl 5.8 and later, quicksort can be stabilized, but doing so will add overhead, so it should only be done if it matters. The best algorithm depends on many things. On average, mergesort does fewer comparisons than quicksort, so it may be better when complicated comparison routines are used. Mergesort also takes advantage of pre-existing order, so it would be favored for using "sort()" to merge several sorted arrays. On the other hand, quicksort is often faster for small arrays, and on arrays of a few distinct values, repeated many times. You can force the choice of algorithm with this pragma, but this feels heavy-handed, so the subpragmas beginning with a "_" may not persist beyond Perl 5.8. The default algorithm is mergesort, which will be stable even if you do not explicitly demand it. But the stability of the default sort is a side-effect that could change in later versions. If stability is important, be sure to say so with a use sort 'stable'; The "no sort" pragma doesn't forbid what follows, it just leaves the choice open. Thus, after no sort qw(_mergesort stable); a mergesort, which happens to be stable, will be employed anyway. Note that no sort "_quicksort"; no sort "_mergesort"; have exactly the same effect, leaving the choice of sort algorithm open. CAVEATS
As of Perl 5.10, this pragma is lexically scoped and takes effect at compile time. In earlier versions its effect was global and took effect at run-time; the documentation suggested using "eval()" to change the behaviour: { eval 'use sort qw(defaults _quicksort)'; # force quicksort eval 'no sort "stable"'; # stability not wanted print sort::current . " "; @a = sort @b; eval 'use sort "defaults"'; # clean up, for others } { eval 'use sort qw(defaults stable)'; # force stability print sort::current . " "; @c = sort @d; eval 'use sort "defaults"'; # clean up, for others } Such code no longer has the desired effect, for two reasons. Firstly, the use of "eval()" means that the sorting algorithm is not changed until runtime, by which time it's too late to have any effect. Secondly, "sort::current" is also called at run-time, when in fact the compile-time value of "sort::current" is the one that matters. So now this code would be written: { use sort qw(defaults _quicksort); # force quicksort no sort "stable"; # stability not wanted my $current; BEGIN { $current = print sort::current; } print "$current "; @a = sort @b; # Pragmas go out of scope at the end of the block } { use sort qw(defaults stable); # force stability my $current; BEGIN { $current = print sort::current; } print "$current "; @c = sort @d; } perl v5.14.2 2010-12-30 sort(3perl)
All times are GMT -4. The time now is 04:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy