mirror of
https://github.com/morgan9e/systemd
synced 2026-04-14 16:37:19 +09:00
8efc2c1608
To make this easier to understand, let's always log (at debug level) when we accept or reject each device: /swapfile: detection of swap file offset on Btrfs is not supported /swapfile: is a candidate device. /dev/zram0: ignoring zram swap /dev/vdb: ignoring device with lower priority /dev/vdc: ignoring device with lower usable space ... If we know that hibernation will fail, refuse. This includes cases where /sys/power/resume is set and doesn't match any device, or /sys/power/resume_offset is set and we're not on btrfs and it doesn't match. If /sys/power/resume is not set at all, we still accept the device with the highest priority (see6d176522f5and88bc86fcf8) Tested cases: 1. no swap active → refuse 2. just zram swap active → refuse 3. swapfile on btrfs with /sys/power/resume{,_offset} set → OK 4. swapfile on btrfs with /sys/power/resume set, offset not set → refuse 5. swapfile on btrfs with /sys/power/resume set to nonexistent device, offset set → refuse 6. /sys/power/resume not set, offset set, candidate exists → OK (*) 7. /sys/power/resume not set, offset not set, candidate exists → OK (*) I think this should fail, but I'm leaving that for the next commit.
systemd - System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.