Bug 665876

Description of problem:
A possible entry for encrypted /tmp directory specified in /etc/crypttab does not result in an mounted /tmp if NetworkManager is being used and has no connection.

Version-Release number of selected component (if applicable):
initscripts-9.20.1-1.fc14.i686

How reproducible:
Use NetworkManager instead of the network subsystem
# chkconfig network off
# chkconfig NetworkManager on

Prepare encrypted /tmp directory:
# file: /etc/crypttab
tmp /dev/disk/by-id/scsi-SATA_Maxtor_6Y080L0_Y23QEQDE-part9 /dev/urandom cipher=aes-cbc-essiv:sha256,tmp

# file: /etc/fstab
/dev/mapper/tmp /tmp ext2 noexec,rootcontext=system_u:object_r:tmp_t:s0 0 0

Reboot.
 
Actual results:
The encrypted directory is present as /dev/mapper/tmp but it won't be mounted.

Expected results:
If encrypted /tmp is defined, it should always be present, no matter if the network is present or not.

Additional info:
The only reason why encrypted /tmp works when the network subsystem is used (or NM is online) is the netfs init script which does mounts all automount definitions from the fstab. If the network subsystem is not used and NM is offline the netfs script exits early and does not mount /tmp.

I've create two independent patches as proposals for a fix.
One attempt is to automount all entries from fstab after an encryption mapping has been created.
The other is an init script which checks if encrypted tmp is used but not mounted and mounts it. I'll attach them to this bug.