deb/hd-idle
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Import Debian changes 1.05+ds-2

Browse Source 
hd-idle (1.05+ds-2) unstable; urgency=medium
.
  * No-change, Source-only upload
.
hd-idle (1.05+ds-1) unstable; urgency=medium
.
  * Initial release. Closes: #924749
This commit is contained in:
Alexandre Mestiashvili
2019-09-19 10:13:38 +02:00
committed by geos_one
parent 28f0bb50f5 7527bfa483
commit 05b82773a0
43 changed files with 1194 additions and 3406 deletions
Download Patch File Download Diff File Expand all files Collapse all files

35
debian/hd-idle.default vendored
View File

@@ -1,7 +1,15 @@
# defaults file for hd-idle
# start hd-idle automatically?
START_HD_IDLE=false
## Debian specific defaults for hd-idle
# In order to make init.d script and systemd service consistent, hd-idle
# defaults file supports only one option - HD_IDLE_OPTS.
# Don't start hd-idle by defaulit. By specifying "-h" in HD_IDEL_OPTS,
# hd-idle daemon will print usage and successfully exit both for systemd
# and systemv scripts
# properly update HD_IDLE_OPTS in order to star hd-idle
HD_IDLE_OPTS="-h"
# hd-idle command line options
# Options are:
@@ -12,20 +20,6 @@ START_HD_IDLE=false
# parameter. This can also be a symlink
# (e.g. /dev/disk/by-uuid/...)
# -i <idle_time> Idle time in seconds.
# -c <command_type> Api call to stop the device. Possible values are "scsi"
# (default value) and "ata".
# -p <power_condition>
# Power condition to send with the issued SCSI START STOP UNIT command. Possible values
# are `0-15` (inclusive). The default value of `0` works fine for disks accessible via the
# SCSI layer (USB, IEEE1394, ...), but it will *NOT* work as intended with real SCSI / SAS disks.
# A stopped SAS disk will not start up automatically on access, but requires a startup command for reactivation.
# Useful values for SAS disks are `2` for idle and `3` for standby.
# -s symlink_policy Set the policy to resolve symlinks for devices.
# If set to "0", symlinks are resolve only on start.
# If set to "1", symlinks are also resolved on runtime
# until success. By default symlinks are only resolve on start.
# If the symlink doesn't resolve to a device, the default
# configuration will be applied.
# -l <logfile> Name of logfile (written only after a disk has spun
# up). Please note that this option might cause the
# disk which holds the logfile to spin up just because
@@ -35,8 +29,9 @@ START_HD_IDLE=false
# this option should not cause any additional spinups.
#
# Options not exactly useful here:
# -t <disk> Spin-down the specified disk immediately and exit.
# -d Debug mode. It will print debugging info to
# stdout/stderr (/var/log/syslog if started as with systemctl)
# -t <disk> Spin-down the specfified disk immediately and exit.
# -d Debug mode. This will prevent hd-idle from
# becoming a daemon and print debugging info to
# stdout/stderr
# -h Print usage information.
#HD_IDLE_OPTS="-i 180 -l /var/log/hd-idle.log"
#HD_IDLE_OPTS="-i 180 -l /var/log/hd-idle.log"