| 1 |
Man... watching this discussion just makes me want to avoid systemd like |
| 2 |
the plague/all the more... |
| 3 |
|
| 4 |
On 2013-09-23 4:21 AM, Stefan G. Weichinger <lists@×××××.at> wrote: |
| 5 |
> Am 23.09.2013 10:00, schrieb Stefan G. Weichinger: |
| 6 |
> |
| 7 |
>> Getting that unit-name right is quite annoying ... fiddling with |
| 8 |
>> understanding that strange escaping etc ... :-( |
| 9 |
> |
| 10 |
> I have now: |
| 11 |
> |
| 12 |
> # cat /etc/systemd/system/dev-disk-by\\x2did-dm\\x2dname\\x2dswap.swap |
| 13 |
> [Unit] |
| 14 |
> #After=systemd-cryptsetup.service |
| 15 |
> After=systemd-cryptsetup@××××.service |
| 16 |
> |
| 17 |
> [Swap] |
| 18 |
> What=/dev/disk/by-id/dm-name-swap |
| 19 |
> |
| 20 |
> see the comment, I tried both because the swap was not activated after |
| 21 |
> boot but it is when I manually start it. |
| 22 |
> |
| 23 |
> I only have: |
| 24 |
> |
| 25 |
> # systemctl | grep cry |
| 26 |
> cryptsetup.target loaded active active Encrypted Volumes |
| 27 |
> |
| 28 |
> so I edited the dependency. This gave me encrypted swap once already |
| 29 |
> after manually starting the swap-unit. |
| 30 |
> |
| 31 |
> |
| 32 |
> But after booting it still generates another swap.service which makes |
| 33 |
> the new unit fail or run into a timeout. |
| 34 |
> |
| 35 |
> # systemctl | grep swap |
| 36 |
> dev-mapper-swap.device loaded inactive dead start |
| 37 |
> dev-mapper-swap.device |
| 38 |
> systemd-...p@××××.service loaded active exited Cryptography |
| 39 |
> Setup for swap |
| 40 |
> swap.target loaded active active Swap |
| 41 |
> |
| 42 |
> oh my ... Glad to have enough RAM for now ;-) |
| 43 |
> |
| 44 |
> for the records: no swap-stuff in fstab ... |
| 45 |
> |
| 46 |
> Stefan |
| 47 |
> |
Archives