chmod 000755 /media/Devuan/var/log/cups/error_log
chmod u+s /usr/lib/dbus-1.0/dbus-daemon-launch-helper

Before "cups-daemon" begins

Another issue appear because of this, i am trying to run VirtualBox and now i can't start now appear this error :
NS_ERROR_FAILURE (0x80004005)

i try a lot of things like root:root permisons on /usr, /usr/lib
purge the package and reinstall again
recompile the dkms modules
but nothing of that works.

Another problem :

pulseaudio :

E: [pulseaudio] core-util.c: XDG_RUNTIME_DIR (/run/user/0) is not owned by us (uid 1000), but by uid 0! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
E: [pulseaudio] main.c: No se ha podido detener el demonio: No existe el fichero o el directorio
--- start
--- exit
E: [autospawn] core-util.c: XDG_RUNTIME_DIR (/run/user/0) is not owned by us (uid 1000), but by uid 0! (This could e g happen if you try to connect to a non-root PulseAudio as a root user, over the native protocol. Don't do that.)
W: [autospawn] lock-autospawn.c: No se puede acceder al candado de autogeneración.
E: [pulseaudio] main.c: Failed to acquire autospawn lock

locate xsession
locate: no se puede abrir `/var/lib/mlocate/mlocate.db': Permiso denegado

That error make a mess with my permissions.

rm will remove the directory entry, but won't free space if something still has the file open. You might be able to find it by looking in /proc (it will be in a directory of the PID of the task that has it open) and truncate it there. Otherwise restarting the task(s) will free the space (if all else fails a reboot restarts everything).

Chris

PS. I learnt that in the college of hard knocks.

The problem is when i restart the system the permissons of /usr/lib/cups/notifier again its 777 and not 000755
Using OpenRC, where i can set the permission of that files / folders ?

and the another thing i need is a script (with root permisions) to check the size of /usr/lib/cups/notifier/error_log , and if the size is => 10MB delete it, and generate again in black

Something maybe like (i use the another file can grow without limits for this example) :

XSE=$(du -h "$HOME/.xsession-errors" | awk '{print $1}')
if [ "$XSE" = "512K" ] ; then
        rm -rf "$HOME/.xsession-errors"
        touch "$HOME/.xsession-errors"
        echo '' | tee "$HOME/.xsession-errors"
fi

I don't know why this logs file don't have a logic limitation, using size and/or days for prevent generate the error of 0 Bytes Available

chris@rigel:~/bin$ df -k /proc/
Filesystem     1K-blocks  Used Available Use% Mounted on
proc                   0     0         0    - /proc

/proc/kcore will be your systems virtual storage mapped to a file. Don't worry about it (or anything else in /proc).

And in case it helps:
chris@rigel:~/bin$ ll /usr/lib/cups/notifier/dbus
-rwxr-xr-x 1 root root 14328 Jul 11  2018 /usr/lib/cups/notifier/dbus

Chris

find / -type f -printf '%s %p\n'| sort -nr | head -50

Results :

140737477877760 /proc/kcore
11829440493 /media/Devuan/var/log/cups/error_log

WTF!. the available size on my pc total is 790GB. its impossible to be 128 Teras

This looks like a file with holes in it.

When something is mapped to memory only some of the pages may be present, thus there could be a page starting at 0 and another page high up in memory. If this address space is mapped to a file, then the file can have a (big) hole in it. Some measures of the size of the file look at the final address and report that as the size. Other methods look at how many pages are used and report a size based on that.

This has the advantage that a large address space can be stored in a much smaller file.

Geoff

This message repeat infinity :

D [13/May/2019:23:06:09 -0400] Notifier dbus started - PID = 0
W [13/May/2019:23:06:09 -0400] Notifier for subscription 275 (dbus://) went away, retrying!
E [13/May/2019:23:06:09 -0400] File \"/usr/lib/cups/notifier/dbus\" has insecure permissions (0100777/uid=0/gid=0).

i just need the right permissions of the file :
/usr/lib/cups/notifier/dbus

apt-get install -y --reinstall cups-daemon

i saw a ne error :

GDBus.Error:org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the setuid helper is not correct

Checking permissions :

ls -al /usr/lib/dbus-1.0/dbus-daemon-launch-helper
-rwxrwxrwx 1 root messagebus 44048 mar 16 02:22 /usr/lib/dbus-1.0/dbus-daemon-launch-helper

Fix :

su -c "chmod u+s /usr/lib/dbus-1.0/dbus-daemon-launch-helper" root
su -c "chmod 000755 -R /usr/lib/cups/notifier" root

find / -type f -printf '%s %p\n'| sort -nr | head -50

Results :

140737477877760 /proc/kcore
11829440493 /media/Devuan/var/log/cups/error_log

WTF!. the available size on my pc total is 790GB. its impossible to be 128 Teras

Ok i try this way :

du -ah /proc/kcore

Result :

0	/proc/kcore

i don't understand. this thing have size or not

Ok the another file :

du -ah /media/Devuan/var/log/cups/error_log

Result :

12G	/media/Devuan/var/log/cups/error_log

Another thing is the file
~/.xsession-errors

can have the same size of 12GB.

Someone can tell me how i put in .bashrc a minimal script for when this files reach 1GB automatically delete it, and create again in blanks?

But when i reboot, i receive a kernel panic, just with a message /bin/bash & /sbin/init don't exist. i enter on another distro i had installed (Slackware) and then i check the file are there and perfectly funciontal.

i notice the directories /lib32 & /lib64 don't exist anymore after i do "btrfsck --repair </dev/disk_partition>" i need to know which packages install that directories and files. i just know libc6 install 1 file on a directory there.

But i know in that directories need more files to boot properly. which packages are for fix the boot ?

i just download and extract from package libc6 a the folder /lib64, just had a symbolic link

ld-linux-x86-64.so.2 -> /lib/x86_64-linux-gnu/ld-2.24.so

And with that the system boot.

But i got a new problem, I have no idea what it is that makes my system is in 0 of available space, because although it releases 10GB of space. after about 5 minutes that manages to enter the system this space is occupied again