I propose throwing out all that "standards" crap like shadow files and
so on. There are already multiple ways implemented, whereas others are
missing.
I tried slock on a computer with some crazy network credential system
and entering a password results in segfault when the network has an
outage. It
Greetings.
On Tue, 08 Sep 2015 16:29:55 +0200 Jan Christoph Ebersbach wrote:
> Hi Christoph,
>
> Thank you for the hint. Attached is the patch in git format.
Your patch has been applied to mainline. Thanks for sending it in.
Sincerely,
Christoph Lohmann
Heyho Nick,
Nick wrote:
> Ideally slock should always be owned by the root user, so that it can disable
> the oom lock. I wonder what the right solution is here, as obviously one can't
> chown a file to be owned by root if one isn't root oneself.
>
> One option would be to add a line like this to
Quoth Dimitris Papastamos:
> On Tue, Sep 08, 2015 at 02:44:26PM +0100, Nick wrote:
> > Quoth Dimitris Papastamos:
> > > On Tue, Sep 08, 2015 at 02:30:39PM +0100, Nick wrote:
> > > > Separately to this, slock seems to exit (without prompt) after about
> > > > 0.3s after I run it, unless I move the
On Tue, Sep 08, 2015 at 02:44:26PM +0100, Nick wrote:
> Quoth Dimitris Papastamos:
> > On Tue, Sep 08, 2015 at 02:30:39PM +0100, Nick wrote:
> > > Separately to this, slock seems to exit (without prompt) after about
> > > 0.3s after I run it, unless I move the mouse or hit the keyboard
> > > dire
Quoth Nick:
> Quoth Dimitris Papastamos:
> > On Tue, Sep 08, 2015 at 02:30:39PM +0100, Nick wrote:
> > > Separately to this, slock seems to exit (without prompt) after about
> > > 0.3s after I run it, unless I move the mouse or hit the keyboard
> > > directly after starting it. Has anyone else se
Quoth Dimitris Papastamos:
> On Tue, Sep 08, 2015 at 02:30:39PM +0100, Nick wrote:
> > Separately to this, slock seems to exit (without prompt) after about
> > 0.3s after I run it, unless I move the mouse or hit the keyboard
> > directly after starting it. Has anyone else seen this? I could look
On Tue, Sep 08, 2015 at 02:30:39PM +0100, Nick wrote:
> Separately to this, slock seems to exit (without prompt) after about
> 0.3s after I run it, unless I move the mouse or hit the keyboard
> directly after starting it. Has anyone else seen this? I could look
> into it more, but wonder if I am
Hi folks,
I just installed slock, and found that it couldn't disable the
out-of-memory killer for itself, so wouldn't run (presumably it
would have failed later through not being able to read the shadow
file, too). This was because I installed it in a directory in my
$HOME using "make install"
