On Fri 28 Apr 2023 at 22:36:39 (-0400), Maureen L Thomas wrote: > Here is what I got. > > root@debian:/var# /bin/ls -ld */ > drwxr-xr-x 2 root root 4096 Apr 28 15:46 backups/ > drwxr-xr-x 19 root root 4096 Apr 12 20:20 cache/ > drwxr-xr-x 2 root root 4096 Apr 28 20:59 cores/ > drwxr-xr-x 2 root root 4096 Nov 13 2020 games/ > drwxr-xr-x 62 root root 4096 Apr 12 20:20 lib/ > drwxrwsr-x 2 root staff 4096 Sep 19 2020 local/ > drwxrwxrwt 3 root root 100 Apr 28 21:13 lock/ > drwxr-xr-x 8 root root 4096 Apr 28 21:36 log/ > drwx------ 2 root root 16384 Nov 12 2020 lost+found/ > drwxrwsr-x 2 root mail 4096 Nov 12 2020 mail/ > drwxr-xr-x 2 root root 4096 Nov 12 2020 opt/ > drwxr-xr-x 27 root root 760 Apr 28 22:31 run/ > drwxr-xr-x 14 root root 4096 Apr 27 22:58 snap/ > drwxr-xr-x 7 root root 4096 Nov 12 2020 spool/ > drwxr-xr-x 8 root root 4096 Apr 28 22:32 tmp/ > root@debian:/var#
You've effectively got no /tmp available for most users. drwxrwxrwt 6 root root 4096 Apr 28 21:02 tmp/ On Sat 29 Apr 2023 at 07:12:13 (+0200), to...@tuxteam.de wrote: > On Fri, Apr 28, 2023 at 10:05:01PM -0400, Maureen L Thomas wrote: > > Yes my figures are very similar to yours. But even after a reboot I still > > cannot burn a back up disk. > > One problem may be that /var/log has subdirectories which don't > belong to root. Applications trying to write their logs might > fail, either because they can't create "their" log subdirectory > or because they even don't try (because they rely on the install > process having done that). > > Here's an example, but note that your package set will differ > from mine, so take this as illustrative: Can I also add to your listing (as a systemd-user): drwxr-sr-x+ 3 root systemd-journal 4096 Jan 1 2022 /var/log/journal $ getfacl -p /var/log/journal/ # file: /var/log/journal/ # owner: root # group: systemd-journal # flags: -s- user::rwx group::r-x group:adm:r-x mask::r-x other::r-x default:user::rwx default:group::r-x default:group:adm:r-x default:mask::r-x default:other::r-x $ Cheers, David.
