[systemd-devel] cryptosetup units must have timeout

[Andrey Borzenkov]

[root at localhost ~]# systemctl status cryptsetup at secrets.service
cryptsetup at secrets.service - Cryptography Setup for secrets
          Loaded: loaded
(/dev/.systemd/generator-ImgwKs/cryptsetup at secrets.service)
          Active: activating (start) since Mon, 21 Feb 2011 21:21:48
-0500; 11min ago
        Main PID: 670 (systemd-cryptse)
          CGroup: name=systemd:/system/cryptsetup at .service/secrets
                  └ 670 /lib/systemd/systemd-cryptsetup attach secrets /de...
[root at localhost ~]# date
Mon Feb 21 21:33:23 EST 2011

Well, the problem is, these units are appeared to be stuck forever in
activating state even if user never supplied password; and in this
case the block shutdown for 3 minutes. Which is not good.

May be they are constantly reactivated by respective mount unit.

[root at localhost ~]# grep secrets /etc/fstab /etc/crypttab
/etc/fstab:# secrets
/etc/fstab:/dev/mapper/secrets /secrets ext2 defaults 2 2
/etc/crypttab:secrets UUID=9cb97898-8892-41fc-92d3-a655805addc3 none noauto

Hmm ... no, mount unit is dead already

[root at localhost ~]# systemctl status secrets.mount
secrets.mount - /secrets
          Loaded: loaded
          Active: inactive (dead)
           Where: /secrets
            What: /dev/mapper/secrets
          CGroup: name=systemd:/system/secrets.mount

and there are now pending password requests

[root at localhost ~]# systemd-tty-ask-password-agent --list
[root at localhost ~]#