Andrei Borzenkov wrote:
> 15.07.2016 19:50, Alad Wenter пишет:
> ...
>
>>>> "systemctl reset-failed" is issued (note that appending the .mount unit
>>>> doesn't work in this case, giving a "Unit mnt-transcend\x2dsdhc.mount is
>>&g
Andrei Borzenkov wrote:
> 15.07.2016 18:16, Alad Wenter пишет:
>> Hi,
>>
>> When a device is mounted, a matching mount unit is created per
>> systemd.mount(5):
>>
>> Mount points created at runtime (independently of unit files or
>>/etc/fstab)
Hi,
When a device is mounted, a matching mount unit is created per
systemd.mount(5):
Mount points created at runtime (independently of unit files or
/etc/fstab) will be monitored by systemd and appear like any other
mount unit in systemd. See /proc/self/mountinfo description in
On 03/06/2015 02:47 PM, David Herrmann wrote:
Hi
On Wed, Jan 28, 2015 at 8:31 PM, Lennart Poettering
wrote:
On Sat, 17.01.15 18:36, David Herrmann (dh.herrm...@gmail.com) wrote:
I think it's reasonable to allow setting the base-timeout in
/etc/systemd/logind.conf, but I want to know Lennart'
On 01/17/2015 11:49 AM, David Herrmann wrote:
Hi
On Wed, Jan 14, 2015 at 10:54 PM, Alad Wenter wrote:
To clarify on my last message, it's 10 seconds before suspend from lid
switch works again.
Those delays are intentional. We have no idea how long the kernel
takes to probe all har
To clarify on my last message, it's 10 seconds before suspend from lid
switch works again.
Regards,
Alad
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/systemd-devel
On my Thinkpad X61 (lspci -v: http://pastie.org/9831762) running Arch
Linux and i3wm, I use systemd-logind to suspend on lid close (without
front-ends like upower, just xss-lock to run Xscreensaver).
It works nicely, except when closing the lid shortly after it was
opened. The laptop does then
