File: control

package info (click to toggle)
idle3-tools 0.9.1-7
  • links: PTS, VCS
  • area: main
  • in suites: forky, sid, trixie
  • size: 196 kB
  • sloc: ansic: 1,228; makefile: 105
file content (42 lines) | stat: -rw-r--r-- 1,703 bytes parent folder | download | duplicates (2)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
Source: idle3-tools
Section: admin
Priority: optional
Maintainer: Debian QA Group <packages@qa.debian.org>
Build-Depends: debhelper-compat (= 13)
Standards-Version: 4.5.0
Rules-Requires-Root: no
Homepage: http://idle3-tools.sourceforge.net/
Vcs-Browser: https://salsa.debian.org/debian/idle3-tools
Vcs-Git: https://salsa.debian.org/debian/idle3-tools.git

Package: idle3-tools
Architecture: any
Depends: ${shlibs:Depends}, ${misc:Depends}
Description: change the idle3 timer of recent Western Digital Hard Disk Drives
 Idle3-tools provides a linux/unix utility that can disable, get and
 set the value of the infamous idle3 timer found on recent Western
 Digital Hard Disk Drives.
 .
 It can be used as an alternative to the official wdidle3.exe
 proprietary utility, without the need to reboot in a DOS environment.
 .
 A power off/on cycle of the drive will still be mandatory for new
 settings to be taken into account.
 .
 Modern Western Digital "Green" Drives include the Intellipark feature
 that stops the disk when not in use.
 .
 Unfortunately, the default timer setting is not perfect on linux/unix
 systems, including many NAS, and leads to a dramatic increase of the
 Load Cycle Count value (SMART attribute #193). With the default timer
 setting, the drive will spin down *every eight seconds* if idle and
 this may get the spindle motor to burn out in a few months or so.
 .
 If you have a Western Digital EADS or EARS drive, please check you
 SMART information before it's too late by running the following
 command:
 .
  sudo smartctl -A /dev/sda | grep "^193"
 .
 If the Load cycle count (which is in the last column) exceeds 1000,
 you're probably affected by the idle3 timer problem.