Dear Fellow Energy Savers:
I believe that some enterprise (and residential) PCs cannot be put to sleep without compromising a service. In some cases, a centralized (e.g., Verdiem Surveyor) control of power management settings and wake/sleep state may solve the problem. But, in some cases it may not. I suggest that the following may be cases requiring a PC (this includes laptops) to remain powered on:
1) Sharing files and having these files be both discoverable and accessible to others (e.g., Microsoft Network Neighborhood and P2P)
2) Being able to immediately respond (e.g., alert a user via an audio signal) to incoming communications such as tweets, IMs, IP phone calls, etc.
3) Maintaining secure connections and not having to constantly reconnect (e.g., VPNs and SSH)
4) Being able to offer and maintain remote desktop services (e.g., on the other side of a NAT where a wake-up message may not flow)
5) Being remotely manageable (e.g., responding to SNMP GETs)
6) Being discoverable to determine existence of resources (e.g., uPnP)
Is this a complete list? A correct list? Even close? I look forward to your shared insights on why some PCs just cannot be put to sleep without compromising a service, and what possibly could be done about the situation (i.e., to enable sleep).
Here is what I am doing:
http://www.csee.usf.edu/~christen/energy/main.html.
Regards,
Ken Christensen
Department of Computer Science and Engineering
University of South Florida
Phone: (813) 974-4761
Homepage:
http://www.csee.usf.edu/~christen
Email:
christen@csee.usf.edu
