A Recipe for Efficiency? Some Principles of Power-aware Computing
HPL-2009-294 A Recipe for Efficiency? Some Principles of Power-aware Computing - Ranganathan, Parthasarathy Keyword(s): Abstract: Power and energy are emerging to be key design considerations across a spectrum of computing solutions, from supercomputers and datacenters, to handhelds and mobile computers. There has been a large body of work on managing power and improving energy efficiency, all of which can be summarized in two ... Full Report
Today I was reading some posts/news in efytimes.com, in that I found one post useful post, and felt it's good to post here so that if any more such commands are there then we can discuss.
Here is that useful post
Some Malicious Linux Commands You Should Be Aware Of (3 Replies)
This is a brief overview of where computing performance is heading. The exponential rise in CPU performance as predicted by Moore's law is apparently also true for individual components, at least when looking at historical data.
RAM / working memory
The following is an overview of the year in... (2 Replies)
Tim Bass
Thu, 15 Nov 2007 23:55:07 +0000
*I predict we may experience less*debates*on the use of the term “event cloud”*related to*CEP in the future, now that both IBM and Google* have made announcements about “cloud computing” and “computing cloud”, IBM Turning Data Centers Into ‘Computing... (0 Replies)
I have a .procmailrc file that includes a file named .rc.phplist. Within .rc.phplist is the following set of recipes:
:0
* $RECIP ?? ^^phplist@$DOMAIN
{
# Has this message already been sent? If so, delete it.
:0h
* ^X-Mailing-List:
/dev/null
:0cw
phplist/queue/.
:0... (18 Replies)
how efficient is it, and how practical is it to call outside programs in a shell script (bash) for small tasks?
for example, say i have a script that might preform many tasks, one of those tasks may require root access; rather than implementing inside the script a method to use su or sudo to... (11 Replies)
pmconfig(1M) System Administration Commands pmconfig(1M)NAME
pmconfig - Configure the Power Management system
SYNOPSIS
/usr/sbin/pmconfig [-r]
DESCRIPTION
The pmconfig utility sets the Power Management and suspend-resume configuration. User has permission to change Power Management configu-
ration using pmconfig only if he is allowed to do so according to PMCHANGEPERM keyword of /etc/default/power. User has permission to change
the suspend-resume configuration using pmconfig only if he is allowed to do so according to the CPRCHANGEPERM keyword of
/etc/default/power. See FILES section below for a description of the PMCHANGEPERM and CPRCHANGEPERM keywords of /etc/default/power.
Based on user permissions, pmconfig first resets the Power Management and/or suspend-resume state back to its default and then reads
the new Power Management and/or suspend-resume configuration from /etc/power.conf and issues the commands to activiate the new configu-
ration. The pmconfig utility is run at system boot. This utility can also be run from the command line after manual changes have been made
to the /etc/power.conf file. For editing changes made to the /etc/power.conf file to take effect, users must run pmconfig.
The preferred interface for changing Power Management and suspend-resume configuration is dtpower(1M).
OPTIONS
The following options are supported:
-r Reset Power Management and suspend-resume state to default and exit. User must have both Power Management and suspend-resume
configuration permission for this option.
EXIT STATUS
The following exit values are returned:
0 Upon successful completion
>0 An error occurred
FILES
/etc/power.conf System Power Management configuration file
/etc/default/power File that controls permissions for system's Power Management and suspend-resume features. The PMCHANGEPERM key-
board controls the Power Management configuration permissions, while the CPRCHANGEPERM keyword controls the sus-
pend-resume configuration permissions.
Allowed values are:
all Any user can change the configuration.
- No one except super-user can change the configuration.
<user1, user2,...> A user in this user list or a super-user can change the configuration. The user list is a space and/or comma (,)
separated list. You must enclose the list in < and > characters.
console-owner A user who owns the system console device node or a super-user can change the configuration.
The default values are PMCHANGEPERM=console-owner and CPRCHANGEPERM=console-owner.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWpmu |
+-----------------------------+-----------------------------+
|Interface stability |Unstable |
+-----------------------------+-----------------------------+
SEE ALSO svcs(1), powerd(1M), power.conf(4), svcadm(1M), attributes(5), smf(5), cpr(7), pm(7D)
Using Power Management
NOTES
The pmconfig service is managed by the service management facility, smf(5), under the service identifier:
svc:/system/power:default
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
DIAGNOSTICS
If the program cannot open the configuration file, it prints an error message to standard error. If the program encounters a syntax error
in the configuration file, it prints an error message and the line number of the error in the configuration file. It then skips the rest
of the information on that line and processes the next line. Any configuration information already processed on the line containing the
error is used. If user does not have permission to change Power Management and/or suspend-resume configuration, and configuration file has
entries for which user doesn't have permission, it process the entries for which user has permissions and prints error on rest.
SunOS 5.10 12 Aug 2004 pmconfig(1M)
