On Thu, Sep 17, 2015 at 13:06:57 +0200, Jacek Konieczny wrote:
> On 2015-09-17 12:54, Elan Ruusamäe wrote:
>>>
>> tmp.mount was not masked, masking of course helped. but i never masked
>> it before, so something changed that now i need to mask
Well, entire systemd architecture supports on-demand
On Wed, Sep 16, 2015 at 16:16:20 +0300, Elan Ruusamäe wrote:
> what's more annoying is that it's mounted "as soon as it (systemd) can"
> meaning in the middle of working x11-session (GRRR!)
Maybe something in this session activated it via dbus? This shouldn't
happen when tmp.mount is masked
On 17.09.2015 13:14, Tomasz Pala wrote:
On Wed, Sep 16, 2015 at 16:16:20 +0300, Elan Ruusamäe wrote:
what's more annoying is that it's mounted "as soon as it (systemd) can"
meaning in the middle of working x11-session (GRRR!)
Maybe something in this session activated it via dbus? This
On 2015-09-17 12:54, Elan Ruusamäe wrote:
On 17.09.2015 13:14, Tomasz Pala wrote:
On Wed, Sep 16, 2015 at 16:16:20 +0300, Elan Ruusamäe wrote:
what's more annoying is that it's mounted "as soon as it (systemd) can"
meaning in the middle of working x11-session (GRRR!)
Maybe something in this
/tmp tmpfs mount used to be off in pld, and i'd like it to stay that way.
but seems something changed and it's mounted now by default.
what's more annoying is that it's mounted "as soon as it (systemd) can"
meaning in the middle of working x11-session (GRRR!)
i haven't updated systemd itself
