[systemd-devel] [PATCH] cryptsetup-generator: avoid ordering cycle on swap
thomas at m3y3r.de
Thu Jan 5 03:36:30 PST 2012
Zitat von Frederic Crozat <fcrozat at suse.com>:
> Le mardi 01 novembre 2011 à 23:53 +0100, Lennart Poettering a écrit :
>> On Mon, 17.10.11 17:28, Tom Gundersen (teg at jklm.no) wrote:
>> Yes, you are right. And I have no idea how we should fix that in a
>> pretty way. Thankfully not many folks are using this feature for now,
>> but it deserves to be fixed nonetheless.
>> For now I have applied your original patch and added an entry to the
>> TODO list.
> Unfortunately, I've just discovered this fix is needed but not
> sufficiant :
> - it works for encrypted swap
> - it doesn't work for encrypted tmp (using /dev/urandom as password),
> since /tmp is a needed dependency for local-fs.target, so, it causes a
> similar dependency loop, between local-fs.target,
> systemd-random-seed-load.service and cryptsetup.target and tmp.mount
> Except it is not seen as a loop by systemd (so, it is not broken by
> cycle breaker) and instead, a timeout is set on tmp.mount which fails
> after 180s.
> So far, the only solution I found is to "patch" on the fly
> systemd-random-seed-load.service, using a generator, to remove
> local-fs.target from After= list, when /dev/*random is specified
> in /etc/crypttab. Not very pretty, better suggestions welcome ;)
any news on this? I see this error on Fedoar 16, too.
More information about the systemd-devel