On Mon, Jul 17, 2017 at 1:59 PM, Genes Lists wrote:
> On Mon, 2017-07-17 at 06:38 +0200, SanskritFritz wrote:
> > On Sat, Jul 15, 2017 at 6:21 PM, Genes Lists via arch-general > ene...@archlinux.org> wrote:
> > > I have a work around which is to add timeout=90
> >
> > Where to add this?
> >
> >
On Mon, 2017-07-17 at 06:38 +0200, SanskritFritz wrote:
> On Sat, Jul 15, 2017 at 6:21 PM, Genes Lists via arch-general ene...@archlinux.org> wrote:
> > I have a work around which is to add timeout=90
>
> Where to add this?
>
>
in /etc/crypttab at the end of the line
--
Gene
li...@sapience
On Mon, Jul 17, 2017 at 12:16 PM, Leonid Isaev via arch-general <
arch-general@archlinux.org> wrote:
> On Mon, Jul 17, 2017 at 07:57:18AM +0200, Bartłomiej Piotrowski wrote:
> > On 2017-07-17 06:38, SanskritFritz via arch-general wrote:
> > > On Sat, Jul 15, 2017 at 6:21 PM, Genes Lists via arch-g
On Mon, Jul 17, 2017 at 07:57:18AM +0200, Bartłomiej Piotrowski wrote:
> On 2017-07-17 06:38, SanskritFritz via arch-general wrote:
> > On Sat, Jul 15, 2017 at 6:21 PM, Genes Lists via arch-general <
> > arch-general@archlinux.org> wrote:
> >
> >> I have a work around which is to add timeout=90
>
On 2017-07-17 06:38, SanskritFritz via arch-general wrote:
> On Sat, Jul 15, 2017 at 6:21 PM, Genes Lists via arch-general <
> arch-general@archlinux.org> wrote:
>
>> I have a work around which is to add timeout=90
>>
>
> Where to add this?
>
To the kernel parameters, with luks.options= key.
B
On Sat, Jul 15, 2017 at 6:21 PM, Genes Lists via arch-general <
arch-general@archlinux.org> wrote:
> I have a work around which is to add timeout=90
>
Where to add this?
I'm also running cryptsetup 1.7.5-1, but with an out-of-date linux kernel
and systemd (4.11.9-1 and 233.75-3, respectively) and it's working fine;
it's plausibly a regression with one of those two.
Is this bug also present on the linux-lts kernel? I've found some issues
I've had go away with a dif
Could wel be related:
https://github.com/systemd/systemd/pull/6264
--
Gene
li...@sapience.com
I have a work around which is to add timeout=90
It seems the timeout=0, which is the default) and is supposed to mean
wait indefinitely) is now treated as dont prompt or wait at all.
I cannot say if this is a change in behavior which is intentional and
the man pages need to be updated (man crypt
This has been working for years - starting on recent reboots systemd is
failing to ask for password for luks encrypted /home partition and boot
halts.
Fully updated from testing repos - when I reboot now, systemd no longer
asks for password to unlock luks partition. There is no hesitation at all
10 matches
Mail list logo
