On Tue, Jan 22, 2019 at 3:46 AM Reindl Harald
wrote:
>
> "ProtectSystem=full" with the setup below just works, "su -" in a
> konsole within the graphical session don't gain write permissions
>
> Tasks: 4
> why?
>
> shouldn't everything started after the graphical login interherit any
> settings f
"ProtectSystem=full" with the setup below just works, "su -" in a
konsole within the graphical session don't gain write permissions
Tasks: 4
why?
shouldn't everything started after the graphical login interherit any
settings from teh display-manager service and run under it's cgroup?
--
Greetings
Not sure if this is the right place for mkosi and casync discussions
probably better create seperated mailing list for both of these
components ( lates issue against mkosi seems to be a user problem not a
bug ).
Anyway we have had two bugs reported against mkosi today one of which
On Mo, 21.01.19 09:21, Yang Lyu ([email protected]) wrote:
> Hi,
>
> Thanks for your reply.
>
> In the scenario it is not convenient to use emergency mode, I hope
> system can save some information and reboot.
What do you mean by "some information"? I mean, logs are always
kept. So JobTimeoutActi
Hi,
Thanks for your reply.
In the scenario it is not convenient to use emergency mode, I hope system can
save some information and reboot.
It is to force system to crash and generate a dump file recording status and
kernel log around that time. So that we can know what happened here through
de
