Red Hat Bugzilla – Bug 949702
Need appropriate timeout setting in /etc/crypttab
Last modified: 2013-05-15 23:01:36 EDT
Description of problem:
In tracking down [Bug 949697] New: Dracut should not time out and fail waiting for LUKS decryption, Harald Hoyer said that part of the problem is that anaconda needs to set the appropriate flag on setting up the system.
anaconda should write "timeout=0" in /etc/crypttab for everything.
This is a tracker bug on getting that into the Fedora 19 anaconda.
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:
systemd-202-2.fc19 has been submitted as an update for Fedora 19.
systemd-202-3.fc19 has been submitted as an update for Fedora 19.
* 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:
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.
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.