On Thu, 2 Feb 2023 at 00:07, Freyja <sio...@sioban.net> wrote:
> I've already tried to solve this issue in December with some success
Hi, could you describe in detail what you did?
Can you also post the output of:
cat /etc/systemd/system.conf
Also, a small thing I happened to notice:
> root in /var/log
> ❯ ls -la journal/
> total 44
> drwxr-sr-x+ 3 root systemd-journal 4096 Aug 19 2021 .
> drwxr-xr-x. 33 root root 12288 Feb 1 06:25 ..
^
On my system I do not have the '.' character in column 11
which you show in your output line that I have quoted
immediately above. I don't know anything about that or
if is relevant, just mentioning it in case someone else
can comment on that.
Command
info -f coreutils -n 'What information is listed'
says:
Following the file mode bits is a single character that specifies
whether an alternate access method such as an access control list
applies to the file. When the character following the file mode
bits is a space, there is no alternate access method. When it is a
printing character, then there is such a method.
GNU ‘ls’ uses a ‘.’ character to indicate a file with a security
context, but no other alternate access method.
