Bug 949702
| Summary: | Need appropriate timeout setting in /etc/crypttab | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stephen John Smoogen <smooge> | |
| Component: | systemd | Assignee: | systemd-maint | |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | medium | |||
| Version: | 19 | CC: | agk, bruno, g.kaviyarasu, gmazyland, harald, johannbg, jonathan, kparal, lnykryn, metherid, mkolman, msekleta, notting, okozina, pfrields, plautrba, sbueno, stickster, systemd-maint, vanmeeuwen+fedora, vpavlin, zbyszek | |
| Target Milestone: | --- | Keywords: | Reopened | |
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | systemd-201-2.fc18.6 | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 951261 (view as bug list) | Environment: | ||
| Last Closed: | 2013-04-27 03:12:45 UTC | Type: | Bug | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
|
Description
Stephen John Smoogen
2013-04-08 19:18:05 UTC
Smooge means bug 868421 I think. Yes bug 868421. I got cc'd on the other one and chose that number by mistake. My apologies. I changed my mind on this one. If they want a default of no timeout then that's a change that belongs in cryptsetup -- not anaconda or blivet. Feel free to try to convince me otherwise. Moving the bug to cryptsetup... cryptsetup itself has no timeout as default from the beginning. But /etc/crypttab is now handled by systemd-cryptsetup unit generator. So let's reassign it to the proper systemd intergalaxy space... sent patch to the systemd-devel ML: http://lists.freedesktop.org/archives/systemd-devel/2013-April/010363.html systemd-202-2.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/FEDORA-2013-6070/systemd-202-2.fc19 systemd-202-3.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/systemd-202-3.fc19 Package systemd-202-3.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing systemd-202-3.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-6488/systemd-202-3.fc19 then log in and leave karma (feedback). systemd-202-3.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 systemd-201-2.fc18.6 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/FEDORA-2013-5452/systemd-201-2.fc18.6 systemd-201-2.fc18.6 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |